ServiceMix
  1. ServiceMix
  2. SM-2256

Unable to shutdown container when JMS appender is configured

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.0
    • Fix Version/s: 5.0.1, 5.1.0, 6.0.0.M1, 6.0.0
    • Component/s: core
    • Labels:
      None

      Description

      Now that SM-2183 has been fixed, you can install and configure the JMS appender. However, once it has been configured, it's no longer possible to stop the container because the JMS ConnectionFactory gets shut down before the JMS appender is removed from the registry, causing it to block up the logging mechanism.

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        34d 10h 43m 1 Gert Vanthienen 04/Apr/14 00:36
        Resolved Resolved Closed Closed
        361d 17h 53m 1 Krzysztof Sobkowiak 31/Mar/15 18:29
        Krzysztof Sobkowiak made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Krzysztof Sobkowiak made changes -
        Fix Version/s 6.0.0.M1 [ 12329337 ]
        Gert Vanthienen made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Assignee Gert Vanthienen [ gertvanthienen ]
        Fix Version/s 5.1.0 [ 12326660 ]
        Fix Version/s 6.0.0 [ 12326661 ]
        Resolution Fixed [ 1 ]
        Hide
        Gert Vanthienen added a comment -

        Thanks for the pull request, Bart!
        I applied your changes to the branches for the 5.0.1, 5.1.0 and 6.0.0 releases

        Show
        Gert Vanthienen added a comment - Thanks for the pull request, Bart! I applied your changes to the branches for the 5.0.1, 5.1.0 and 6.0.0 releases
        Bart Horré made changes -
        Attachment 0001-SM-2256-make-jms-appender-async.patch [ 12637766 ]
        Bart Horré made changes -
        Attachment 0001-SM-2256-make-jms-appender-async.patch [ 12637766 ]
        Hide
        Bart Horré added a comment - - edited

        I took a stab at this.
        It seemed that not being able to shutdown was the only issue. The logging would block the container right after startup.
        I used a reference-listener to check when the ConnectionFactory becomes available so we can avoid trying to append logs before everything is in place.

        If I could improve anything, please let me know.

        https://github.com/apache/servicemix/pull/1

        Show
        Bart Horré added a comment - - edited I took a stab at this. It seemed that not being able to shutdown was the only issue. The logging would block the container right after startup. I used a reference-listener to check when the ConnectionFactory becomes available so we can avoid trying to append logs before everything is in place. If I could improve anything, please let me know. https://github.com/apache/servicemix/pull/1
        Gert Vanthienen made changes -
        Field Original Value New Value
        Fix Version/s 5.0.1 [ 12326511 ]
        Fix Version/s 5.0.0 [ 12324078 ]
        Hide
        Gert Vanthienen added a comment -

        Deferring to the Apache ServiceMix 5.0.1 release

        Show
        Gert Vanthienen added a comment - Deferring to the Apache ServiceMix 5.0.1 release
        Gert Vanthienen created issue -

          People

          • Assignee:
            Gert Vanthienen
            Reporter:
            Gert Vanthienen
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development