Thanks for helping us out here. I've filed https://issues.jboss.org/browse/WFCORE-4674 and I think I've got a fix for it. The one caveat is the fix will be in a the log manager with a slight hack in JBoss Modules. That also means once fixed in those two projects releases and upgrades will be required.

On Wed, Sep 18, 2019 at 12:28 PM Dustin Kut Moy Cheung <dcheung@redhat.com> wrote:
Yup I do have some logging stuff:

-Xbootclasspath/a:/opt/eap/modules/system/layers/base/.overlays/layer-base-jboss-eap-7.2.3.CP/org/jboss/logmanager/main/jboss-logmanager-2.1.7.Final-redhat-00001.jar:/opt/eap/modules/system/layers/base/org/glassfish/javax/json/main/javax.json-1.1.2.redhat-1.jar:/opt/eap/modules/system/layers/base/javax/json/api/main/javax.json-api-1.1.2.redhat-1.jar:/opt/eap/modules/system/layers/base/.overlays/layer-base-jboss-eap-7.2.3.CP/org/wildfly/common/main/wildfly-common-1.5.1.Final-redhat-00001.jar

The additional files that I add to the modules folder is here:

https://paste.fedoraproject.org/paste/y2xf5u5nq3iL18pQOkAlNQ

Let me know if I should create an EAP or a Wildfly issue! Happy to do so! :)

Sincerely,
Dustin

On Wed, 18 Sep 2019 at 14:43, James Perkins <jperkins@redhat.com> wrote:
This was exactly my question too :) Brian, Ken and I were just looking at this error yesterday and it only seems to show up when; Java 11 is used, Xbootclasspath is defined with the log manager and a custom handler/formatter is used.

I'm not sure if there is an issue already filed about this, but if not it might be time to file a specific one as this is at least the second time I'm aware of it came up. I can definitely reproduce it and am hoping to have time to look at this today.

On Wed, Sep 18, 2019 at 11:36 AM Brian Stansberry <brian.stansberry@redhat.com> wrote:
Do you have -Xbootclasspath/a stuff involving logging in the VM launch command?

On Wed, Sep 18, 2019 at 10:48 AM Dustin Kut Moy Cheung <dcheung@redhat.com> wrote:
Thanks for the suggestion! Unfortunately this didn't seem to help:

15:30:44,918 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
    ("subsystem" => "logging"),
    ("custom-handler" => "kafka")
]): java.lang.IllegalArgumentException: WFLYLOG0019: Failed to load module 'org.apache.log4jappender' for handler 'kafka'
at org.jboss.as.logging@6.0.15.Final-redhat-00001//org.jboss.as.logging.handlers.HandlerOperations$HandlerAddOperationStepHandler.createHandlerConfiguration(HandlerOperations.java:293)

I still don't get why it works on OpenJDK 8 and not OpenJDK 11 :(

Sincerely,
Dustin

On Tue, 17 Sep 2019 at 20:21, James Perkins <jperkins@redhat.com> wrote:
That module defined on custom-handler looks wrong. I think it should likely be org.apache.kafka.log4jappender.

On Mon, Sep 16, 2019 at 3:48 PM Dustin Kut Moy Cheung <dcheung@redhat.com> wrote:
Hi,

I'm following this guide to get logging sent to kafka: https://developer.jboss.org/wiki/SendingWildFlyLogsToKafka

This works on EAP 7.2.3.GA running on JDK 8, but fails to run on JDK 11:

```
15:54:28,819 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
    ("subsystem" => "logging"),
    ("custom-handler" => "kafka")
]): java.lang.IllegalArgumentException: Failed to load module "org.apache.log4j" for pojo "kafka"
...
```
Do you think this is related to the new module system in JDK 11 and I need to add some extra JVM flags to get it to work?
Thank you for your help!

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


--
James R. Perkins
JBoss by Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev


--
Brian Stansberry
Manager, Senior Principal Software Engineer
Red Hat


--
James R. Perkins
JBoss by Red Hat


--
James R. Perkins
JBoss by Red Hat