I was running mvn jetty:run
-Djava.util.logging.manager=org.apache.logging.log4j.jul.LogManager and it
gives that exception, now I runned mvn jetty:run-forked with <jvmArgs>
-Djava.util.logging.manager=org.apache.logging.log4j.jul.LogManager</jvmArgs>
configuration for jetty and it worked but I am getting another exception
from other component but I think its a compatibility issue:
Caused by: java.lang.IllegalArgumentException: can't parse argument number:
path
at java.text.MessageFormat.makeFormat(MessageFormat.java:1429)
at java.text.MessageFormat.applyPattern(MessageFormat.java:479)
at java.text.MessageFormat.<init>(MessageFormat.java:362)
at java.text.MessageFormat.format(MessageFormat.java:840)
at
org.apache.logging.log4j.message.MessageFormatMessage.formatMessage(MessageFormatMessage.java:94)
at
org.apache.logging.log4j.message.MessageFormatMessage.getFormattedMessage(MessageFormatMessage.java:66)
at
org.apache.logging.log4j.core.async.AsyncLogger.logMessage(AsyncLogger.java:250)
at
org.apache.logging.log4j.spi.ExtendedLoggerWrapper.logMessage(ExtendedLoggerWrapper.java:127)
at
org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:685)
at org.apache.logging.log4j.jul.ApiLogger.log(ApiLogger.java:61)
at
com.vaadin.external.org.slf4j.impl.JDK14LoggerAdapter.log(JDK14LoggerAdapter.java:588)
at com.vaadin.external.org.slf4j.impl.JDK14LoggerAdapter.info
(JDK14LoggerAdapter.java:305)
at
org.atmosphere.container.JSR356AsyncSupport.<init>(JSR356AsyncSupport.java:65)
... 39 more
Caused by: java.lang.NumberFormatException: For input string: "path"
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:580)
at java.lang.Integer.parseInt(Integer.java:615)
at java.text.MessageFormat.makeFormat(MessageFormat.java:1427)
... 51 more
>From this line : JSR356AsyncSupport.java:65
logger.info("JSR 356 Mapping path {}", servletPath);
when servletPath = "/{path}"
I am not sure if it is a log4j issue, There is a way to fix this?
On Fri, Jul 3, 2015 at 11:41 AM, Gary Gregory <[email protected]>
wrote:
> See also https://logging.apache.org/log4j/log4j-2.3/manual/webapp.html
>
> Gary
>
> On Fri, Jul 3, 2015 at 7:38 AM, Jose Luis Valencia <
> [email protected]>
> wrote:
>
> > I am working with Java components that use JUL in a web application and
> I
> > am not able to get JUL logs routed to log4j 2, I added the required maven
> > dependency for log4j-jul and set
> > -Djava.util.logging.manager=org.apache.logging.log4j.jul.LogManager in
> the
> > command line but maven gives an NoSuchClassexception because
> > org.apache.logging.log4j.jul.LogManager is not yet loaded and by
> > System.setProperty() in a spring CustomWebApplicationInitializer but
> > https://logging.apache.org/log4j/log4j-2.2/log4j-jul/index.html says it
> > must be called before any call of to LogManager or Logger. ¿Where I
> should
> > set the system property in a web application?
> >
> > Thank you!
> >
> > *JOSÉ L. VALENCIA G.*
> >
>
>
>
> --
> E-Mail: [email protected] | [email protected]
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>
--
José L. Valencia Gutierrez
<http://www.rocoto.com.pe>
