PK73009: SECJ0306E error seen in logs when Node Agent is shutdown, while global security is enabled

Fixes are available

APAR status

Closed as program error.

Error description

The following error message shows up in Node Agent logs when
Node Agent is shutdown while global security is enabled:

RoleBasedAuth E   SECJ0306E: No received or invocation
credential exist on the thread. The Role based authorization
check will not have an accessId of the caller to check.  The
parameters are: access check
method propagateNotifications:[Ljavax.management.Notification;
on resource NotificationService and module NotificationService.

The stack trace is:

java.lang.Exception: Invocation and received credentials are
both null
at
com.ibm.ws.security.role.RoleBasedAuthorizerImpl.checkAccess(Rol
eBasedAu
thorizerImpl.java:251)
at
com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImp
l.java:1
799)
at
com.ibm.ws.management.AdminServiceImpl.access$400(AdminServiceIm
pl.java:
101)
at
com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.ja
va:988)
at
com.ibm.ws.security.util.AccessController.doPrivileged(AccessCon
troller.
java:118)
at
com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.j
ava:906)
at
com.ibm.ws.management.connector.AdminServiceDelegator.invoke(Adm
inServic
eDelegator.java:157)
at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown
Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
Accessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
com.ibm.ws.management.connector.soap.SOAPConnector.invoke(SOAPCo
nnector.
java:345)
at
com.ibm.ws.management.connector.soap.SOAPConnector.service(SOAPC
onnector
.java:210)
at
com.ibm.ws.management.connector.soap.SOAPConnection.handleReques
t(SOAPCo
nnection.java:55)
at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnecti
on.java:
680)
at
com.ibm.ws.http.HttpConnection.run(HttpConnection.java:484)
at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1470)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
****************************************************************
* PROBLEM DESCRIPTION: When global security is enabled,        *
*                      NodeAgent logs display SECJ0306E        *
*                      error on NodeAgent shutdown.            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This behavior is observed when node agent shuts down while
global security is enabled and application servers monitored
by the node agent are running.

Node agent logs would contain the following error message:

RoleBasedAuth E   SECJ0306E:No received or invocation
credential exist on the thread. The   Role based authorization
check will not have an accessId of the caller to check.  The
parameters are: access check method
propagateNotifications:[Ljavax.management.Notification; on
resource NotificationService and module NotificationService.
The stack trace is java.lang.Exception: Invocation and
received credentials are both null
at
com.ibm.ws.security.role.RoleBasedAuthorizerImpl.checkAccess(Rol
eBasedAuthorizerImpl.java:251)
at
com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImp
l.java:1799)
at
com.ibm.ws.management.AdminServiceImpl.access$400(AdminServiceIm
pl.java:101)
at
com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.ja
va:988)
at
com.ibm.ws.security.util.AccessController.doPrivileged(AccessCon
troller.java:118)
at
com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.j
ava:906)
at
com.ibm.ws.management.connector.AdminServiceDelegator.invoke(Adm
inServiceDelegator.java:157)
at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
AccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
com.ibm.ws.management.connector.soap.SOAPConnector.invoke(SOAPCo
nnector.java:345)
at
com.ibm.ws.management.connector.soap.SOAPConnector.service(SOAPC
onnector.java:210)
at
com.ibm.ws.management.connector.soap.SOAPConnection.handleReques
t(SOAPConnection.java:55)
at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnecti
on.java:680)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:484)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1470)

Problem conclusion

The errors occurred because admin code was invoking security
code even after security service was stopped (as a part of
NodeAgent shutdown). Code fix has been introduced to check
state of SOAPConnector security before invoking its code.

The fix for this APAR is currently targeted for inclusion in
fixpacks 6.0.2.33, 6.1.0.23 and 7.0.0.3. Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK73009
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
60A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-09-30
Closed date
2009-01-13
Last modified date
2009-01-14

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK73009: SECJ0306E error seen in logs when Node Agent is shutdown, while global security is enabled

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?