1 Reply Latest reply on Mar 9, 2008 10:43 AM by 3004

    BEA WLS 9.2 MP2 tries to create initial context on the wrong IP address.

    666705
      Hello,

      we are facing a strange problem in a Weblogic communication between BEA WLS 8.1 SP6 (HP JDK 1.4.2.16) & BEA WLS 9.2 MP2 (HP JDK 1.5.0.10).

      The situation is the following:
      Both Weblogic servers are running under HP-UX PA-RISC and using in all listener configurations the DNS name of an HP Package [DNS1]. (Attention: This Package DNS Name [DNS1] has another IP [20.20.20.30] address than the physical server [20.20.20.20]!).

      Now the Weblogic 8.1 Server establish an connection to the Weblogic 9.2 Server (EJB call). So far so good.
      Inside this EJB another connection is been made back from the Weblogic 9.2 to the Weblogic 8.1 server.

      And now the trouble starts:
      IWeblogic 9.2 now uses the wrong IP address to access Weblogic 8.1. It tries to use the physical server IP address instead the Package IP address. Because of the fact that all listeners only registered to the Package IP (DNS Name) this will fail!.

      We already double checked that we using the DNS name [DNS1] when we initialize the context:

      props.put(Context.PROVIDER_URL,"t3://DNS1:8001");

      In the whole code we never using the physical server IP address [20.20.20.20]

      We have no idea why Weblogic 9.2 uses the wrong IP address.

      Just FYI: This is an upgrade project. The same constalation mentioned before works fine if only two BEA Weblogic 8.1 servers involved!

      Maybe somebody can help.

      Thx a million.

      Error messages:

      <Feb 28, 2008 5:45:58 PM GMT> <Debug> <JTANaming> <000000> <ServerCoordinatorDescriptor.getOrCreate(managedServer1+20.20.20.20:8001+domain1+t3+)>
      <Feb 28, 2008 5:45:58 PM GMT> <Debug> <JTANaming> <000000> <java.lang.Exception: DEBUG: ServerCoordinatorDescriptor.getOrCreate(managedServer1+20.20.20.20:800
      1+domain1+t3+)
      at weblogic.transaction.internal.TxDebug.debugStack(TxDebug.java:60)
      at weblogic.transaction.internal.ServerCoordinatorDescriptor.getOrCreate(ServerCoordinatorDescriptor.java:947)
      at weblogic.transaction.internal.ServerCoordinatorDescriptor.getOrCreate(ServerCoordinatorDescriptor.java:371)
      at weblogic.transaction.internal.ServerCheckpoint.onRecovery(ServerCheckpoint.java:175)
      at weblogic.transaction.internal.StoreTransactionLoggerImpl.recover(StoreTransactionLoggerImpl.java:441)
      at weblogic.transaction.internal.StoreTransactionLoggerImpl.init(StoreTransactionLoggerImpl.java:230)
      ...
      <Feb 28, 2008 5:45:59 PM GMT> <Debug> <JNDI> <000000> <Failed to create initial context due to: java.net.ConnectException: t3://20.20.20.20:8001: Destinati
      on unreachable; nested exception is:
      java.net.ConnectException: Connection refused (errno:239); No available router to destination
      at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:204)
      at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:154)
      at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:349)
      at weblogic.jndi.Environment.getContext(Environment.java:307)
      at weblogic.jndi.Environment.getContext(Environment.java:277)
      at weblogic.jndi.Environment.createInitialContext(Environment.java:200)
      at weblogic.jndi.Environment.getInitialContext(Environment.java:184)
      at weblogic.jndi.Environment.getInitialContext(Environment.java:162)
      at weblogic.transaction.internal.CoordinatorFactory.getInitialContext(CoordinatorFactory.java:45)
      ...
      <Feb 28, 2008 5:45:59 PM GMT> <Debug> <JTA2PCStackTrace> <000000> <Cannot obtain Coordinator: managedServer1+20.20.20.20:8001+domain1+t3+
      javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://20.20.20.20:8001: Destination unreachable; nested exception is:
      java.net.ConnectException: Connection refused (errno:239); No available router to destination]
      at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:49)
      at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:765)
      at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:364)
      at weblogic.jndi.Environment.getContext(Environment.java:307)

      --
      Edited by markus.jessl@eds.com at 02/29/2008 12:40 AM
        • 1. Re: BEA WLS 9.2 MP2 tries to create initial context on the wrong IP address.
          3004
          Markus Jessl <> wrote:
          Hello,

          we are facing a strange problem in a Weblogic communication between BEA
          WLS 8.1 SP6 (HP JDK 1.4.2.16) & BEA WLS 9.2 MP2 (HP JDK 1.5.0.10).

          The situation is the following:
          Both Weblogic servers are running under HP-UX PA-RISC and using in all
          listener configurations the DNS name of an HP Package [DNS1]. (Attention:
          This Package DNS Name [DNS1] has another IP [20.20.20.30] address than the
          physical server [20.20.20.20]!).

          Now the Weblogic 8.1 Server establish an connection to the Weblogic 9.2
          Server (EJB call). So far so good. Inside this EJB another connection is
          been made back from the Weblogic 9.2 to the Weblogic 8.1 server.

          And now the trouble starts:
          IWeblogic 9.2 now uses the wrong IP address to access Weblogic 8.1. It
          tries to use the physical server IP address instead the Package IP
          address. Because of the fact that all listeners only registered to the
          Package IP (DNS Name) this will fail!.

          We already double checked that we using the DNS name [DNS1] when we
          initialize the context:

          props.put(Context.PROVIDER_URL,"t3://DNS1:8001");

          In the whole code we never using the physical server IP address
          [20.20.20.20]
          Hello,

          Join the club, I have the same problem.
          Raised this problem to BEA a year ago, but of course the don't know what to
          do.



          Bart

          --
          Schelstraete Bart
          bart@schelstraete.org
          http://www.schelstraete.org
          http://www.linkedin.com/in/bschelst