5 Replies Latest reply on Jan 28, 2016 9:44 AM by jbertram

    Problem by sending a JMS

    erlaunis

      Hi, I'm working on an application made 10 years ago. The developpers have used JBoss 6.1.0 but now, I want to use JBoss 7.1.0. I have a problem with a JMS sending. Actually, the program stops when it tries to send a JMS message. It says :

       

      12:20:07,221 DEBUG JmsMessageProducer:65 - Create Jndi Context with :java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory java.naming.provider.url=jnp://localhost:1099

      12:20:07,224 DEBUG JmsMessageProducer:71 - Create connexion factory :ConnectionFactory

      12:20:07,231 DEBUG TimedSocketFactory:87 - createSocket, hostAddr: localhost/127.0.0.1, port: 1099, localAddr: null, localPort: 0, timeout: 0

      12:20:08,235 TRACE NamingContext:336 - Failed to connect server localhost/127.0.0.1:1099

      javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused: connect]

              at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:307)

              at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1746)

              at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:695)

              at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:688)

              at javax.naming.InitialContext.lookup(InitialContext.java:411)

              at fr.inra.grignon.persyst.web.jms.JmsMessageProducer.sendJmsTextMessage(JmsMessageProducer.java:72)

              at fr.inra.grignon.persyst.web.servlet.DoResultats.doPost(DoResultats.java:407)

              at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)

              at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)

              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)

              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)

              at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)

              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)

              at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)

              at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)

              at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:44)

              at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)

              at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)

              at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)

              at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:957)

              at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)

              at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:423)

              at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1079)

              at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:620)

              at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

              at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

              at java.lang.Thread.run(Thread.java:745)

      Caused by: java.net.ConnectException: Connection refused: connect

              at java.net.DualStackPlainSocketImpl.connect0(Native Method)

              at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)

              at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)

              at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)

              at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)

              at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)

              at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)

              at java.net.Socket.connect(Socket.java:579)

              at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97)

              at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82)

              at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:303)

              ... 29 more

      12:20:08,276 DEBUG NamingContext:1751 - Failed to connect to localhost:1099

      javax.naming.CommunicationException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]

              at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:337)

              at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1746)

              at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:695)

              at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:688)

              at javax.naming.InitialContext.lookup(InitialContext.java:411)

              at fr.inra.grignon.persyst.web.jms.JmsMessageProducer.sendJmsTextMessage(JmsMessageProducer.java:72)

              at fr.inra.grignon.persyst.web.servlet.DoResultats.doPost(DoResultats.java:407)

              at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)

              at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)

              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)

              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)

              at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)

              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)

              at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)

              at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)

              at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:44)

              at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)

              at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)

              at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)

              at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:957)

              at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)

              at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:423)

              at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1079)

              at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:620)

              at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

              at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

              at java.lang.Thread.run(Thread.java:745)

       

       

      I think that this error comes from JBoss and because I'm using an other version. In the pom.xml of the project, I have <version.org.jboss.jbossas>6.1.0.Final</version.org.jboss.jbossas> and when I want to build it with 7.1.0, it doesn't work.

      Moreover, when I connect to JBoss 7.1, it works.

       

      I don't know what is the problem, if it's because of the version or maybe my configs are not correct.

       

      Can anyone help me to resolve this please ?

        • 1. Re: Problem by sending a JMS
          jaysensharma

          JBossas7 does not use the JNP protocol (unlike JBossAS6). Similarly the JNDI naming factory is changed to:

          JNDI_FACTORY="org.jboss.naming.remote.client.InitialContextFactory"

           

          Please have a look at the JBossAS7 base article for sending and receiving JMS messages to / from JMS queue:

           

          How to connect to a remote queue in JBoss AS 7 ?

          http://middlewaremagic.com/jboss/?p=1616

           

          Regards

          Jay SenSharma

          • 2. Re: Problem by sending a JMS
            erlaunis

            Thanks for your reply.

             

            So, if I understand, I can't use JBossas7 with this method. I need to use JBoss6 or change the configs with your link. As the application is already developped, what do you advise me ?

             

            Thanks,

            Lison Rousseaux

            • 3. Re: Problem by sending a JMS
              jbertram

              In my opinion, it's not really possible to provide you with any meaningful recommendations when you've provided only a couple of details about your application.

              • 4. Re: Problem by sending a JMS
                erlaunis

                I know, but as I'm a beginner, I don't really know what is important or not. If you want any information, be free to ask because for now, I don't really know what to do, I'm a little lost in J2EE :/ And I need to solve that thing before beginning to developp. It's been 5 months that I try to resolve exceptions like that by my own and there's always an other one after. It never ends !  

                 

                Anyway, thanks for your reply

                • 5. Re: Problem by sending a JMS
                  jbertram

                  If you're lost in Java EE and you don't know what's important with your application's environment and development then you need more help than what you can reasonably expect to get on a community forum.

                   

                  You might consider moving to JBoss EAP and getting a support subscription from Red Hat so you can get the kind of help you really need.  To be clear, JBoss EAP 6 is based on the community release of JBoss Application Server 7.