1 Reply Latest reply on Jun 17, 2004 1:51 PM by Yongjun Jiao

    how to keep alive the connect between standalone Tomcat and

    Yongjun Jiao Newbie

      Here is my configuration:
      standalone Tomcat 4.1.30,
      JBoss 3.2.2RC3,
      jbossall-client.jar in Tomcat shared/lib/,

      My Tomcat works as an EJB client to call JBoss. I also cached EJB home on the Tomcat.
      It is understandable that the 1st EJB invocation is slow. However the 2nd EJB invocation is almost as slow as the first time if the interval between the 1st and 2nd invocation is greater than, say, 1 minute(even shorter).
      It is fast if the invocation interval is serveral seconds.

      My guess is the connection between Tomcat and JBoss is closed after some wating time.
      I am just wondering whether JBoss supports such a feature as Http1.1 connecdtion Keep-Alive.

      Another strange thing is if I put the jbossall-client.jar into my web application LIB directory, each invocation is much slower.

        • 1. Re: how to keep alive the connect between standalone Tomcat
          Yongjun Jiao Newbie

          If you look at org.jboss.invocation.pooled.server.PooledInvoker,
          JBoss does seem to cache the connection on the client side.
          However the CurrentClientPoolSize is already 0 during my testing.

          I used COMMIT D option and "optiond-refresh-rate".
          Originally I thought JBoss would automcatically RELOAD the cache beans after the "optiond-refresh-rate". However it turned out JBoss just removed the cache, no RELOAD.