6 Replies Latest reply on Aug 30, 2007 6:08 AM by Mark Little

    JBoss and ESB

    Nikolay Newbie

      I use this document for install jbossesb-4.0GA into jboss-4.2.1.GA
      http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/docs/GettingStarted.pdf
      Example Hello Word - ok!!!

      But, I have some problem
      telnet localhost 1099 --> OK
      telnet 192.168.168.2 1099 --> not open
      I've read in this forum that I must start JBoss
      run.bat -c default --host=192.168.168.2
      After that I get problem whit ESB.Please, Help me and Sorry for my English.


      2007-08-27 18:18:36,578 DEBUG [org.jboss.internal.soa.esb.dependencies.JuddiRMIService] Starting jbo
      ss.org:service=JuddiRMI
      2007-08-27 18:18:36,578 INFO [org.jboss.internal.soa.esb.dependencies.JuddiRMIService] starting jud
      di RMI service
      2007-08-27 18:18:37,531 DEBUG [org.jnp.interfaces.NamingContext] Failed to connect to localhost:1099

      javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is j
      avax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception
      is java.net.ConnectException: Connection refused: connect]]
      at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269)
      at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1387)
      at org.jnp.interfaces.NamingContext.bind(NamingContext.java:539)
      at org.jnp.interfaces.NamingContext.bind(NamingContext.java:532)
      at javax.naming.InitialContext.bind(InitialContext.java:359)
      at org.apache.juddi.registry.rmi.JNDIRegistration.register(JNDIRegistration.java:78)
      at org.jboss.internal.soa.esb.dependencies.JuddiRMIService.startService(JuddiRMIService.java:23)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
      at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:417)


        • 1. Re: JBoss and ESB
          Tom Fennelly Master

          Hi.

          JBossESB 4.0GA will not run on JBossAS 4.2.x. It will only run on JBossAS 4.0.x.

          I would point out that we're about to release 4.2GA (end of this month), which has many improvements on the 4.0 GA release.

          • 2. Re: JBoss and ESB
            Nikolay Newbie

            Ok!!! I understand, but it's very strange, because example hello word is working.

            • 3. Re: JBoss and ESB
              hai wu Newbie

              I just encountered the same problem, with JBossESB 4.2 M3, running on JBoss AS 4.2.1GA. I have to change every place in configuration file where it says localhost:1099 to hostname:1099.

              After doing that HelloWorld is working, but still in server.log file, it shows some error messages as follows:
              2007-08-30 00:19:21,527 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Exiting on IOE
              java.net.SocketException: Socket closed
              at java.net.SocketInputStream.read(SocketInputStream.java:162)
              at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
              at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
              at org.jboss.util.stream.NotifyingBufferedInputStream.read(NotifyingBufferedInputStream.java:79)
              at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2196)
              at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2376)
              at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2443)
              at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2515)
              at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2664)
              at java.io.ObjectInputStream.readByte(ObjectInputStream.java:875)
              at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:316)
              at java.lang.Thread.run(Thread.java:595)
              2007-08-30 00:19:21,528 DEBUG [org.jboss.mq.il.uil2.SocketManager] End ReadTask.run
              2007-08-30 00:19:21,530 DEBUG [org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool] Creating a new Queue session.
              2007-08-30 00:19:21,530 DEBUG [org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool] Number of Sessions in the pool now is 3
              2007-08-30 00:19:21,531 DEBUG [org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool] Returning session, poolsize=3, maxsize=20, number of pools=2
              2007-08-30 00:19:21,533 DEBUG [org.jboss.mq.referenceable.SpyDestinationObjectFactory] SpyDestinationObjectFactory->getObjectInstance()
              2007-08-30 00:19:21,527 DEBUG [org.jboss.mq.il.uil2.SocketManager] Failed to handle: org.jboss.mq.il.uil2.msgs.CloseMsg33541591[msgType: m_connectionClosing, msgID: 8, erro
              r: null]
              java.io.IOException: Client is not connected
              at org.jboss.mq.il.uil2.SocketManager.internalSendMessage(SocketManager.java:264)
              at org.jboss.mq.il.uil2.SocketManager.sendReply(SocketManager.java:238)
              at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:134)
              at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:395)
              at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:398)
              at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
              at java.lang.Thread.run(Thread.java:595)
              2007-08-30 00:19:21,548 DEBUG [org.jboss.mq.il.uil2.SocketManager] Failed to send error reply
              java.io.IOException: Client is not connected
              at org.jboss.mq.il.uil2.SocketManager.internalSendMessage(SocketManager.java:264)
              at org.jboss.mq.il.uil2.SocketManager.access$800(SocketManager.java:53)
              at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:408)
              at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:398)
              at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
              at java.lang.Thread.run(Thread.java:595)
              2007-08-30 00:19:21,549 DEBUG [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] pipeline process for message
              2007-08-30 00:19:21,549 DEBUG [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] executing processor 0
              2007-08-30 00:19:21,549 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
              2007-08-30 00:19:21,550 INFO [STDOUT] Body: Hello World
              2007-08-30 00:19:21,550 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
              2007-08-30 00:19:23,692 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] Periodic recovery - second pass <Thu, 30 Aug 2007 00:19:23>
              2007-08-30 00:19:23,692 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] AtomicActionRecoveryModule: Second pass
              2007-08-30 00:19:23,692 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_6] - TORecoveryModule - second pass
              2007-08-30 00:19:23,692 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.secondpass] Local XARecoveryModule - second pass
              2007-08-30 00:20:06,667 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] run: IdleRemover notifying pools, interval: 450000


              Is this normal?
              Thanks,
              Hai

              • 4. Re: JBoss and ESB
                hai wu Newbie

                Forgot to mention the above errors were encountered after running "ant runtest", and I have to modify the source code for file 'src/org/jboss/soa/esb/samples/quickstart/helloworld/test/SendJMSMessage.java'.

                The "Hello World" shows up, but with the above error messages mentioned before.

                Please advice,

                • 5. Re: JBoss and ESB
                  Kevin Conner Master

                   

                  "haiwu.us@gmail.com" wrote:
                  I have to change every place in configuration file where it says localhost:1099 to hostname:1099.

                  This is something we are working on, there are two tasks covering it.

                  http://jira.jboss.com/jira/browse/JBESB-832, which will handle property substitution and http://jira.jboss.com/jira/browse/JBESB-871, which will handle configuration via the ServiceBindingManager.


                  "haiwu.us@gmail.com" wrote:
                  After doing that HelloWorld is working, but still in server.log file, it shows some error messages as follows:
                  2007-08-30 00:19:21,527 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Exiting on IOE
                  java.net.SocketException: Socket closed


                  This is generated by the JMS subsystem and is caused when the client connection has unexpectedly closed. There have been recent changes which should now close the client connection cleanly, these will be in the GA release.


                  • 6. Re: JBoss and ESB
                    Mark Little Master

                    Plus you can safely ignore anything to do with recovery unless you're using transactions.