Hello JNDI is not a (big) problem - you have to ensure that all (aries-)jndi bundles and JDBC driver bundles should start before pax-logging-log4j2. Also data source should be ready.
The proper solution should be (IMO) to implement lazily initialized log4j2's ConnectionSource. regards Grzegorz Grzybek wt., 9 kwi 2019 o 17:05 Jean-Baptiste Onofré <j...@nanthrax.net> napisał(a): > Did you check with jndi:names if it's registered ? > > On 09/04/2019 17:00, leonardchicco wrote: > > Hi, > > > > In my custom distribution, I tried to set the JNDIfeature as > startupFeature > > and bootFeature as following > > > > <startupFeatures> > > <feature>jndi</feature> > > <feature>eventadmin</feature> > > </startupFeatures> > > <bootFeatures> > > <feature>jndi</feature> > > ... > > </bootFeatures> > > > > But i have the same log error. > > > > Thanks in advance > > > > > > > > -- > > Sent from: http://karaf.922171.n3.nabble.com/Karaf-Dev-f930721.html > > > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com >
