0 Replies Latest reply on Jul 21, 2009 5:29 AM by Spongebob Squarepants

    NAT problem after migration from JBoss 4.0.5 to 4.2.3

    Spongebob Squarepants Newbie

      Hi everyone,

      as mentioned above I have a problem with NAT after migrating JBoss from
      version 4.0.5.GA to 4.2.3.GA. Our JBoss specialist has retired recently and
      I am the lucky guy who had to take over.

      With help of his documentation and a little help from www.jboss.org and
      google, I managed to migrate the existing configuration of our JBoss from
      version 4.0.5 to 4.2.3.

      We use multiple JBoss' in a clustered environment. Most of our clients are
      connected via VPN. They did not even notice the migration. But one of our
      clients is connected via NAT since he uses the same IP ranges as we do. Downloading newer applcations works fine, so our servers are available.

      Before the migration he could work normally as any other client. After the
      migration, everytime he tries to instanciate a bean the application crashes.

      I compared the complete old configuration against the default 4.0.5
      config and our current 4.2.3 config. The only difference I found was
      an additional parameter in the $JAVA_OPTS var in the run.sh.


      I adopted this parameter into our current configuration, shut our
      complete cluster down and restartet it. But without success. Whenever a
      bean is instanciated, an exception like the following is thrown:

      org.jboss.invocation.ServiceUnavailableException: Service unavailable for -1632156200 calling method public abstract com.crazy_bytes.collab.sessionBean.CollabManagement com.crazy_bytes.collab.sessionBean.CollabManagementHome.create() throws javax.ejb.CreateException,java.rmi.RemoteException
       at org.jboss.invocation.unified.interfaces.UnifiedInvokerHAProxy.invoke(UnifiedInvokerHAProxy.java:409)
       at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
       at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
       at org.jboss.proxy.ejb.RetryInterceptor.invoke(RetryInterceptor.java:176)
       at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61)
       at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
       at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:184)
       at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
       at $Proxy0.create(Unknown Source)
       at com.crazy_bytes.collab.CollabDelegate.<init>(CollabDelegate.java:23)
       at com.crazy_bytes.collab.CollabDelegate.getInstance(CollabDelegate.java:36)
       at com.crazy_bytes.gui.Main.checkForAlias(Main.java:177)
       at com.crazy_bytes.gui.Main.main(Main.java:73)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
       at java.lang.reflect.Method.invoke(Unknown Source)
       at com.sun.javaws.Launcher.executeApplication(Unknown Source)
       at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
       at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
       at com.sun.javaws.Launcher.run(Unknown Source)
       at java.lang.Thread.run(Unknown Source)

      I can not reach our retired collegue and I am out of ideas. I googled over the net and searched this forum, but all I found concerning this problem is the parameter I mentioned above.

      For example one JBoss is reachable as follows:
      Local server IP:
      NATed server IP at the client:
      Local client IP:

      Anybody got an idea what I am doing wrong?

      Best regards,