MLS is not starting on one of the nodes in a cluster.
MLS application failing to start on the secondary node with this exception:
Caused by: javax.resource.ResourceException: Failed to lookup
ActivationSpec.jms/IWKItemChangeMonitorActivation
at com.ibm.ejs.j2c.RALifeCycleManagerImpl.activateEndpoint(RALifeCycleManagerImpl.java:1721)
at com.ibm.ejs.container.MessageEndpointFactoryImpl.activateEndpoint(MessageEndpointFactoryImpl.java:296)
at com.ibm.ws.runtime.component.EJBContainerImpl.startMDBs(EJBContainerImpl.java:5368)
... 50 more
Caused by: javax.naming.NameNotFoundException: Context: xxx123sCell/clusters/wp_cluster, name:
jms/IWKItemChangeMonitorActivation: First component in name
jms/IWKItemChangeMonitorActivation not found. [Root exception is
org.omg.CosNaming.NamingContextPackage.NotFound:
IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
at com.ibm.ws.naming.jndicos.CNContextImpl.mapNotFoundException(CNContextImpl.java:4563)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1821)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1776)
This happens if the Activation Spec is created on only one of the nodes instead of on the cluster.
Complete the following steps to modify the Web Content Manager message Page driven bean (MDB) to include additional service integration (SIB) endpoints, one for each cluster member in the subscriber cluster:
Open the Deployment Manager administrative console.
Navigate to Resources -> JMS -> Activation specifications.
Select IWKItemChangeMonitorActivation and under Provider endpoints add
the additional server:port:BootstrapBasicMessaging for each cluster
member in the subscriber cluster; separate them by commas.
Click OK to save your changes.
Select IWKSyndicationMonitorActivation and
under Provider endpoints add the additional
server:port:BootstrapBasicMessaging for each cluster member in the
subscriber cluster; separate them by commas.
Click OK to save your changes.
Click Save to save your changes.
Log out of the Deployment Manager administrative console.
Complete the following steps to modify the Web Content Manager JMS Connection Factory definition to include additional SIB endpoints, one for each cluster member in the subscriber cluster:
Open the Deployment Manager administrative console.
Navigate to Resources -> JMS -> Topic connection factories. Select
IWKMessagingTopicConnectionFactory and
under Provider endpoints add the additional
server:port:BootstrapBasicMessaging for each cluster member in the
subscriber cluster; separate them by commas.
Click OK to save your changes.
Click Save to save your changes.
Log out of the Deployment Manager administrative console.
Restart the cluster.