1 Reply Latest reply on Oct 21, 2002 10:22 AM by Terry Rosenbaum

    Client using OIL2 lingers 1 minute at exit

    Terry Rosenbaum Newbie

      A client using the OIL2 invocation layer lingers 1 minute when exiting.

      Did the following:

      Create a TopicConnection (OIL2ConnectionFactory)
      Create a TopicSession (untransacted, auto ack)
      Lookup a Topic
      Create a TopicPublisher for the Topic
      Create a TemporaryTopic
      Create a TopicSubscriber for the TemporaryTopic
      Publish a message using TopicPublisher
      close() TopicPublisher
      close() TopicSubscriber
      close() TopicSession
      close() TopicConnection
      return from main thread

      At this point, there is a 1 minute
      delay before the process actually exits.

      When using OIL instead (ConnectionFactory)
      the process exits immediately.

      The delay has to do with the PooledExecutor
      used by the OIL2SocketHandler.

      This can be fixed by modifying the
      OIL2SocketHandler.stop() method
      to interrupt all tasks in its pool:


      public void stop()
      if (log.isTraceEnabled())
      running = false;


      public void stop()
      if (log.isTraceEnabled())
      running = false;

      I don't know enough about the OIL2 code yet to
      say for certain that this is the right thing to
      do. I'm hoping that someone who does understand
      OIL2 code fully can look at/fix this issue.

      After applying the above modification, the same
      sequence above results in the process exiting
      immediately when the main thread exits (no more
      1 minute delay).

      I also noted that the version of the "concurrent"
      library used by JBoss is apparently older than the
      current version released by its developer (e.g.
      the latest PooledExecutor has a shutdownNow() method
      that is not present in the version used by JBoss).

      I entered a bug for this behavior on SourceForge.