Troubleshooting
Problem
Application is not able to find the running WebSphere Application Server (WAS) Messaging Engine (ME), even though the requested ME is up and running.
Symptom
You see the following errors in the SystemOut.log:
CWSIV0775W: The creation of a connection for destination <destination name> on bus
<Bus_name> for endpoint activation
[com.ibm.ws.sib.ra.inbound.impl.SibRaStaticDestinationEndpointActivation
@1780178 <active=true> <connections={}>
<messageEndpointFactory=com.ibm.ejs.container.MessageEndpointFactoryImpl
@aaf7b289> <endpointConfiguration=[com.ibm.ws.sib.api.jmsra.impl.JmsJcaActivationSp
ecImpl$JmsJcaEndpointConfigurationImpl@20709692
<JmsJcaActivationSpecImpl.this=[com.ibm.ws.sib.api.jmsra.impl.JmsJcaActi
vationSpecImpl@1538415538 <userName=null> <password=null>
<xaRecoveryAlias=null>
<destination=topic://ws_avs_gmail_out_t?topicSpace=<name>&de
liveryMode=Persistent&busName=<Bus_name>>
<durableSubscriptionHome=<ME_name>>
<destinationType=javax.jms.Topic> <messageSelector=EventType in ('')>
<acknowledgeMode=Auto-acknowledge> <subscriptionDurability=Durable>
<shareDurableSubscriptions=InCluster> <clientId=pvs>
<subscriptionName=pvs_mdb> <maxBatchSize=1> <maxConcurrency=1>
<busName=jms_Bus> <shareDataSourceWithCMP=false>
<targetTransportChain=null> <readAhead=Default> <target=null>
<targetType=BusMember> <targetSignificance=Preferred>
<providerEndpoints=null>]>]>
<endpointInvoker=com.ibm.ws.sib.api.jmsra.impl.JmsJcaEndpointInvokerImpl
@16a016a> <workManager=com.ibm.ejs.j2c.work.WorkManagerImpl@51cc51cc>
<endpointMethodTransactional=true> <remoteConnection=null>
<remoteDestination=true> <timer=java.util.Timer@1e201e2>] failed with
exception com.ibm.websphere.sib.exception.SIResourceException:
CWSIT0088E: There are currently no messaging engines in bus jms_Bus
running. Additional failure information: CWSIT0103E: No messaging
engine was found that matched the following parameters: bus=<BUS_name>,
targetGroup=null, targetType=BusMember, targetSignificance=Preferred,
transportChain=InboundBasicMessaging, proximity=Bus..
...
...
DiscoveryRcv W DCSV1115W: DCS Stack <server_name>: Member <server_name> connection was closed. Member will be removed from view. DCS connection status is Discovery|Ptp, receiver
closed.
Cause
The Service Integration Bus (SIB) relies on the Work Load Manager (WLM) to locate messaging engines (ME). When an application makes a connection request, the WLM tries to find the ME. If the ME is running on a server that is not part of the local core group, and there is no bridge between the local core group and the one where the desired ME is running, then the WLM will not be able to find the ME, even though it is running.
This equally applies if client and server are in different cells.
Resolving The Problem
Add all servers to the same core group, or configure a bridge between the core groups if the servers need to be members of a different core group.
The following articles may be useful in planning your core group configuration.
- Configuring communication between core groups that are in the same cell
- Configuring the core group bridge between core groups that are in different cells
- Core groups (high availability domains)
- Best Practices for Large WebSphere Application Server Topologies, "section "2.1.7.2 Partitioning the cell"
Historical Number
39025 422 000
Product Synonym
WebSphere Application Server WAS SIB SIBUS SI BUS
Was this topic helpful?
Document Information
Modified date:
19 October 2022
UID
swg21624734