Solaris Cluster 4.3 HA WebSphere MQ Reach Timeout and Goes into "Start failed" when More Than 4 WebSphere MQ Resources Started
Last updated on OCTOBER 27, 2016
Applies to:Solaris Cluster - Version OSC 4.3 to OSC 4.3 [Release 4.3]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
In this scenario Solaris Cluster 4.3 is running Cluster Data Service for IBM WebSphere MQ.
After installing and configuring 8 HA WebSphere resources only 4 WebSphere resources are able to start.
Outside the cluster all 8 WebSphere queue managers are able to start.
When trying to start more than 4 WebSphere resources the fifth resource is reaching start timeout and going into "Start failed" state.
This occures not to the specific resource . It is for any WebSphere resource after 4th resource.
In /var/adm/messages this looks like this:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms