That can be tough to solve because frequently you will get a
NoClassDefFoundError on Class A even though it is there because it has a
reference to Class B or something in Class B and it isn’t there. Unfortunately,
the JVM isn’t very good about letting you know what is actually missing.
Ralph
>
Thanks, Ralph, for busting my theory of the case. :-)
I built a test application, from one of the examples floating around on the
Internet, added log4j2 to it, built the client and ran it on my server. It
worked without incident, disproving my theory.
Ugh, now to figure out how to debug java.
The developer snapshot tarball works for me.
Available at http://people.apache.org/~sdeboy/
On Jan 16, 2017 3:43 AM, "Robert Lu" wrote:
> Hi,
>
> Cloud you please compile Chainsaw for macOS Sierra?
>
>
>
>
> -
> To unsubscribe,
Can you provide a test application along with a link to the JBoss version you
are using? I haven’t worked with JBoss in several years but would happy to
take a look - if for no other reason than to do something with LOG4J2-18.
Ralph
> On Jan 16, 2017, at 9:11 AM, COHEN, STEVEN M wrote:
>
> O
Our team is fairly standardized on using log4j2 over log4j, commons-logging or
any other framework.
This had presented some issues with jboss-eap which does not support log4j2.
Nevertheless, for applications running on the jboss-server it was fairly easy,
and even a good thing to package log4j
No problem, I've found a solution.
I've made my simple Log level Lookup.
Feel free to include into main log4j project. It's simple and powerful!
import org.apache.logging.log4j.core.LogEvent;
import org.apache.logging.log4j.core.config.plugins.Plugin;
import org.apache.logging.log4j.core.loo
Hi,
Cloud you please compile Chainsaw for macOS Sierra?
-
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
