PM71953: JMS APPLICATION RECEIVES CWSIT0019E ERROR THOUGH THE SERVICE INTEGRATION BUS MESSAGING ENGINE IS UP AND RUNNING

Fixes are available

APAR status

Closed as program error.

Error description

After undeploying and deploying an application in a WebSphere
Process Server(WPS) environment, application cannot access
the destination running under the ME (by using targetType as
Destination), though the ME is running and destination is
avaible. Application produced the CWSIT0019E errors as follows:

Exception:com.ibm.websphere.sib.exception.SIResourceException
SourceId:com.ibm.ws.sib.ra.impl.SibRaConnectionInfo.create
Connection
ProbeId:1 Reporter:com.ibm.ws.sib.ra.impl.SibRaConnectionInfo
@68e268e2 com.ibm.websphere.sib.exception.SIResourceException:
CWSIT0019E: No suitable messaging engine is available on bus
XXXBus that matched the specified connection properties
{targetSignificance=Required, busName=XXXBus, targetType=
Destination,targetGroup=sca/XXX Module}. Reason for failure:
CWSIT0103E: No messaging engine was found that matched the
following parameters: bus=XXXBus,targetGroup=sca/XXXModule,
targetType=Destination, targetSignificance=Required,
transportChain=InboundSecureMessaging, proximity=Bus.
at
com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl.localBo
otstrap(TrmSICoreConnectionFactoryImpl. java:363)

Local fix

```
Restart the messaging cluster
```

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider     *
*                  for IBM WebSphere Application Server 7.x    *
*                  and 8.x.                                    *
****************************************************************
* PROBLEM DESCRIPTION: Application cannot connect with the     *
*                      destination resulting CWSIT0019E        *
*                      error, though ME is running and         *
*                      destination is available.               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This is a timing issue and it may occur when there is a WPS
application deployment (creates SIB destination) immediately
after an application undeployment (deletes SIB destination).
The scenario at which the problem can occur
1) A destination "Destination A" is marked for deletion during
application undeployment. The following message is logged in
the SystemOut.log.
========================================
CWSIP0063I: The local destination sca/XXXModule with UUID
NNN has been marked for deletion.
========================================
(2) Cleanup task for "Destination A" is assigned to a separate
background thread AsynchDeletionThread.
(3) Due to large number of cleanup tasks piled up in
AsynchDeletionThread, it may take some time execute the
cleanup task for "Destination A".
(4) Meanwhile, "Destination A" is re created with same name
along with application re deployment and the destination name
is registered in WLM (Work Load Manager) as "Destination A".
(5) AsynchDeletionThread gets its turn to execute the cleanup
task for "Destination A". Clean up task deregisters the
"Destination A" from WLM. After deregister, "Destination A" is
unknown to WLM and hence the "Destination A" cannot be accessed
by an application.
In a working scenario, task (5) expected to be completed before
task(4).
The fix is not to delegate deregister task to a separate
background thread which might add minor delay in destination
deregister. Instead deregister the destination as soon as it
is being marked for deletion.
This APAR is applicable only if CWSIT0019E error has
"targetType=Destination" as one of the ME connection
properties.

Problem conclusion

Source code has been modified to deregister the destination
from WLM as soon as the destination removed from the
configuration.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.29, 8.0.0.6, and 8.5.0.2.

Please refer to the Recommended Updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM71953
Reported component name
WAS SIB & SIBWS
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-08-31
Closed date
2012-10-18
Last modified date
2013-02-28

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WAS SIB & SIBWS
Fixed component ID
620800101

Applicable component levels

R800 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021

Tips

PM71953: JMS APPLICATION RECEIVES CWSIT0019E ERROR THOUGH THE SERVICE INTEGRATION BUS MESSAGING ENGINE IS UP AND RUNNING

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R800 PSY

Document Information

Share your feedback

Need support?