2 Replies Latest reply on Apr 8, 2011 4:16 AM by Aslak Knutsen

    Problems running Alpha5 with Seam JMS

    John Ament Master

      So I've run into a bunch of errors while trying to run alpha 5.  I think some of them are shrinkwrap issues, and some are arquillian issues.

       

      1. Packaged hornetq-jms.xml is not being picked up by the app server.

      I have the following code in my test case

      war.addAsManifestResource(HORNETQ_JMS_DEPLOYMENT_CONFIG);

      (previously, it was adManifestResource).  the config file points to our src/test/resources-jbossas6/hornetq-jms.xml

       

      2. Attached is a log file that occurs with some tests, but not all.  I'm sort of at a loss, because this shouldn't be in my war file

       

      3. Pretty much every execution results in the following being printed to threadDump.log

      Unable to get server thread dump: java.lang.ClassCastException: javax.naming.Reference cannot be cast to javax.management.MBeanServerConnection

          at org.jboss.jbossas.servermanager.Server.getServerConnection(Server.java:666)

          at org.jboss.jbossas.servermanager.Server.listThreadDump(Server.java:706)

          at org.jboss.jbossas.servermanager.ServerController.writeServerDump(ServerController.java:522)

          at org.jboss.jbossas.servermanager.ServerController.stopServer(ServerController.java:470)

          at org.jboss.jbossas.servermanager.ServerManager$1.run(ServerManager.java:80)

       

      I compared my dependencies to the cdi example in Dan's branch of the showcase, and they don't look all that different

        • 1. Problems running Alpha5 with Seam JMS
          Aslak Knutsen Master

          John Ament wrote:

           

          2. Attached is a log file that occurs with some tests, but not all.  I'm sort of at a loss, because this shouldn't be in my war file

          If your refering to the Stacktraces related to org.jboss.deployers.plugins.managed.BeanMetaDataICF, they are just DEBUG. It's basically the ManagmentView saying that something has ben bound to it it can't parse or similar. This should no effect the deployment itself.

           

           

          John Ament wrote:

           

          3. Pretty much every execution results in the following being printed to threadDump.log

          Unable to get server thread dump: java.lang.ClassCastException: javax.naming.Reference cannot be cast to javax.management.MBeanServerConnection

              at org.jboss.jbossas.servermanager.Server.getServerConnection(Server.java:666)

              at org.jboss.jbossas.servermanager.Server.listThreadDump(Server.java:706)

              at org.jboss.jbossas.servermanager.ServerController.writeServerDump(ServerController.java:522)

              at org.jboss.jbossas.servermanager.ServerController.stopServer(ServerController.java:470)

              at org.jboss.jbossas.servermanager.ServerManager$1.run(ServerManager.java:80)

           

          I compared my dependencies to the cdi example in Dan's branch of the showcase, and they don't look all that different

          This sounds like a Dependency issue. It's missing some jndi/mbean related lib.

          • 2. Re: Problems running Alpha5 with Seam JMS
            Aslak Knutsen Master

            John Ament wrote:

             

            So I've run into a bunch of errors while trying to run alpha 5.  I think some of them are shrinkwrap issues, and some are arquillian issues.

             

            1. Packaged hornetq-jms.xml is not being picked up by the app server.

            I have the following code in my test case

            war.addAsManifestResource(HORNETQ_JMS_DEPLOYMENT_CONFIG);

            (previously, it was adManifestResource).  the config file points to our src/test/resources-jbossas6/hornetq-jms.xml

            addAsManifestResource is mapped to /META-INF in SW Alpha-12, you need to use addAsResource(HORNETQ_JMS_DEPLOYMENT_CONFIG, "META-INF/hornetq-jms-xml") which should end up in /WEB-INF/classes/META-INF/hornetq...