1 Reply Latest reply on Jul 15, 2002 11:55 PM by Hiram Chirino

    [ More ] Exception in JMSCI message listener

    Vinay Menon Newbie

      Hello,
      I can see loads of the following stack traces in the JBoss server log which I believe are to do with message driven beans...

      [19:18:22,399,JAWSPersistenceManager] Set parameter: idx=1, jdbcType=BIGINT, value=1
      [19:18:22,402,JMSContainerInvoker] Exception in JMSCI message listener
      java.rmi.ServerException: Bean exception. Notify the application administrator; nested exception is:
      javax.ejb.EJBException: null
      javax.ejb.EJBException: null
      at uk.co.isesolutions.apps.imacs.util.listener.InterceptorListener.onMessage (pc 137)
      at java.lang.reflect.Method.invoke (Method.java)
      at org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke (MessageDrivenContainer.java:406) (pc 53)
      at org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor.invoke (MessageDrivenInstanceInterceptor.java:81) (pc 25)
      at org.jboss.ejb.plugins.TxInterceptorCMT.invokeNext (TxInterceptorCMT.java:138) (pc 9)
      at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions (TxInterceptorCMT.java:279) (pc 269)
      at org.jboss.ejb.plugins.TxInterceptorCMT.invoke (TxInterceptorCMT.java:100) (pc 3)
      at org.jboss.ejb.plugins.SecurityInterceptor.invoke (SecurityInterceptor.java:127) (pc 25)
      at org.jboss.ejb.plugins.LogInterceptor.invoke (LogInterceptor.java:170) (pc 152)
      at org.jboss.ejb.MessageDrivenContainer.invoke (MessageDrivenContainer.java:281) (pc 5)
      at org.jboss.ejb.plugins.jms.JMSContainerInvoker.invoke (JMSContainerInvoker.java:584) (pc 45)
      at org.jboss.ejb.plugins.jms.JMSContainerInvoker$MessageListenerImpl.onMessage (JMSContainerInvoker.java:930) (pc 117)
      at org.jboss.jms.asf.StdServerSession.onMessage (StdServerSession.java:233) (pc 203)
      at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage (SpyMessageConsumer.java:565) (pc 139)
      at org.jboss.mq.SpyMessageConsumer.addMessage (SpyMessageConsumer.java:376) (pc 61)
      at org.jboss.mq.SpySession.run (SpySession.java:248) (pc 56)
      at org.jboss.jms.asf.StdServerSession.run (StdServerSession.java:172) (pc 28)
      at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run (PooledExecutor.java:725) (pc 15)
      at java.lang.Thread.run (Thread.java:479) (pc 11)


      The ejb-jar segement relating to this bean is

      <ejb-name>uk.co.isesolutions.apps.imacs.util.listener.InterceptorListener</ejb-name>
      <ejb-class>uk.co.isesolutions.apps.imacs.util.listener.InterceptorListener</ejb-class>
      <message-selector>FOR = 'INTERCEPTORLISTENER'</message-selector>
      <transaction-type>Container</transaction-type>
      <acknowledge-mode>Auto-acknowledge</acknowledge-mode>
      <message-driven-destination>
      <destination-type>javax.jms.Queue</destination-type>
      </message-driven-destination>

      Have seen a few posts related to this and was wondering if there is any understanding as to why this could be happening?

      Many thanks

      Vinay