[
https://issues.apache.org/jira/browse/SM-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13954984#comment-13954984
]
Bart Horré edited comment on SM-2256 at 4/1/14 6:06 AM:
--------------------------------------------------------
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
was (Author: barthorre):
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.
> Unable to shutdown container when JMS appender is configured
> ------------------------------------------------------------
>
> Key: SM-2256
> URL: https://issues.apache.org/jira/browse/SM-2256
> Project: ServiceMix
> Issue Type: Bug
> Components: core
> Affects Versions: 5.0.0
> Reporter: Gert Vanthienen
> Fix For: 5.0.1
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
