Author |
Message
|
mb8_learner |
Posted: Mon Jun 18, 2018 12:35 pm Post subject: IIB 10: JMS Connectivity Issue |
|
|
Novice
Joined: 28 May 2013 Posts: 22
|
we are connecting to tibco queue through JMS nodes. when the TIBCO servers got restarted, our flow isnt re-establishing the connection. Even in tibco queue we arent able to see any readers. if we restarted the flow, again the flow is establishing the connection.
Did anyone faced the same issue. Any fix for this. |
|
Back to top |
|
 |
abhi_thri |
Posted: Tue Jun 19, 2018 12:14 am Post subject: |
|
|
Master
Joined: 17 Jul 2017 Posts: 242 Location: UK
|
it is a known issue
Quote: |
Description of problem: A JMS input node does not attempt to reconnect to a JMS provider following a connection failure, or a restart of the JMS provider.
Corrective action: If the JMS provider is implemented by using a model that pushes on the JMS client, rather than a traditional polling model, the JMS provider might not throw an exception when calling receive() on a broker connection. To resolve this problem, set the jmsAsyncExceptionHandling property of the JMSProviders configurable service to true for this JMS provider.
|
|
|
Back to top |
|
 |
mb8_learner |
Posted: Thu Jul 12, 2018 11:18 am Post subject: |
|
|
Novice
Joined: 28 May 2013 Posts: 22
|
do you raised any PMR for this or any other details on this issue.
When we tried to recreate the issue, we aren't able to recreate it. so we arent able to provide much information for this PMR. so we are struck |
|
Back to top |
|
 |
Vitor |
Posted: Thu Jul 12, 2018 11:29 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 25464 Location: Ohio, USA
|
mb8_learner wrote: |
do you raised any PMR for this or any other details on this issue. |
If the problem's described in the product documentation, I don't think you need a PMR to tell IBM about it. Or to find out what their suggested course of action is.
 _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|