0 Replies Latest reply on Sep 4, 2008 4:20 AM by Harald Hartmann

    javax.naming.CommunicationException with 1.5 but not with 1.

    Harald Hartmann Newbie

      Hello everbody,

      when we run

      C:\Programme\java\jre1.5.0_04\bin\java.exe -classpath .;J:\jar\j2ee\HabaClient.jar;J:\jar\j2ee\jbossall-client.jar de/haba/harald/ejb/LookupTester jnp://138.33.5.51:1099

      we get a javax.naming.CommunicationException: Could not obtain connection to any of these urls: 138.33.5.51:1099 and discovery failed with error: javax.naming.CommunicationException: Failed to connect to server 138.33.5.51:1100 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 138.33.5.51:1100 [Root exception is java.net.ConnectException: Connect attempt timed out]] [Root exception is javax.naming.CommunicationException: Failed to connect to server 138.33.5.51:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 138.33.5.51:1099 [Root exception is java.net.ConnectException: Connect attempt timed out]]]

      with

      C:\Programme\java\jre1.6.0_01\bin\java.exe -classpath .;J:\jar\j2ee\HabaClient.jar;J:\jar\j2ee\jbossall-client.jar de/haba/harald/ejb/LookupTester jnp://138.33.5.51:1099

      there aren't any problems.

      The lookupTester calls the lookupTesterEJB in a for-next-loop and get back the System.getProperties() especially lookup.getHost().getProperty("bind.address")

      Just for testing we set jnp.partitionName from TestPartition to ProductivePartition then the jre1.5.0_14 doesn't get a Exception, but the first 10 calls go to our productive cluster and then the last ones to the test cluster.

      any clues?

      Kind Regards