Re: [jetty-users] Conflict between jetty-maven-plugin and tomcat-jdbc on

[Joakim Erdfelt <joakim@xxxxxxxxxxx>]

Please use the active issue tracker at github.

https://github.com/eclipse/jetty.project/issues

FYI: Bugzilla is going away (to be replaced by something else in the near future).

We'll still be using github and its issue tracker, even when this replacement for bugzilla hits.

Joakim Erdfelt / joakim@xxxxxxxxxxx

On Mon, Oct 10, 2016 at 8:23 PM, Zoran Jeremic <zoran.jeremic@xxxxxxxxx> wrote:

Hi Jan,

Thank you for your quick response. Could you please point me to the proper place to report this bug, since I don't have that much experience with it? I thought it should be reported on eclipse bugzilla, but once I tried it and selected Jetty (https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Jetty), I got a message:

Sorry, entering a bug into the product Jetty has been disabled.

Is there some other place or product I should go to?

Thanks,

Zoran

On Mon, Oct 10, 2016 at 8:10 PM, Jan Bartel <janb@xxxxxxxxxxx> wrote:

Hi Zoran,

Can you raise a bug on jetty for this? I think we may need to hook up a bit more of the juli machinery to the jetty logging mechanism. If you open a bug, I'll look into it.

cheers

Jan

On 11 October 2016 at 14:07, Zoran Jeremic <zoran.jeremic@xxxxxxxxx> wrote:

Hi,

I have a maven application that uses jetty-maven-plugin 9.3.7 for local development. I am also using tomcat-jdbc 9.0.0.M10, and jetty plugin has a conflict with this dependency on org.apache.juli.logging.Log.
When I run application using Jetty server, the following exception is fired:


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.tomcat.jdbc.pool.PoolProperties.<clinit>(PoolProperties.java:36)
    at org.prosolo.core.hibernate.HibernateConfig.dataSource(HibernateConfig.java:112)
    at org.prosolo.core.hibernate.HibernateConfig$$EnhancerBySpringCGLIB$$f615c572.CGLIB$dataSource$1(<generated>)
    at org.prosolo.core.hibernate.HibernateConfig$$EnhancerBySpringCGLIB$$f615c572$$FastClassBySpringCGLIB$$91af07c5.invoke(<generated>)
    at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228)
    at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:309)
    at org.prosolo.core.hibernate.HibernateConfig$$EnhancerBySpringCGLIB$$f615c572.dataSource(<generated>)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:162)


If I exclude tomcat-juli from tomcat-jdbc jetty runs fine, but I can't run JUnit tests since the other exceptions is happening due to the missing class:


Caused by: java.lang.ClassNotFoundException: org.apache.juli.logging.LogFactory
        at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
        at org.apache.tomcat.jdbc.pool.PoolProperties.<clinit>(PoolProperties.java:36)
        at org.prosolo.core.hibernate.HibernateConfig.dataSource(HibernateConfig.java:112)
        at org.prosolo.core.hibernate.HibernateConfig$$EnhancerBySpringCGLIB$$6e9ae256.CGLIB$dataSource$0(<generated>)
        at org.prosolo.core.hibernate.HibernateConfig$$EnhancerBySpringCGLIB$$6e9ae256$$FastClassBySpringCGLIB$$ddcf2b49.invoke(<generated>)
        at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228)
        at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:309)
        at org.prosolo.core.hibernate.HibernateConfig$$EnhancerBySpringCGLIB$$6e9ae256.dataSource(<generated>)


Any ideas how to solve this issue?

Thanks,
Zoran

_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users

--

Jan Bartel <janb@xxxxxxxxxxx>

www.webtide.com
Expert assistance from the creators of Jetty and CometD

_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users

_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users