[wildfly-dev] JBAS011592 the logging subsystem requires the log manager to be org.jboss.logmanager.LogManager
Max Rydahl Andersen
manderse at redhat.com
Mon Nov 24 07:34:23 EST 2014
On 20 Oct 2014, at 11:20, Max Rydahl Andersen wrote:> On 20 Oct 2014, at
1:48, James R. Perkins wrote:
>
>> As Stuart asked more details would help.
>>
>> The only way this could happen is if something, an agent for example,
>> attempts to get a logger before JBoss Modules initializes logging.
>> JBoss Modules looks for a META-INF/services/
>> java.util.logging.LogManager service which JBoss Log Manager has. If
>> an agent needs to be used the java.util.logging.manager needs to be
>> set to org.jboss.logmanager.LogManager before the agent initializes a
>> logger.
>
> It is all in the jira.
>
> And no, these errors have been happening on what is just plain vanilla
> WildFly or EAP/JPP bundles.
>
> We do not do any agent funkyness afaik.
>
> And as said the "workaround" so far have been "restart it" and it
> works.
>
> zero changes to the state or arguments.
okey so there been some new movement in this.
https://bugzilla.redhat.com/show_bug.cgi?id=1037970
Indicating there actually is a race condition if something pings the jvm
via jmx during the startup
*before* jboss main boot process manages to set the logmanager.
Something that will happen because
we actually have a feature that scans for locally running jvm's and
attach an agent to gather info.
Suggested workaround is to add this to our launch:
JAVA_OPTS="$JAVA_OPTS
-Djava.util.logging.manager=org.jboss.logmanager.LogManager"
JAVA_OPTS="$JAVA_OPTS
-Xbootclasspath/p:$JBOSS_HOME/modules/org/jboss/logmanager/main/jboss-logmanager-1.3.1.Final-redhat-1.jar"
-logging org.jboss.logmanager.LogManager
Question from us is, is the above workaround proper ? Will EAP/WildFly
change their boot arguments to match to avoid this race condition issue
for bat/sh launched servers too ?
/max
>
> /max
>
>>
>> On 10/19/2014 12:42 AM, Stuart Douglas wrote:
>>> Are you using a java agent by any chance?
>>>
>>> If you are then the java agent is probably causing the issue, by
>>> attempting to log something before JBoss modules can set the log
>>> manager.
>>>
>>> If you are not using a java agent then I am not sure exactly what
>>> the
>>> cause might be. Looking at the code it looks like it is possible for
>>> a
>>> custom security manager to break logging as the security manager is
>>> initialized first, however that does not seem likely.
>>>
>>> Can you share the details on exactly what command line is being used
>>> to
>>> start the server?
>>>
>>> Stuart
>>>
>>> Max Rydahl Andersen wrote:
>>>> Heya,
>>>>
>>>> In tools and around arquillian I'm seeing more and more of $subject
>>>> error that I can't figure out the cause of.
>>>>
>>>> I've found https://issues.jboss.org/browse/WFLY-3152 which David
>>>> responds the error message is clear.
>>>>
>>>> I might be clear, but I can't figure out why starting wildfly the
>>>> exact
>>>> same way will in one case result in this
>>>> error but then on second start it just works.
>>>>
>>>> I first thought that our tools might not be setting the LogManager
>>>> (which it does not), but when I look at standalone.sh
>>>> in the same server there is also no setting of this property hence
>>>> afaics the server is being obtuse.
>>>>
>>>> The answer in all cases seem to have been "have tried restarting
>>>> it?"
>>>> and then things starts working, until it doesn't - and
>>>> then we restart again.
>>>>
>>>> Any idea on what is going on here ?
>>>>
>>>> Thanks,
>>>> /max
>>>> http://about.me/maxandersen
>>>> _______________________________________________
>>>> wildfly-dev mailing list
>>>> wildfly-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> wildfly-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>> --
>> James R. Perkins
>> JBoss by Red Hat
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
> /max
> http://about.me/maxandersen
/max
http://about.me/maxandersen
More information about the wildfly-dev
mailing list