| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Issue with WSRR cache notification |
« View previous topic :: View next topic » |
| Author |
Message
|
| krazzy4 |
 Posted: Thu Jan 03, 2013 11:50 pm Post subject: Issue with WSRR cache notification |
 |
|
Newbie
Joined: 15 Jan 2009
Posts: 1
|
Hi,
We are trying to setup WSRR cache notification. We are using WMB v8.0.0.1 and WSRR v7.0.0.5. We have followed the steps mentioned in WMB info centre. Below is the snapshot of the configuration done on the broker.
DefaultWSRR
connectionFactoryName='jms/SRConnectionFactory'
connectionTimeout='180'
enableCacheNotification='true'
endpointAddress=<http link of WSRR> initialContextFactory='com.ibm.websphere.naming.WsnInitialContextFactory'
locationJNDIBinding=<bindings link with iiop>
needCache='true'
predefinedCacheQueries=''
refreshQueriesAfterNotification='true'
subscriptionTopic='jms/SuccessTopic'
timeout='600000'
We are not getting any notifications after updating an artifact in WSRR. And the following error is displayed in event log.
]( MB8BROKER.Alico1 ) JMSClient.''CacheUpdate for WSRR Nodes'' The connection with the JMS provider could not start, or has closed for Initial Context factory ''url: <bindings link with iiop>
initial context factory: com.ibm.websphere.naming.WsnInitialContextFactory topic connection factory: jms/SRConnectionFactory topic: jms/SuccessTopic. This error has been output 1 time''. The node will try to re-establish the connection.
The JMS Connection with the JMS provider from this node has stopped. This could be due to the message flow stopping, or the connection could have ended abnormally because of a problem with the JMS provider.
The node tries to reconnect to the JMS provider, unless the message flow is shutting down. Check that the provider is available.
Not sure where the problem is. Any clues would be of great help.
Thank you. |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Fri Jan 04, 2013 5:52 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Since you don't use predefined queries, you might try setting needCache and refreshQueriesAfterNotification to false. This wont solve the root problem, but may get you a workaround till the PMR team has time to look at it.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| agrawalamit166 |
| Posted: Fri Jan 04, 2013 8:39 am Post subject: |
|
|
Voyager
Joined: 17 Aug 2009
Posts: 78
Location: NY, US
|
Please look this response message:
BIP4648
JMSClient.<insert_1> The connection with the JMS provider could not start, or has closed for Initial Context factory <insert_2>. The node will try to re-establish the connection.
Severity
20 : Error
Explanation
The JMS Connection with the JMS provider from this node has stopped. This could be due to the message flow stopping, or the connection could have ended abnormally because of a problem with the JMS provider.
Response
The node tries to reconnect to the JMS provider, unless the message flow is shutting down. Check that the provider is available. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Jan 04, 2013 8:43 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| 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
|
|
|
|
