Hi , I Installed Websphere 7 in linux server and deployed the buses in the server.

After installing i found one cluster  reached to unavailable state and if i tried to start and i'm  getting the below error


"The messaging engine IICPNRSvcs.000-WbeBus 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 "



i checked Messaging engines also present  and from logs getting the  below mentioned error is shown

Hi gaurav

  After create a SIB Bus and add members (message engine are created in members), you need to restart the members.

  Have you tried to start cluster members independently?

  Hope this helps.  Tell us if you need more support.

regards

Thanks Gabriel.! I already performed these steps but it did not work. one more point for this bus we are using horizontal base cluster architecture and once creating the bus and it's  members, the messaging engine aquires the status as unknown.  Kindly advise or suggest me as I'm totally new in this field thanks 

Gaurav

  Please attach the start of the one of the cluster members to review which is the problem.
 
  Thanks

Regards 

Hi Gabriel,  u are saying in that in configuration rather than cluster option I need to check single single server and tried to find which cluster member is having the issue. Please correct me if I'm wrong thanks 

Gaurav,

  When you attach to SIB Bus a cluster as member, the message engine (ME) is only started in one of the cluster members not in all because is a singleton service. When the cluster members is stoped other cluster member takes the ME.

  For test purpose, you can start only one cluster member (server) and review why is not starting your ME.

  Hope this help.   Tell us if you need more support.
 
regards

Hi Gabriel thanksa lot ! for showing the correct path I did the same and issue is resolved.

Glad to help Gaurav

Regards