IBM Support

CWSIV0775W, CWSIT0088E and CWSIT0103E errors are thrown and application is not able to find running Messaging Engine even through the same Messaging Engine is running in the cluster

Technote (troubleshooting)


Application is not able to find the running WebSphere Application Server (WAS) Messaging Engine (ME), even though the requested ME is up and running.


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
@1780178 <active=true> <connections={}>
@aaf7b289> <endpointConfiguration=[
vationSpecImpl@1538415538 <userName=null> <password=null>
<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>
@16a016a> <>
<endpointMethodTransactional=true> <remoteConnection=null>
<remoteDestination=true> <timer=java.util.Timer@1e201e2>] failed with
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


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.

Cross reference information
Segment Product Component Platform Version Edition
Business Integration WebSphere MQ Configuration
Business Integration WebSphere Process Server
Business Integration WebSphere Service Registry and Repository
Business Integration IBM Business Process Manager Standard
Business Integration WebSphere Enterprise Service Bus
Business Integration WebSphere Partner Gateway - Express

Historical Number

39025 422 000

Product Alias/Synonym

WebSphere Application Server WAS SIB SIBUS SI BUS

Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 7.0, 8.0, 8.5.5, 9.0

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows

Software edition: Base, Network Deployment

Reference #: 1624734

Modified date: 30 September 2013

Translate this page: