Use this set of specific tips to help you troubleshoot problems with service integration messaging engines.
A messaging engine fails to start and the following error is displayed in the WebSphere® Application Server administrative console:
The messaging engine <name> cannot be started as there is no runtime initialized for it yet, retry the operation once it has been initialized. If dynamic configuration reload is enabled for this bus, then the servers must be restarted.
Before trying to start the messaging engine again, make sure that you have restarted the server. For the runtime to initialize successfully, the application server must be started.
To find out whether a start up problem is preventing the messaging engine runtime from initializing, check for error messages in the SystemOut.log of the hosting server.
When attempting to use the Informix JDBC driver 3.00JC1 to store data, the messaging engine cannot start up and the following error message might appear in the WebSphere Application Server SystemOut.log file:
00000022 SibMessage E [RetireBus:retire_web.000- RetireBus] CWSIS0002E: The messaging engine encountered an exception while starting. Exception: com.ibm.ws.sib.msgstore.PersistenceException: CWSIS1501E: The data source has produced an unexpected exception: java.sql.BatchUpdateException: Unique constraint (informix.u114_62) violated. 00000022 SibMessage E [RetireBus:retire_web.000- RetireBus] CWSID0035E: Messaging engine retire_web.000-RetireBus cannot be started; detected error reported during com.ibm.ws.sib.msgstore.impl.MessageStoreImpl start() 00000022 SibMessage E [RetireBus:retire_web.000- RetireBus] CWSID0027I: Messaging engine retire_web.000-RetireBus cannot be restarted because a serious error has been reported.T] 00000022 SibMessage I [RetireBus:retire_web.000- RetireBus] CWSID0016I: Messaging engine retire_web.000-RetireBus is in state Stopped.
There is a known defect (PTS 172471) in the Informix JDBC Driver 3.00JC1. To avoid this error, upgrade the Informix JDBC Driver to 3.00JC2.
AdminControl.invoke(AdminControl.queryNames("type=SIBMessagingEngine, name=messagingenginename,*"), "dump", "com.ibm.ws.sib.msgstore.*")
$AdminControl invoke [$AdminControl queryNames type=SIBMessagingEngine, name=messagingenginename,*] dump com.ibm.ws.sib.msgstore.*
The dump is created as an XML file in the $WAS_HOME/logs/server1 directory. The file is named according to the format: messaging_engine_nameUUIDtimestamp.xml
<MessageStore> <itemStreams> <ItemStreamLink id="0" state="Available"> <class>com.ibm.ws.sib.msgstore.ItemStream</class> <priority>5</priority> <canExpireSilently></canExpireSilently> <storageStrategy>STORE_NEVER</storageStrategy> <expiryTime>0</expiryTime> <sequence>0</sequence> <tranID>null</tranID> <tickValue>0</tickValue> <items> <ItemLink id="2" state="Available" refCount="3" refCountDecreasing="false"> <class>com.ibm.ws.sib.msgstore.Item</class> <priority>5</priority> <canExpireSilently></canExpireSilently> <storageStrategy>STORE_NEVER</storageStrategy> <expiryTime>0</expiryTime> <sequence>1</sequence> <tranID>null</tranID> <tickValue>0</tickValue> </ItemLink></items></ItemStreamLink></itemStreams></MessageStore>
CWSIS1546I: The messaging engine, ME_UUID={0}, INC_UUID={1}, has lost an existing lock or failed to gain an initial lock on the data store.
To solve this problem, you must follow the procedure described in Resolving indoubt transactions.
[8/11/04 21:55:01:439 CDT] 0000000f SibMessage I [LateBus:xyzsun15.server1-LateBus] isAlive: MessagingEngine suffered common mode error. Correct error (see logs) and restart server. [8/11/04 21:55:01:468 CDT] 0000000f SibMessage I [LateBus:xyzsun15.server1-LateBus] isAlive: MessagingEngine will be stopped because of common mode error. No failover will occur. [8/11/04 21:55:01:493 CDT] 0000000f SibMessage I [LateBus:xyzsun15.server1-LateBus] Messaging Engine xyzsun15.server1-LateBus not in state from which stop is valid: Starting [8/11/04 21:55:01:513 CDT] 0000000f SibMessage I [LateBus:xyzsun15.server1-LateBus] isAlive: MessagingEngine stopped because of common mode error. Correct error (see logs) and restart server. [8/11/04 21:57:01:431 CDT] 0000000e SibMessage I [LateBus:xyzsun15.server1-LateBus] isAlive: MessagingEngine suffered common mode error. Correct error (see logs) and restart server.
The messaging engine failed to start because the database directory for the messaging engine still exists after deletion of the bus and you must manually remove it. To delete the Apache Derby database for a non-existent messaging engine, you must delete the database directory that is located in profile_root/databases/com.ibm.ws.sib, where profile_root is the directory in which profile-specific information is stored.
You must stop WebSphere Application Server before you can delete the database files.
For other databases, you can either delete all of the rows from the data store tables or you can drop all of the data store tables. These tables are in the schema that you configured for the data store. For a list of the tables, see Data store tables.
For more information, see Data store life cycle.
To enable communication between buses, a foreign bus and a service bus integration link must be created. On the first bus, the name of the foreign bus must match the name of the second bus that becomes a foreign bus, and the name of the foreign bus for this second bus must match the name of the first bus. The service integration bus link must be have the same name on both buses.
You may see the following type of error if your configuration is not correct, for example because the service integration bus links do not match:
SibMessage E [TechBus:TechCluster.000-TechBus] CWSIT0057E: The inter-bus connection BookstoreBus failed in the remote messaging engine on host aixp401.rchland.ibm.com with reason: CWSIT0067E: Inter-bus connection BookstoreBus in bus BookstoreBus is not available.
The administrative console panel used for configuring the properties of a service integration bus link can also be used to change the foreign bus name that the link is pointing to. However, you must not alter the name of the foreign bus after it has been configured. If you do, any messaging engines that already hold state information about the link will not be able to use the link until the foreign bus name is reset to its previous value.
When the number of messages held by a destination reaches its limiting threshold, any attempt to send a message to that destination fails with a JMSException with a wrapped SILimitExceeded exception. The destination continues to fail with this exception until the number of messages held by the destination reduces below the limiting threshold.
To obtain an accurate count of the number of available messages, you can monitor the Available Message Count PMI statistic for queue and topicspace destinations. If the number of available messages increases, take action to balance the system. Consider stopping producers from sending new messages until the destination consumes the available messages.
The ideal balance is for the number of messages produced and the number of messages consumed to be equal over a period of time. If your system is unbalanced and the producing application sends more messages than the destination can consume, the producing application eventually throws a JMSException.
Consider cloning your application across multiple servers in a non-clustered environment. By default, applications are cloned in a clustered server environment. To enable subscribers in a non-clustered environment, set the cloned flag in the TopicConnectionFactory JNDI setting for DurableSubscriptions.
It is possible, although rare, for a messaging engine, destination or link to be corrupted after a restart of the system. If this corruption occurs you will see a message indicating the problem. If the problem lies with the messaging engine, the messaging engine will not start. If a destination or link is corrupted, the relevant messaging engine will start, but the destination or link will not be usable on that messaging engine.
If you do not know the cause of the problem, contact your IBM service representative to establish the cause before attempting to resolve the situation.
To be able to retrieve the status of messaging engines, you must be logged into the administrative console with at least monitor authority. If you do not have this authority, the messaging engine status is displayed as "Unavailable", even if the messaging engine has started.
[4/20/05 10:49:57:083 CDT] 0000004b RoleBasedAuth A SECJ0305I: The role-based authorization check failed for admin-authz operation SIBMessagingEngine:stateExtended. The user UNAUTHENTICATED (unique ID: unauthenticated) was not granted any of the following required roles: administrator, operator, configurator, monitor.Where the user ID shown in the message is the user ID that you used to log in to the administrative console.
If an application depends on a messaging engine being available, then the messaging engine must be started before the application can be run. If you want application server to start an application automatically, you should develop your applications to test that any required messaging engine has been started and, if needed, wait for the messaging engine. If this technique is used in a startup bean, then the startup bean method should perform the test and wait work in a separate thread (using the standard WorkManager methods), so that the application server startup is not delayed.
For an example of code to test and wait for a messaging engine, see Applications with a dependency on messaging engine availability.