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
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
zero changes to the state or arguments.
okey so there been some new movement in this.
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:
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 ?
> 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
>> If you are not using a java agent then I am not sure exactly what
>> cause might be. Looking at the code it looks like it is possible for
>> 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
>> start the server?
>> Max Rydahl Andersen wrote:
>>> 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
>>> responds the error message is clear.
>>> I might be clear, but I can't figure out why starting wildfly the
>>> 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
>>> and then things starts working, until it doesn't - and
>>> then we restart again.
>>> Any idea on what is going on here ?
>>> wildfly-dev mailing list
>> wildfly-dev mailing list
> James R. Perkins
> JBoss by Red Hat
> wildfly-dev mailing list