[jboss-jira] [JBoss JIRA] Updated: (JBAS-9149) Disappearing log messages
[
https://issues.jboss.org/browse/JBAS-9149?page=com.atlassian.jira.plugin....
]
David Lloyd updated JBAS-9149:
------------------------------
Fix Version/s: Open To Community
The overwhelmingly most likely cause of this problem is the Log Window of Death between
the time the bootstrap log handlers are shut down and the "real" log handlers
are started. This is a problem that has actually existed since at *least* AS 5. The only
solution is to eliminate bootstrap logging as it is impossible to atomically swap the
entire logging configuration. This is something I definitely want to do, especially for
domain mode, but it is non-trivial. For now I will assign this to "Open to
Community", until and unless I have a chance to do this myself. If you are an
ambitious community member and are interested in taking this on, contact me in IRC
(dmlloyd on irc.freenode.net) and we'll chat about what needs to be done.
The reason we're seeing it more often now is most likely that with our concurrent
server startup, it is far, far more likely for services to be started during this window.
The logging reconfiguration process is actually very similar to AS 6 - but on AS 6 things
tended to start serially so it was unlikely to be observable.
Disappearing log messages
-------------------------
Key: JBAS-9149
URL: https://issues.jboss.org/browse/JBAS-9149
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Logging
Reporter: Brian Stansberry
Assignee: David Lloyd
Fix For: Open To Community
Affects post-Beta1 trunk (perhaps Beta1 as well; reports are from folks using trunk)
Report from Scott Stark of error messages sometimes not appearing:
> On 3/25/11 11:43 AM, Scott Stark wrote:
>> When starting up with a loopback address that is other than 127.0.0.1
>> (I'll get to that later), this exception happens:
>>
>> 14:31:16,275 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to
>> start service jboss.network.default:
>> org.jboss.msc.service.StartException in service jboss.network.default:
>> failed to resolve interface default
>> at
>>
org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:101)
>> at
>>
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>> [:1.6.0_20]
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>> [:1.6.0_20]
>> at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]
>>
>> Now I have seen this msg not be displayed at all, so under some
>> circumstances it is being lost.
Darran Lofthouse also reported that in some cases log messages from the start() method of
one of his services would not appear, but the service would indeed be started, implying
that the message is disappearing somehow.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira