Unable to shutdown container when JMS appender is configured

Details

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.

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.

Bart Horré
added a comment - 31/Mar/14 07:09 - 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