1 Reply Latest reply on Jan 5, 2002 5:39 AM by Peter Sojan

    JNDI lookup stalls with 2.4.4

    Peter Sojan Newbie

      I upgraded to 2.4.4 from 2.4.3 and the first thing I´ve done is to deploy the simple "Interest" application mentioned in the online docs.

      When running the test client JNDI returns a context but stalls when this context is used to lookup the interest bean:
      InitialContext jndiContext = new InitialContext();
      System.out.println("Got context");

      // Get a reference to the Interest Bean
      Object ref = jndiContext.lookup("interest/Interest");
      System.out.println("Got reference");

      No exception, no hint in the logs, just hanging within the lookup(...) method. The properties
      file for JNDI seems to be ok, because if I change something the client immediately throws an exception.

      Any hints on this!?

      ANother thing on 2.4.4: You cannot properly shutdown JBoss via Ctrl-C on my system: JBoss utters to shut down 47 (?) MBeans and then hangs, leaving java processes around (must be killed to get a clean environment again). Shutting down via browser is ok, however.


        • 1. Re: JNDI lookup stalls with 2.4.4 - SOLVED
          Peter Sojan Newbie

          Ok it was of course my very own fault:

          I moved my machine some time ago and got a new IP-Address. An idiot like I am I forgot to update this
          in my /etc/hosts file so JNDI lookups went to the old
          IP-Address. And because TCP timeouts on linux are very long I couldnt see anything unless today: Someone eventually reused my old IP-Address and as he turned on his machine I finally got an "Connection refused" Exception during JNDI lookup.

          Btw. the mentioned shutdown problems also vanished magically once I reflected my new address in the /etc/hosts file.

          so long