]
Jason Greene updated AS7-613:
-----------------------------
Fix Version/s: 7.1.2.Final
(was: 7.1.1.Final)
Disappearing log messages
-------------------------
Key: AS7-613
URL:
https://issues.jboss.org/browse/AS7-613
Project: Application Server 7
Issue Type: Feature Request
Components: Logging
Affects Versions: 7.0.0.Alpha1, 7.0.0.Beta1
Reporter: Brian Stansberry
Assignee: David Lloyd
Priority: Critical
Fix For: 7.1.2.Final
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.
If you think it was sent incorrectly, please contact your JIRA administrators: