Posted: Wed Oct 12, 2011 9:58 pm Post subject: JMS input node error after DB refresh
Newbie
Joined: 06 Dec 2010 Posts: 6
Hi,
My client has an application with a JMS input node which receives DB row change event through LDAP into JMS input node. The database gets a daily refresh from Production environment and after each refresh, the JMS input node gets connection errors which only resolves after manual execution group restart. Is this an expected behaviour or have I missed some configuration? Or maybe the DB team needs to do something before they shut down DB?
The exception message shows as below in the system log:
Oct 13 14:54:09 esbtesta WebSphere Broker v7001[17764]: (ESBUAT.ADP-CASS-CDC)[5]BIP4643E: WMB JMSClient.'Broker 'ESBUAT'; Execution Group 'ADP-CASS-CDC'; Message Flow 'CASPRD_CDC_Connector'; Node 'ComIbmJMSClientInputNode::CASS_PROD_CONNECTION' '. Error Receiving JMS Message. If Available the text from the JMS Exception is ''. : ESBUAT.ed39a264-3101-0000-0080-ba355f884807: JMSClientErrors.java: 626: JMSClientInputNode::run(): :
Done. _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
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