4 Replies Latest reply on May 9, 2003 1:43 AM by Sergey Tavanets

    Problem with JMS in JBoss 3.2.0

    Sergey Tavanets Newbie

      Hi!
      I am occasionally getting the following exception:
      java.lang.IncompatibleClassChangeError
      at org.jboss.mq.security.SecurityManager$SubjectInfo.toString(SecurityManager.java:61)
      at org.jboss.mq.security.SecurityManager.authorize(SecurityManager.java:204)
      at org.jboss.mq.security.ServerSecurityInterceptor.authorizeRead(ServerSecurityInterceptor.java:216)
      at org.jboss.mq.security.ServerSecurityInterceptor.receive(ServerSecurityInterceptor.java:99)
      at org.jboss.mq.server.TracingInterceptor.receive(TracingInterceptor.java:486)
      at org.jboss.mq.server.JMSServerInvoker.receive(JMSServerInvoker.java:227)
      at org.jboss.mq.il.jvm.JVMServerIL.receive(JVMServerIL.java:245)
      at org.jboss.mq.Connection.receive(Connection.java:1166)
      at org.jboss.mq.SpyMessageConsumer.receive(SpyMessageConsumer.java:266)
      at com.vocognition.talkface.jms.JMSModel.waitForReplyTo(JMSModel.java:94)
      at com.vocognition.talkface.talkman.LUTHandler.service(LUTHandler.java:36)
      at com.vocognition.talkface.protocol.tfshttp.JMSServlet.doGet(JMSServlet.java:146)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
      at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:360)
      at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294)
      at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:558)
      at org.mortbay.http.HttpContext.handle(HttpContext.java:1714)
      at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:507)
      at org.mortbay.http.HttpContext.handle(HttpContext.java:1664)
      at org.mortbay.http.HttpServer.service(HttpServer.java:863)
      at org.jboss.jetty.Jetty.service(Jetty.java:460)
      at org.mortbay.http.HttpConnection.service(HttpConnection.java:775)
      at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:939)
      at org.mortbay.http.HttpConnection.handle(HttpConnection.java:792)
      at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:201)
      at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
      at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:455)

      Does anyone know what it means?

      Regards,

      Sergey.

        • 1. Re: Problem with JMS in JBoss 3.2.0
          Adrian Brock Master

          Can you post the details as a bug
          on www.sf.net.

          Include the jboss version, vm version, OS
          and any other useful information.

          If you can create a simple testcase that reproduces
          this that would be good too otherwise
          some details about what this part of application does.

          Do you have TRACE enabled?


          Regards,
          Adrian

          • 2. Re: Problem with JMS in JBoss 3.2.0
            Sergey Tavanets Newbie

            Just to let you know that the problem is not present in JBoss 3.2.1
            However there is still a problem that sometimes queues do not give messages out when requested. The idea now is that it happens when there are multiple MDB's are bound to one queue using different MessageSelectors. I will post the detail when I properly investigate the problem.

            Sergey.

            • 3. Re: Problem with JMS in JBoss 3.2.0
              Sergey Tavanets Newbie

              Just to let you know that the problem is not present in JBoss 3.2.1
              However there is still a problem that sometimes queues do not give messages out when requested. The idea now is that it happens when there are multiple MDB's are bound to one queue using different MessageSelectors. I will post the detail when I properly investigate the problem.

              Sergey.

              • 4. Re: Problem with JMS in JBoss 3.2.0
                Sergey Tavanets Newbie

                Just to let you know that the problem is not present in JBoss 3.2.1
                However there is still a problem that sometimes queues do not give messages out when requested. The idea now is that it happens when there are multiple MDB's are bound to one queue using different MessageSelectors. I will post the detail when I properly investigate the problem.

                Sergey.