Troubleshooting
Problem
You are unable to start WebSphere Application Server (WAS) message engine(ME) either with JVM restart or manually with WAS console.
Symptom
When WAS console is used to start ME. The following error is reported
The messaging engine "ME_name" cannot be started as there is no runtime initialized for it yet, retry the operation once it has initialized. For the runtime to successfully initialize the hosting server must be started, have its 'SIB service' already enabled, and dynamic configuration reload enabled. If this is a newly configured messaging engine and it is the first messaging engine to be hosted on this server, then it is most likely the 'SIB service' was not previously enabled and thus the server will need to be restarted. The messaging engine runtime might not be initializing because of an error while trying to start, examine the SystemOut.log of the hosting server to check for error messages indicating the problem
In the SystemOut.log following errors are seen.
[ME_NAME] CWSIS1581I: The file store is attempting to initalise its log file: \\machine\Data\messageStores\Cluster\log\Log
[ME_NAME] CWSIS1580E: The file store's log file cannot be found in the provided location: \\machine\Data\messageStores\Cluster\log\Log.
[ME_NAME] CWSIS1582I: The file store had a problem initialising its log file but will attempt to retry.
This repeats many times then you see following
[ME_NAME] CWSIS1582I: The file store had a problem initialising its log file but will attempt to retry.
[ME_NAME] CWSIS1583E: The file store has exceeded the initialisation retry limit and will now stop.
[ME_NAME] CWSIS0002E: The messaging engine encountered an exception while starting. Exception: com.ibm.ws.sib.msgstore.SeverePersistenceException: Retry time limit reached when starting file store!
[ME_NAME] CWSID0035E: Messaging engine BlogsCluster.000-ConnectionsBus cannot be started; detected error reported during com.ibm.ws.sib.msgstore.impl.MessageStoreImpl start()
[ME_NAME] CWSID0027E: Messaging engine BlogsCluster.000-ConnectionsBus cannot be restarted because a serious error has been reported.
[ME_NAME] CWSID0016I: Messaging engine BlogsCluster.000-ConnectionsBus is in state Stopped.
[ME_NAME] CWSID0016I: Messaging engine BlogsCluster.000-ConnectionsBus is in state Joined.
[ME_NAME] CWSID0039E: HAManager-initiated activation has failed, messaging engine ME_NAME will be disabled. Reason Refer to earlier messages
Cause
In this case, the end user was using a local id to start WAS. The ID did not have permission for the file store logs.
Resolving The Problem
The correct id and password were inserted in the Services panel for WebSphere Application Server.
Product Synonym
WebSphere Application Server WAS SIB SIBUS SI BUS
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21610323