2 Replies Latest reply on Jun 9, 2004 4:47 PM by genman

    OIL connections increasing

    mlange

       

      "mlange" wrote:
      We use 3.0.6 with Oracle as persistence manager for JMS messages. Messages are sent to the queue by using the OIL Invocation Layer. When running the server for a while we can see that the connections on the TCP port 8090 are increasing steadily:

      tcp 0 0 192.168.200.31:45467 192.168.200.31:8090 TIME_WAIT
      tcp 0 0 192.168.200.31:44409 192.168.200.31:8090 CONNECTED
      tcp 0 0 192.168.200.31:44413 192.168.200.31:8090 CONNECTED
      tcp 0 0 192.168.200.31:44425 192.168.200.31:8090 CONNECTED
      tcp 0 0 192.168.200.31:8090 192.168.200.31:44413 CONNECTED
      tcp 0 0 192.168.200.31:8090 192.168.200.31:44409 CONNECTED
      tcp 0 0 192.168.200.31:8090 192.168.200.31:44425 CONNECTED
      ...

      Is this correct behaviour? On 3.2.2 we do not see this. Does is make sense to use the JVM Invocation Layer?

      Thanks,

      -marek


        • 1. Re: OIL connections increasing
          rudifr

          We have the same problem with JBoss 3.2.3 and Oracle 9i as persistence mechanism for JMS.

          The number of connections and the number of OIL Worker and OILClientILService threads are steadily increasing.

          • 2. Re: OIL connections increasing
            genman


            1) You should be using the UIL2 connection factory for external client connections. OIL and OIL2, etc., may deadlock your application.
            2) You should use java:/ConnectionFactory for all in-VM connections.
            3) You should verify you are properly closing the connection when done.