Lingo
  1. Lingo
  2. LINGO-22

JmsServiceExporter.destroy() doesn't close the underlying JmsProducer.

    Details

    • Type: Bug Bug
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.1
    • Fix Version/s: 1.4
    • Labels:
      None
    • Environment:
      Windows XP Pro SP1, Sun JRE 1.4.1_03
    • Testcase included:
      yes
    • Number of attachments :
      1

      Description

      See the attached unit test (which includes a demonstration of the 'fix"). After calling destroy()
      on the JmsServiceExporter instance, a number of threads are left lying around:
      Thread[Durable Queue Worker,6,main]
      Thread[Dispatch Worker,6,main]
      Thread[Thread-1,6,main]
      Thread[ActiveMQ ShutdownHook,5,main]
      Thread[TcpTransportServerChannel@tcp://A0277:61615,5,main]
      Thread[TcpTransportChannel: Socket[addr=/127.0.0.1,port=4016,localport=61615],5,main]
      Thread[TcpTransportChannel: Socket[addr=localhost/127.0.0.1,port=61615,localport=4016],7,main]
      Thread[JmsSessionDispatcher: 1,10,main]

      Calling close() on the JmsProducer cleans these up.

        Activity

        Hide
        james strachan added a comment -

        updated fix version

        Show
        james strachan added a comment - updated fix version
        james strachan made changes -
        Field Original Value New Value
        Fix Version/s 1.3 [ 12094 ]
        james strachan made changes -
        Fix Version/s 1.3 [ 12843 ]
        Fix Version/s 1.2.1 [ 12094 ]
        james strachan made changes -
        Fix Version/s 1.4 [ 12670 ]
        Fix Version/s 1.3 [ 12843 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Jim Beattie
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: