1 Reply Latest reply on May 24, 2004 9:50 AM by Adrian Brock

    How does the client know the Network connection is droped ?

    cold_lin Newbie

      I just done some tests on EJB network connection issue:
      1) client call a method of a session bean on server, before this method finish, the network of server is dropped.
      Then the client program seems keep on waitting forever. There are some error inormation generated on server side.

      2)client call a method of a session bean on server, before this method finish, the network of client is dropped.
      Then the client program seems keep on waitting forever. There is no error inormation found on server side.

      Can someone explain this and tell me how to let the client/server know there is a network connection problem?


      Many Thanks,

        • 1. Re: How does the client know the Network connection is drope
          Adrian Brock Master

          It depends upon the protocol used.

          e.g. if you are using the default RMI method, you should check the options available
          in the jdk documentation.
          You should also check your OS settings.

          Alternatively, where relevant, JBoss allows you to override the socket creation
          so you can configure whatever you like using client/server socket factories.

          e.g. for RMI in conf/jboss-service.xml

          
           <!-- RMI/JRMP invoker -->
           <mbean code="org.jboss.invocation.jrmp.server.JRMPInvoker"
           name="jboss:service=invoker,type=jrmp">
           <attribute name="RMIObjectPort">4444</attribute>
           <attribute name="ServerAddress">${jboss.bind.address}</attribute>
           <!--
           <attribute name="RMIClientSocketFactory">custom</attribute>
           <attribute name="RMIServerSocketFactory">custom</attribute>
           <attribute name="SecurityDomain">ssl-domain-name</attribute>
           -->
          
           <depends>jboss:service=TransactionManager</depends>
           </mbean>
          


          uncomment and replace custom with your implementation, e.g. one
          that sets a read timeout on the socket.

          You might also try java 1.4 which is a lot better than previous versions
          at detecting network problems.