Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Issue in NFT for SIB creation

SA-2968

Summary



Developers are facing issues while SIB creation. There are 2 jvm’s in a cluster, while creating SIB we need 1 messaging engine running on any servers and other should not attempt to connect to data store and fails over when we stop 1 server. Developers are not able to achieve this config. At the moment it runs on 1st server but tries to connect form 2nd server as well and gives errors.

Error Messages



Server01

[10/21/14 8:26:58:062 BST] 0000000d SibMessage I [epa_nft-ChordiantBusService:gbrdsr10336_wasadmin1.gbrdsr10336_wasadmin1-epa_nft-server01-epa_nft-ChordiantBusService] CWSIV0777I: A connection to messaging engine gbrdsr10336_wasadmin1.gbrdsr10336_wasadmin1-epa_nft-server01-epa_nft-ChordiantBusService for destination Default.Topic.Space on bus epa_nft-ChordiantBusService has been successfully created.


[10/21/14 8:26:58:063 BST] 0000000d SibMessage I [epa_nft-ChordiantBusService:gbrdsr10336_wasadmin1.gbrdsr10336_wasadmin1-epa_nft-server01-epa_nft-ChordiantBusService] CWSID0016I: Messaging engine gbrdsr10336_wasadmin1.gbrdsr10336_wasadmin1-epa_nft-server01-epa_nft-ChordiantBusService is in state Started.
javax.jms.JMSException: CWSIA0241E: An exception was received during the call to the method JmsManagedConnectionFactoryImpl.createConnection: com.ibm.websphere.sib.exception.SIResourceException: CWSIT0019E: No suitable messaging engine is available on bus epa_nft-ChordiantBusService that matched the specified connection properties {multicastInterface=none, connectionProximity=Bus, targetSignificance=Preferred, subscriptionProtocol=Unicast, targetType=BusMember, busName=epa_nft-ChordiantBusService}. Reason for failure: CWSIT0103E: No messaging engine was found that matched the following parameters: bus=epa_nft-ChordiantBusService, targetGroup=null, targetType=BusMember, targetSignificance=Preferred, transportChain=InboundSecureMessaging, proximity=Bus..
com.ibm.websphere.sib.exception.SIResourceException: CWSIT0019E: No suitable messaging engine is available on bus epa_nft-ChordiantBusService that matched the specified connection properties {multicastInterface=none, connectionProximity=Bus, targetSignificance=Preferred, subscriptionProtocol=Unicast, targetType=BusMember, busName=epa_nft-ChordiantBusService}. Reason for failure: CWSIT0103E: No messaging engine was found that matched the following parameters: bus=epa_nft-ChordiantBusService, targetGroup=null, targetType=BusMember, targetSignificance=Preferred, transportChain=InboundSecureMessaging, proximity=Bus.


Server02

[10/21/14 8:32:52:011 BST] 0000000a SibMessage I [epa_nft-ChordiantBusService:gbrdsr10336_wasadmin1.gbrdsr10336_wasadmin1-epa_nft-server02-epa_nft-ChordiantBusService] CWSID0016I: Messaging engine gbrdsr10336_wasadmin1.gbrdsr10336_wasadmin1-epa_nft-server02-epa_nft-ChordiantBusService is in state Joined.
[10/21/14 8:32:52:079 BST] 0000000d SibMessage I [epa_nft-ChordiantBusService:gbrdsr10336_wasadmin1.gbrdsr10336_wasadmin1-epa_nft-server02-epa_nft-ChordiantBusService] CWSID0016I: Messaging engine gbrdsr10336_wasadmin1.gbrdsr10336_wasadmin1-epa_nft-server02-epa_nft-ChordiantBusService is in state Starting.
[10/21/14 8:32:53:297 BST] 00000010 SibMessage I [epa_nft-ChordiantBusService:gbrdsr10336_wasadmin1.gbrdsr10336_wasadmin1-epa_nft-server02-epa_nft-ChordiantBusService] CWSIS1538I: The messaging engine, ME_UUID=8DB9101393D1A2B7, INC_UUID=312A312A319F71B0, is attempting to obtain an exclusive lock on the data store.
[10/21/14 8:32:58:304 BST] 00000010 SibMessage I [epa_nft-ChordiantBusService:gbrdsr10336_wasadmin1.gbrdsr10336_wasadmin1-epa_nft-server02-epa_nft-ChordiantBusService] CWSIS1593I: The messaging engine, ME_UUID=8DB9101393D1A2B7, INC_UUID=312A312A319F71B0, has failed to gain an initial lock on the data store.


javax.jms.JMSException: CWSIA0241E: An exception was received during the call to the method JmsManagedConnectionFactoryImpl.createConnection: com.ibm.websphere.sib.exception.SIResourceException: CWSIT0088E: There are currently no messaging engines in bus epa_nft-ChordiantBusService running. Additional failure information: CWSIT0103E: No messaging engine was found that matched the following parameters: bus=epa_nft-ChordiantBusService, targetGroup=null, targetType=BusMember, targetSignificance=Preferred, transportChain=InboundSecureMessaging, proximity=Bus..
at com.ibm.ws.sib.api.jms.impl.JmsManagedConnectionFactoryImpl.createConnection(JmsManagedConnectionFactoryImpl.java:198)
at com.ibm.ws.sib.api.jms.impl.JmsManagedTopicConnectionFactoryImpl.createTopicConnection(JmsManagedTopicConnectionFactoryImpl.java:87)
at com.ibm.ws.sib.api.jms.impl.JmsManagedTopicConnectionFactoryImpl.createTopicConnection(JmsManagedTopicConnectionFactoryImpl.java:76)
at com.chordiant.userprofile.server.CacheMgr.setup(Unknown Source)
at com.chordiant.userprofile.server.CacheMgr.serviceControl(Unknown Source)
at com.chordiant.core.customobjects.CustomObjectsHelper.run(Unknown Source)
at java.lang.Thread.run(Thread.java:761)
Caused by:
com.ibm.websphere.sib.exception.SIResourceException: CWSIT0088E: There are currently no messaging engines in bus epa_nft-ChordiantBusService running. Additional failure information: CWSIT0103E: No messaging engine was found that matched the following parameters: bus=epa_nft-ChordiantBusService, targetGroup=null, targetType=BusMember, targetSignificance=Preferred, transportChain=InboundSecureMessaging, proximity=Bus.


Steps to Reproduce



Configuring SIB in clustered environment


Root Cause



The issue is with the environment. Following messages were observed in logs:

1. 
HMGR0005I This message indicates that the high availability manager is disabled because the high availability manager communication transport can only establish communication with a single server process.

2. [10/22/14 13:19:12:559 BST] 00000035 SystemOut     O 2014-10-22 13:19:12,558 [CustomObjectsHelper delayed setup thread] WARN   com.ibm.ws.sib.api.jms.impl.JmsManagedConnectionFactoryImpl - JMS is not setup to support cluster-aware caching.
javax.jms.JMSException: CWSIA0241E: An exception was received during the call to the method JmsManagedConnectionFactoryImpl.createConnection: com.ibm.websphere.sib.exception.SIResourceException: CWSIT0019E: No suitable messaging engine is available on bus epa_nft-ChordiantBusService that matched the specified connection properties {multicastInterface=none, connectionProximity=Bus, targetSignificance=Preferred, subscriptionProtocol=Unicast, targetType=BusMember, busName=epa_nft-ChordiantBusService}. Reason for failure: CWSIT0103E: No messaging engine was found that matched the following parameters: bus=epa_nft-ChordiantBusService, targetGroup=null, targetType=BusMember, targetSignificance=Preferred, transportChain=InboundSecureMessaging, proximity=Bus..

Resolution



1. For 
HMGR0005I, enable the High Availability manager by checking Enable service at server startup under Application servers >{servername}> Core group service
2. For CWSIA0241E, CWSIT0019E, CWSIT0103E: Clear the SIB tables and restart
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us