MDB Node already removed Exception

Discussions

EJB programming & troubleshooting: MDB Node already removed Exception

  1. MDB Node already removed Exception (1 messages)

    We have MDBs deployed in Websphere processing messages from the Websphere MQ queues. We have noticed strange behaviour that sometimes, the message listener associated with the MDB goes down automatically and after that we see messages like below. It gets rectified only after a WAS restart. IBM has pointed out as coding issue. Has anyone seen such an error in MDBs, if yes, how can we correct this node already removed error. is it some problem with transaction handling inside MDB? Thanks, ************************************ [11/4/07 1:17:23:069 PDT] 00000030 SystemOut O 4731 [MessageListenerThreadPool : 3] ERROR com.nordstrom.sis.dtclistener.ejb.TransferUpdateListenerDupOneBean - java.lang.IllegalStateException: Node already removed. [11/4/07 1:17:23:099 PDT] 00000036 SystemOut O 4761 [MessageListenerThreadPool : 5] ERROR com.nordstrom.sis.dtclistener.ejb.CreateListenerBean - java.lang.IllegalStateException: Node already removed. [11/4/07 1:17:23:144 PDT] 00000036 ServerSession W WMSG0031E: Exception processing JMS Message for MDB CreateListener, JMSDestination jms/SF.TRANSFERSDTCQUERY.REQ : javax.ejb.EJBException: See nested exception; nested exception is: java.lang.RuntimeException: java.lang.IllegalStateException: Node already removed. java.lang.RuntimeException: java.lang.IllegalStateException: Node already removed. at com.nordstrom.sis.dtclistener.ejb.CreateListenerBean.ejbCreate(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.ibm.ejs.container.MessageDrivenBeanO.(MessageDrivenBeanO.java:149) at com.ibm.ejs.container.CMMessageDrivenBeanO.(CMMessageDrivenBeanO.java:70) at com.ibm.ejs.container.CMMessageDrivenBeanOFactory.create(CMMessageDrivenBeanOFactory.java:39) at com.ibm.ejs.container.EJSHome.createBeanO(EJSHome.java:912) at com.ibm.ejs.container.EJSHome.createBeanO(EJSHome.java:1015) at com.ibm.ejs.container.activator.UncachedActivationStrategy.atActivate(UncachedActivationStrategy.java:83) at com.ibm.ejs.container.activator.Activator.activateBean(Activator.java:595) at com.ibm.ejs.container.EJSContainer.preInvokeActivate(EJSContainer.java:3439) at com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java:2836) at com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java:2764) at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:87) at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:127)

    Threaded Messages (1)

  2. please reply[ Go to top ]

    Has nobody experienced this kind of exception. Is this pretty common in EJBs?