| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Multiple broker connections to a single JMS queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| TonyD |
 Posted: Tue Dec 16, 2008 3:00 pm Post subject: Multiple broker connections to a single JMS queue |
 |
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
We have a number of message flows that read JMS queues. The JMS queues are remote WAS SIB queues. The flows, some with multiple instances, are in a single execution group, and connect satisfactorily at broker startup.
We have now added a second execution group and deployed the JMS queue-reading flows to it for added capacity. However we are now getting JMS connection errors from the first execution group flows.
Does anyone know if there is a restriction against having multiple broker JMS clients reading the same queue? I am thinking that the instances of a flow in the first execution group share one connection, and that the second execution group initiates a second connection to each of the JMS queues in question. |
|
| Back to top |
|
 |
| AkankshA |
| Posted: Tue Dec 16, 2008 7:49 pm Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
can you please paste the error here...
i remember facing a similar problem with weblogic server some time back but the actual cause turned out to be limiting the number of connections at webslogic server and not wrt WMB...
_________________
Cheers |
|
| Back to top |
|
|
| TonyD |
| Posted: Wed Dec 17, 2008 11:57 am Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
| Code: |
Dec 17 10:22:37 eqcigs61 WebSphere Broker v6008[27550]: (TRN_BKR01.CMS_01)[1322834848]BIP4367E: The method 'run' in Java node 'eventRequest' has thrown the following exception: com
.ibm.websphere.sib.exception.SIErrorException: CWSIC8007E: An exception was caught from the remote server with Probe Id 3-016-0011. Exception: null.. : TRN_BKR01.804eb297-1901-0000
-0080-90144758e0ee: /build/S600_P/src/DataFlowEngine/PluginInterface/com_ibm_broker_plugin_CMbService.cpp: 1634: ImbJavaExceptionUtils::throwableToNativeException: :
Dec 17 10:22:37 eqcigs61 WebSphere Broker v6008[27550]: (TRN_BKR01.CMS_01)[1322834848]BIP4395E: Java exception: 'com.ibm.websphere.sib.exception.SIErrorException'; thrown from clas
s name: 'com.ibm.ws.sib.comms.common.JFAPCommunicator', method name: 'parseSingleException', file: 'JFAPCommunicator.java', line: '1801' : TRN_BKR01.804eb297-1901-0000-0080-9014475
8e0ee: /build/S600_P/src/DataFlowEngine/PluginInterface/com_ibm_broker_plugin_CMbService.cpp: 1652: ImbJavaExceptionUtils::throwableToNativeException: :
|
This is an example ... fairly meaningless to me! This pair of messages occurred for each flow in the existing eg (CMS_01) that was deployed in the new eg (which was called CMS_02).
We added the new eg, deployed the flows to it, and they successfully connected to their input queues. The already-connected flows in eg CMS_01 then objected and threw the error messages shown above ... very odd! The errors went away when we stopped the flows in the new eg.
Will investigate whether there is a connection limit set in WAS. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
