[wildfly-dev] how a -javaagent can use logging and not blow up WildFly

[Emmanuel Hugonnet]

Yes this works.
This is how the NetBeans Profiler works around that :)

Le 05/03/2017 à 23:18, John Mazzitelli a écrit :
>>> "oh, you just do this magical step and it works around the problem."
>>
>> With recent builds setting system property org.wildfly.logging.skipLogManagerCheck=true
>> should workaround your problem.
> 
> Ah.. That's a good one to know.
> 
> I need something for earlier WildFly and EAP builds, though. But I recently found this solves my problem (this worked for me on both EAP6 and EAP7.1):
> 
> Inside standalone.conf:
> 
> # Add "org.jboss.logmanager" to the JBoss Modules system packages
> if [ "x$JBOSS_MODULES_SYSTEM_PKGS" = "x" ]; then
>    JBOSS_MODULES_SYSTEM_PKGS="org.jboss.byteman,org.jboss.logmanager"
> fi
> 
> #   Explicitly tell the VM to use the JBoss Log Manager via -Djava.util.logging.manager system property.
> #   Use the -javaagent VM option to load the agent
> JAVA_OPTS="$JAVA_OPTS -Djava.util.logging.manager=org.jboss.logmanager.LogManager -javaagent:my-agent.jar"
> 
> That seems to fix my problem.
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
Url : http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170306/9229b415/attachment-0001.bin