You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2016/08/28 09:14:21 UTC

[jira] [Commented] (CAMEL-10274) examples using mvn:jetty-run do not work after log4j2 upgrade

    [ https://issues.apache.org/jira/browse/CAMEL-10274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15443116#comment-15443116 ] 

Claus Ibsen commented on CAMEL-10274:
-------------------------------------

camel-example-cdi-rest-servlet/pom.xml:        <artifactId>jetty-maven-plugin</artifactId>
camel-example-reportincident/pom.xml:        <artifactId>jetty-maven-plugin</artifactId>
camel-example-restlet-jdbc/pom.xml:        <artifactId>jetty-maven-plugin</artifactId>
camel-example-servlet-tomcat-no-spring/pom.xml:        <artifactId>jetty-maven-plugin</artifactId>
camel-example-servlet-tomcat/pom.xml:        <artifactId>jetty-maven-plugin</artifactId>
camel-example-spring-ws/pom.xml:        <artifactId>jetty-maven-plugin</artifactId>
camel-example-swagger-xml/pom.xml:        <artifactId>jetty-maven-plugin</artifactId>

> examples using mvn:jetty-run do not work after log4j2 upgrade
> -------------------------------------------------------------
>
>                 Key: CAMEL-10274
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10274
>             Project: Camel
>          Issue Type: Task
>          Components: examples
>            Reporter: Claus Ibsen
>             Fix For: 2.18.0
>
>
> The examples such as camel-example-swagger-xml do not start with mvn jetty:run and fails with some logging stuff.
> {code}
> Caused by: java.util.ServiceConfigurationError: org.apache.juli.logging.Log: Provider org.eclipse.jetty.apache.jsp.JuliLog not a subtype
>        	at java.util.ServiceLoader.fail(ServiceLoader.java:239)
>        	at java.util.ServiceLoader.access$300(ServiceLoader.java:185)
>        	at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:376)
>        	at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404)
>        	at java.util.ServiceLoader$1.next(ServiceLoader.java:480)
>        	at org.apache.juli.logging.LogFactory.<init>(LogFactory.java:78)
>        	at org.apache.juli.logging.LogFactory.<clinit>(LogFactory.java:66)
>        	at org.apache.jasper.servlet.JasperInitializer.<clinit>(JasperInitializer.java:44)
>        	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>        	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>        	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>        	at java.lang.reflect.Constructor.newInstance(Constructor.java:408)
>        	at java.lang.Class.newInstance(Class.java:438)
>        	at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:380)
>        	... 50 more
> {code}
> This problem is likely in all the examples that uses the jetty plugin.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)