|
From: <php...@li...> - 2009-11-30 18:21:20
|
> But now that it came all clear, you can set the log4j logger to listen on a > different port: > Well, I don't like configuration options; software should just work. In my opinion adding a configuration option to work around a bug in some external software component is a bad idea. I think the jboss developers are to blame, because they use a well known service end point for their internal communication purpose. I will have a look at this issue when I prepare version 5.5.4.1. In the worst case, we need to switch off chainsaw if we're running within the jboss app server or if we detect that the service listening on port 4445 is not chainsaw. Regards, Jost Boekemeier |