PK90983: SICOMMANDINVOCATIONFAILEDEXCEPTION DURING APPLICATION STARTUP

Fixes are available

APAR status

Closed as program error.

Error description

The following exception is thrown when an application starts:
[7/1/09 14:58:19:695 EDT] 0000002a SystemErr R Exception in
thread "System RM Persistent store Threadpool : 0" java.lang.
RuntimeException:com.ibm.ws.sib.wsrm.exceptions.MEStore
ConnectionException: CWSJZ0001E: An internal messaging error
occurred in MEStoreConnectionImpl, 1:819:1.33.1.15;
nested exception is:
com.ibm.wsspi.sib.core.exception.SICommandInvocationFailed
Exception:INVOKE_COMMAND_ERROR_CWSIR0151
[7/1/09 14:58:19:695 EDT] 0000002a SystemErr R at
com.ibm.ws.websvcs.rm.impl.storage.PersistentStorageManager
Singleton.initializeStore(PersistentStorageManagerSingleton.
java:549)
[7/1/09 14:58:19:695 EDT] 0000002a SystemErr R at
com.ibm.ws.websvcs.rm.impl.storage.PersistentStorageManager
Singleton.messagingEngineConnectionOpened(
PersistentStorageManagerSingleton.java:464)
[7/1/09 14:58:19:695 EDT] 0000002a SystemErr R at
com.ibm.ws.sib.wsrm.impl.connection.MEStoreConnectionImpl.
initialiseNonTxMEConnection(MEStoreConnectionImpl.java:404)
[7/1/09 14:58:19:695 EDT] 0000002a SystemErr R at
com.ibm.ws.sib.wsrm.impl.connection.MEStoreConnectionImpl.
initialize(MEStoreConnectionImpl.java:304)
[7/1/09 14:58:19:696 EDT] 0000002a SystemErr R at
com.ibm.ws.websvcs.rm.impl.storage.PersistentStorageManager
Singleton$2.run(PersistentStorageManagerSi
ngleton.java:682)
[7/1/09 14:58:19:696 EDT] 0000002a SystemErr R at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
............................... ...........................
? [7/8/09 11:27:14:644] XXX MEStoreConnec [[:] Tracing
exception:]
[:] Tracing exception:com.ibm.wsspi.sib.core.exception.
SICommandInvocationFailedException:
INVOKE_COMMAND_ERROR_CWSIR0151
at com.ibm.ws.sib.processor.impl.ConnectionImpl.internalInvoke
Command(ConnectionImpl.java:7065)
at com.ibm.ws.sib.processor.impl.ConnectionImpl.invokeCommand
(ConnectionImpl.java:6954)
at com.ibm.ws.sib.wsrm.impl.connection.MEStoreConnectionImpl.
performInvoke(MEStoreConnectionImpl.java:771)
.
The reason why the exception is thrown is because the WSRM
CommandHandler has not been registered yet. We appear to have
two threads in a race. Thread XXX appears to be called when
the messaging engine connection is established and attempts to
invoke a command.  Thread YYY is the one that resgistered the
command handler but does so after the invoke command happens:
> [7/8/09 11:27:14:985] YYY ConnectionImp.register
CommandHandler()[[ossBus:agd017Node02websv.PRdySrv02-ossBus]
Entry]

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server 7.0                                  *
****************************************************************
* PROBLEM DESCRIPTION: SICommandInvocationFailedException      *
*                      during application startup              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The reason why the exception is thrown is because the WSRM
CommandHandler has not been registered yet. We appear to have
two threads in a race. Thread XXX appears to be called when
the messaging engine connection is established and attempts to
invoke a command.  Thread YYY is the one that resgistered the
command handler but does so after the invoke command happens.
The subsequent Exception is now marked as transient.

Problem conclusion

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.7.  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
PK90983
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-07-09
Closed date
2009-08-10
Last modified date
2009-08-10

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

PK93630

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK90983: SICOMMANDINVOCATIONFAILEDEXCEPTION DURING APPLICATION STARTUP

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?