1 Reply Latest reply on May 18, 2006 4:38 AM by glum

    Client couldn't detect a broken connection

    Joseph Tang Newbie

      Hi all,

      I'm running jboss 4.0.3 SP1 on Redhat Linux 9.0 with Java 1.6.0-beta-b59g.
      I deployed a simple EJB 2.1 program and ran a java client
      on another linux machine which accesses the EJB across Internet.

      The jboss server is running on a dynamic IP server, when the IP changes,
      the connection doesn't close explicitly. The client then keeps waiting for
      the server reply endlessly.

      Therefore I tried to find out how the client would throw an exception when
      the connection is broken.

      I tried to set properties like jnp.timeout, jnp.sotimeout and jndi.ldap.read.timeout;
      and DefaultCacheTimeout and DefaultCacheResolution in jboss-sesrvice.xml.
      However the client does not detect the timeout.

      Does anyone have a clue?

      Thanks in advanced.

        • 1. Re: Client couldn't detect a broken connection
          glum Newbie

          We have the same scenario. But besides performing EJB calls our client also subscribes to a server JMS topic in order to receive server notification messages. Connection loss may be easily detected via JMS API. So this is a working solution but if you do not use use JMS it looks more like a workaround than a solution...