Hi James,

Oh I see, that makes total sense - since premain() executes before LogManager is configured. But when agentmain() is executes it’s afterwards. I wouldn’t need to replicate this behavior. I would probably have add a new one if I don’t get one that I need. Am I correct? 

Thanks

./Sam

On Wed, Nov 14, 2018 at 11:38 PM James Perkins <jperkins@redhat.com> wrote:

I'm not sure I follow. The only time the log manager is required to be on the boot class path is if the agent creates a logger before the java.util.logging.LogManager is configured.

On Tue, Nov 13, 2018 at 6:17 PM Sam Thomas <sam.thomas@broadcom.com> wrote:

Hi,

I understand when starting jboss you can supply the above to specify the logmanager. If this is not supplied during start up and an agent connects to jboss during runtime using agentmain(), how can I replicate the -Xbootclasspath/p: behavior during runtime? 

Thanks and Regards

Sam Thomas

_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev

--

James R. Perkins

JBoss by Red Hat

--

Thanks

./Sam