1 Reply Latest reply on May 4, 2010 10:04 AM by Ron Olson

    Configuring JBoss/ESB to work with different ports

    Ron Olson Newbie

      HI all-


      I need to have JBossESB 4.8 live side-by-side with an existing instance of JBoss 4.2.3. I started with a brand new instance of 4.8, copied the "default" directory to "default_8880" and started updating the various configuration files. I changed




      in deploy/jboss-web.deployer/server.xml









      in conf/jboss-service.xml




      in deploy/http-invoker.sar/META-INF/jboss-service.xml


      I verified that these ports were unavailable via netstat -an as well as telnet localhost <port>. All ports are not being used by another program.


      The errors I'm seeing in the server.log file are repetitions of:


      2010-05-03 16:17:03,848 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_      3_GA date=200807181417)] Started in 1m:37s:850ms
      2010-05-03 16:17:07,453 INFO  [org.jboss.soa.esb.listeners.message.MessageAwareListener] State reached : false
      2010-05-03 16:17:07,476 INFO  [org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool] Received NamingException, re      freshing context.
      2010-05-03 16:17:08,504 DEBUG [org.jboss.soa.esb.listeners.message.MessageAwareListener] Courier Exception
      org.jboss.soa.esb.couriers.CourierException: Unable to create Message Consumer
      at org.jboss.internal.soa.esb.couriers.JmsCourier.internalPickupPayload(JmsCourier.java:497)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:465)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:458)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:228)
      at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:204)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:297)
      at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:253)
      at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:1      15)
      at java.lang.Thread.run(Thread.java:595)
      Caused by: org.jboss.soa.esb.couriers.CourierServiceBindException: Failed to get JMS Session from pool.
      at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:161)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageConsumer(JmsCourier.java:580)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.internalPickupPayload(JmsCourier.java:489)
      ... 8 more
      Caused by: javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: error unmarshalling return      ; nested exception is:
      java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.mq.referenceable.ObjectRefAddr (no security ma      nager: RMI class loader disabled)]


      Okay, so there's an RMI issue. I get this on both my local machine as well as the remote server I'm trying to deploy it to. If I'm running it on my local machine, with no other JBoss instance running, I get the error, but when I run the "default" server, it works fine.


      It would seem I messed something up in the configuration somewhere; I've searched high and low and there seems to be no one specific way to configure the server to coexist with another JBoss server.


      Might anyone have any ideas what I can do to resolve this?