You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@directory.apache.org by Wayne Johnson <wj...@mqsoftware.com> on 2007/07/17 20:22:17 UTC
Apache DS (I think) fails to load when we upgraded to Jetty 6.1.4 or 6.1.5rc0
I am trying to upgrade our Jetty & Apache DS (1.0.0) server From Jetty 6.0.1 to Jetty 6.1.4 (or even Jetty 6.1.5rc0) and can't get Apache Directory Service to load. Unfortunately, the only error I seem to get is:
INFO | jvm 1 | 2007/07/17 12:50:04 | 2007-07-17 12:50:04.642::WARN: Config error at <New id="factory" class="org.springframework.context.support.FileSystemXmlApplicationContext"><Arg>jetty/server.xml</Arg><Call id="cfg" name="getBean"><Arg>configuration</Arg><Call id="jndi-env" name="toJndiEnvironment"/></Call><Call id="env" name="getBean"><Arg>environment</Arg><Call name="setProperty"><Arg><Get name="INITIAL_CONTEXT_FACTORY" class="javax.naming.Context"/></Arg><Arg>org.apache.directory.server.jndi.ServerContextFactory</Arg></Call><Call name="putAll"><Arg><Ref id="jndi-env"/></Arg></Call></Call></New>
INFO | jvm 1 | 2007/07/17 12:50:04 | Configuration Exception: null
I'm not sure if this is a problem in Jetty, or Apache DS, or our configuration. Any ideas? Any hints on how to configure logging for a bit more information? I tried adding a log4j.appender for directory service but still nothing.
I'll also post to the Jetty mailing list as well. Thanks.
Wayne Johnson
Senior Software Engineer
MQSoftware, Inc.
1660 S Highway 100
Minneapolis, MN 55416
(952) 345-8628
Re: Apache DS (I think) fails to load when we upgraded to Jetty 6.1.4 or 6.1.5rc0
Posted by Chris Custine <cc...@apache.org>.
Hi Wayne,
One bit of advice is to use the jcl104-over-slf4j package which is an
implementation of commons-logging that maps to slf4j. Spring and many other
projects use commons-logging, so this is a good way to make your logging
setup consistent. So basically all you do is throw out commons-logging and
add jcl104-overslf4j and you are all set. I have a blog entry about the
commons-logging problems and how to use slf4j to fix it here:
http://blog.organicelement.com/2006/12/21/commons-logging-classloader-woes/
Good luck,
Chris
On 7/17/07, Wayne Johnson <wj...@mqsoftware.com> wrote:
>
> I did finally figure it out. I was missing a slf4j jarfile. Part of my
> confusion was due to the myriad of loggers and logger wrappers involved.
>
> Our configuration is pretty complicated with Axis, Directory Service,
> Slide, an HTTP server and a few JSP web apps running under the Tanuki Java
> Service Wrapper. I apologize for not including more but I wasn't sure how
> to describe it without dropping 2 dozen configuration files on everyone.
>
> Thanks everyone for the suggestions.
>
>
> -----Original Message-----
> From: akarasulu@gmail.com on behalf of Alex Karasulu
> Sent: Tue 7/17/2007 4:15 PM
> To: users@directory.apache.org
> Subject: Re: Apache DS (I think) fails to load when we upgraded to Jetty
> 6.1.4 or 6.1.5rc0
>
> How about providing more information on whether you have ADS embedded
> running in Jetty or
> in some app running both or ADS is standalone.
>
> Alex
>
> On 7/17/07, Wayne Johnson <wj...@mqsoftware.com> wrote:
> >
> > I am trying to upgrade our Jetty & Apache DS (1.0.0) server From Jetty
> > 6.0.1 to Jetty 6.1.4 (or even Jetty 6.1.5rc0) and can't get Apache
> > Directory Service to load. Unfortunately, the only error I seem to get
> is:
> >
> > INFO | jvm 1 | 2007/07/17 12:50:04 | 2007-07-17 12:50:04.642::WARN:
> Config
> > error at <New id="factory" class="
> > org.springframework.context.support.FileSystemXmlApplicationContext
> "><Arg>jetty/server.xml</Arg><Call
> > id="cfg" name="getBean"><Arg>configuration</Arg><Call id="jndi-env"
> > name="toJndiEnvironment"/></Call><Call id="env"
> > name="getBean"><Arg>environment</Arg><Call name="setProperty"><Arg><Get
> > name="INITIAL_CONTEXT_FACTORY" class="javax.naming.Context"/></Arg><Arg>
> > org.apache.directory.server.jndi.ServerContextFactory</Arg></Call><Call
> > name="putAll"><Arg><Ref id="jndi-env"/></Arg></Call></Call></New>
> > INFO | jvm 1 | 2007/07/17 12:50:04 | Configuration Exception: null
> >
> > I'm not sure if this is a problem in Jetty, or Apache DS, or our
> > configuration. Any ideas? Any hints on how to configure logging for a
> bit
> > more information? I tried adding a log4j.appender for directory service
> > but still nothing.
> >
> > I'll also post to the Jetty mailing list as well. Thanks.
> >
> > Wayne Johnson
> > Senior Software Engineer
> > MQSoftware, Inc.
> > 1660 S Highway 100
> > Minneapolis, MN 55416
> > (952) 345-8628
> >
> >
> >
>
>
>
Re: Apache DS (I think) fails to load when we upgraded to Jetty 6.1.4 or 6.1.5rc0
Posted by Emmanuel Lecharny <el...@gmail.com>.
Hi Wayne,
np at all. Thanks Sun for having introduced his logger in the JDK...
How stupid it was !
On 7/18/07, Wayne Johnson <wj...@mqsoftware.com> wrote:
> I did finally figure it out. I was missing a slf4j jarfile. Part of my confusion was due to the myriad of loggers and logger wrappers involved.
>
> Our configuration is pretty complicated with Axis, Directory Service, Slide, an HTTP server and a few JSP web apps running under the Tanuki Java Service Wrapper. I apologize for not including more but I wasn't sure how to describe it without dropping 2 dozen configuration files on everyone.
>
> Thanks everyone for the suggestions.
>
>
> -----Original Message-----
> From: akarasulu@gmail.com on behalf of Alex Karasulu
> Sent: Tue 7/17/2007 4:15 PM
> To: users@directory.apache.org
> Subject: Re: Apache DS (I think) fails to load when we upgraded to Jetty 6.1.4 or 6.1.5rc0
>
> How about providing more information on whether you have ADS embedded
> running in Jetty or
> in some app running both or ADS is standalone.
>
> Alex
>
> On 7/17/07, Wayne Johnson <wj...@mqsoftware.com> wrote:
> >
> > I am trying to upgrade our Jetty & Apache DS (1.0.0) server From Jetty
> > 6.0.1 to Jetty 6.1.4 (or even Jetty 6.1.5rc0) and can't get Apache
> > Directory Service to load. Unfortunately, the only error I seem to get is:
> >
> > INFO | jvm 1 | 2007/07/17 12:50:04 | 2007-07-17 12:50:04.642::WARN: Config
> > error at <New id="factory" class="
> > org.springframework.context.support.FileSystemXmlApplicationContext"><Arg>jetty/server.xml</Arg><Call
> > id="cfg" name="getBean"><Arg>configuration</Arg><Call id="jndi-env"
> > name="toJndiEnvironment"/></Call><Call id="env"
> > name="getBean"><Arg>environment</Arg><Call name="setProperty"><Arg><Get
> > name="INITIAL_CONTEXT_FACTORY" class="javax.naming.Context"/></Arg><Arg>
> > org.apache.directory.server.jndi.ServerContextFactory</Arg></Call><Call
> > name="putAll"><Arg><Ref id="jndi-env"/></Arg></Call></Call></New>
> > INFO | jvm 1 | 2007/07/17 12:50:04 | Configuration Exception: null
> >
> > I'm not sure if this is a problem in Jetty, or Apache DS, or our
> > configuration. Any ideas? Any hints on how to configure logging for a bit
> > more information? I tried adding a log4j.appender for directory service
> > but still nothing.
> >
> > I'll also post to the Jetty mailing list as well. Thanks.
> >
> > Wayne Johnson
> > Senior Software Engineer
> > MQSoftware, Inc.
> > 1660 S Highway 100
> > Minneapolis, MN 55416
> > (952) 345-8628
> >
> >
> >
>
>
>
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
RE: Apache DS (I think) fails to load when we upgraded to Jetty 6.1.4 or 6.1.5rc0
Posted by Wayne Johnson <wj...@mqsoftware.com>.
I did finally figure it out. I was missing a slf4j jarfile. Part of my confusion was due to the myriad of loggers and logger wrappers involved.
Our configuration is pretty complicated with Axis, Directory Service, Slide, an HTTP server and a few JSP web apps running under the Tanuki Java Service Wrapper. I apologize for not including more but I wasn't sure how to describe it without dropping 2 dozen configuration files on everyone.
Thanks everyone for the suggestions.
-----Original Message-----
From: akarasulu@gmail.com on behalf of Alex Karasulu
Sent: Tue 7/17/2007 4:15 PM
To: users@directory.apache.org
Subject: Re: Apache DS (I think) fails to load when we upgraded to Jetty 6.1.4 or 6.1.5rc0
How about providing more information on whether you have ADS embedded
running in Jetty or
in some app running both or ADS is standalone.
Alex
On 7/17/07, Wayne Johnson <wj...@mqsoftware.com> wrote:
>
> I am trying to upgrade our Jetty & Apache DS (1.0.0) server From Jetty
> 6.0.1 to Jetty 6.1.4 (or even Jetty 6.1.5rc0) and can't get Apache
> Directory Service to load. Unfortunately, the only error I seem to get is:
>
> INFO | jvm 1 | 2007/07/17 12:50:04 | 2007-07-17 12:50:04.642::WARN: Config
> error at <New id="factory" class="
> org.springframework.context.support.FileSystemXmlApplicationContext"><Arg>jetty/server.xml</Arg><Call
> id="cfg" name="getBean"><Arg>configuration</Arg><Call id="jndi-env"
> name="toJndiEnvironment"/></Call><Call id="env"
> name="getBean"><Arg>environment</Arg><Call name="setProperty"><Arg><Get
> name="INITIAL_CONTEXT_FACTORY" class="javax.naming.Context"/></Arg><Arg>
> org.apache.directory.server.jndi.ServerContextFactory</Arg></Call><Call
> name="putAll"><Arg><Ref id="jndi-env"/></Arg></Call></Call></New>
> INFO | jvm 1 | 2007/07/17 12:50:04 | Configuration Exception: null
>
> I'm not sure if this is a problem in Jetty, or Apache DS, or our
> configuration. Any ideas? Any hints on how to configure logging for a bit
> more information? I tried adding a log4j.appender for directory service
> but still nothing.
>
> I'll also post to the Jetty mailing list as well. Thanks.
>
> Wayne Johnson
> Senior Software Engineer
> MQSoftware, Inc.
> 1660 S Highway 100
> Minneapolis, MN 55416
> (952) 345-8628
>
>
>
Re: Apache DS (I think) fails to load when we upgraded to Jetty 6.1.4 or 6.1.5rc0
Posted by Alex Karasulu <ak...@apache.org>.
How about providing more information on whether you have ADS embedded
running in Jetty or
in some app running both or ADS is standalone.
Alex
On 7/17/07, Wayne Johnson <wj...@mqsoftware.com> wrote:
>
> I am trying to upgrade our Jetty & Apache DS (1.0.0) server From Jetty
> 6.0.1 to Jetty 6.1.4 (or even Jetty 6.1.5rc0) and can't get Apache
> Directory Service to load. Unfortunately, the only error I seem to get is:
>
> INFO | jvm 1 | 2007/07/17 12:50:04 | 2007-07-17 12:50:04.642::WARN: Config
> error at <New id="factory" class="
> org.springframework.context.support.FileSystemXmlApplicationContext"><Arg>jetty/server.xml</Arg><Call
> id="cfg" name="getBean"><Arg>configuration</Arg><Call id="jndi-env"
> name="toJndiEnvironment"/></Call><Call id="env"
> name="getBean"><Arg>environment</Arg><Call name="setProperty"><Arg><Get
> name="INITIAL_CONTEXT_FACTORY" class="javax.naming.Context"/></Arg><Arg>
> org.apache.directory.server.jndi.ServerContextFactory</Arg></Call><Call
> name="putAll"><Arg><Ref id="jndi-env"/></Arg></Call></Call></New>
> INFO | jvm 1 | 2007/07/17 12:50:04 | Configuration Exception: null
>
> I'm not sure if this is a problem in Jetty, or Apache DS, or our
> configuration. Any ideas? Any hints on how to configure logging for a bit
> more information? I tried adding a log4j.appender for directory service
> but still nothing.
>
> I'll also post to the Jetty mailing list as well. Thanks.
>
> Wayne Johnson
> Senior Software Engineer
> MQSoftware, Inc.
> 1660 S Highway 100
> Minneapolis, MN 55416
> (952) 345-8628
>
>
>
Re: Apache DS (I think) fails to load when we upgraded to Jetty 6.1.4 or 6.1.5rc0
Posted by Chris Custine <cc...@apache.org>.
You may get more specific info from the Jetty list, but you should be able
to do it in log4j config or whatever logging impl Jetty is using. Spring
itself uses commons-logging, so it will defer to whatever logging impl you
have packaged with the server.
On 7/17/07, Wayne Johnson <wj...@mqsoftware.com> wrote:
>
> Forgive my ignorance, but can you be a bit more specific on how to turn up
> logging on Spring? Or is that a question for the Jetty list?
>
> > -----Original Message-----
> > From: chris.custine@gmail.com
> > [mailto:chris.custine@gmail.com]On Behalf
> > Of Chris Custine
> > Sent: Tuesday, July 17, 2007 1:57 PM
> > To: users@directory.apache.org
> > Subject: Re: Apache DS (I think) fails to load when we
> > upgraded to Jetty
> > 6.1.4 or 6.1.5rc0
> >
> >
> > Try turning up the debug logging for Spring. It looks like Spring is
> > getting an NPE somewhere (possibly from loading ApacheDS
> > since there is no
> > logging from ADS showing up yet). If there were any calls
> > going in to ADS,
> > I think you would have seen log output. It might also be
> > some change to the
> > Jetty JNDI impl?
> >
> > Good luck,
> > Chris
> >
> > On 7/17/07, Wayne Johnson < wjohnson@mqsoftware.com> wrote:
> > >
> > > I am trying to upgrade our Jetty & Apache DS ( 1.0.0)
> > server From Jetty
> > > 6.0.1 to Jetty 6.1.4 (or even Jetty 6.1.5rc0) and can't get Apache
> > > Directory Service to load. Unfortunately, the only error I
> > seem to get is:
> > >
> > > INFO | jvm 1 | 2007/07/17 12:50:04 | 2007-07-17 12:50:
> > 04.642::WARN: Config
> > > error at <New id="factory" class="
> > >
> > org.springframework.context.support.FileSystemXmlApplicationCo
> > ntext"><Arg>jetty/server.xml</Arg><Call
> > > id="cfg" name="getBean"><Arg>configuration</Arg><Call id="jndi-env"
> > > name="toJndiEnvironment"/></Call><Call id="env"
> > > name="getBean"><Arg>environment</Arg><Call
> > name="setProperty"><Arg><Get
> > > name="INITIAL_CONTEXT_FACTORY" class="
> > javax.naming.Context"/></Arg><Arg>
> > >
> > org.apache.directory.server.jndi.ServerContextFactory</Arg></C
> > all><Call
> > > name="putAll"><Arg><Ref id="jndi-env"/></Arg></Call></Call></New>
> > > INFO | jvm 1 | 2007/07/17 12:50:04 | Configuration
> > Exception: null
> > >
> > > I'm not sure if this is a problem in Jetty, or Apache DS, or our
> > > configuration. Any ideas? Any hints on how to configure
> > logging for a bit
> > > more information? I tried adding a log4j.appender for
> > directory service
> > > but still nothing.
> > >
> > > I'll also post to the Jetty mailing list as well. Thanks.
> > >
> > > Wayne Johnson
> > > Senior Software Engineer
> > > MQSoftware, Inc.
> > > 1660 S Highway 100
> > > Minneapolis, MN 55416
> > > (952) 345-8628
> > >
> > >
> > >
> >
> >
>
RE: Apache DS (I think) fails to load when we upgraded to Jetty 6.1.4 or 6.1.5rc0
Posted by Wayne Johnson <wj...@mqsoftware.com>.
Forgive my ignorance, but can you be a bit more specific on how to turn up logging on Spring? Or is that a question for the Jetty list?
> -----Original Message-----
> From: chris.custine@gmail.com
> [mailto:chris.custine@gmail.com]On Behalf
> Of Chris Custine
> Sent: Tuesday, July 17, 2007 1:57 PM
> To: users@directory.apache.org
> Subject: Re: Apache DS (I think) fails to load when we
> upgraded to Jetty
> 6.1.4 or 6.1.5rc0
>
>
> Try turning up the debug logging for Spring. It looks like Spring is
> getting an NPE somewhere (possibly from loading ApacheDS
> since there is no
> logging from ADS showing up yet). If there were any calls
> going in to ADS,
> I think you would have seen log output. It might also be
> some change to the
> Jetty JNDI impl?
>
> Good luck,
> Chris
>
> On 7/17/07, Wayne Johnson < wjohnson@mqsoftware.com> wrote:
> >
> > I am trying to upgrade our Jetty & Apache DS ( 1.0.0)
> server From Jetty
> > 6.0.1 to Jetty 6.1.4 (or even Jetty 6.1.5rc0) and can't get Apache
> > Directory Service to load. Unfortunately, the only error I
> seem to get is:
> >
> > INFO | jvm 1 | 2007/07/17 12:50:04 | 2007-07-17 12:50:
> 04.642::WARN: Config
> > error at <New id="factory" class="
> >
> org.springframework.context.support.FileSystemXmlApplicationCo
> ntext"><Arg>jetty/server.xml</Arg><Call
> > id="cfg" name="getBean"><Arg>configuration</Arg><Call id="jndi-env"
> > name="toJndiEnvironment"/></Call><Call id="env"
> > name="getBean"><Arg>environment</Arg><Call
> name="setProperty"><Arg><Get
> > name="INITIAL_CONTEXT_FACTORY" class="
> javax.naming.Context"/></Arg><Arg>
> >
> org.apache.directory.server.jndi.ServerContextFactory</Arg></C
> all><Call
> > name="putAll"><Arg><Ref id="jndi-env"/></Arg></Call></Call></New>
> > INFO | jvm 1 | 2007/07/17 12:50:04 | Configuration
> Exception: null
> >
> > I'm not sure if this is a problem in Jetty, or Apache DS, or our
> > configuration. Any ideas? Any hints on how to configure
> logging for a bit
> > more information? I tried adding a log4j.appender for
> directory service
> > but still nothing.
> >
> > I'll also post to the Jetty mailing list as well. Thanks.
> >
> > Wayne Johnson
> > Senior Software Engineer
> > MQSoftware, Inc.
> > 1660 S Highway 100
> > Minneapolis, MN 55416
> > (952) 345-8628
> >
> >
> >
>
>
Re: Apache DS (I think) fails to load when we upgraded to Jetty 6.1.4 or 6.1.5rc0
Posted by Chris Custine <cc...@apache.org>.
Try turning up the debug logging for Spring. It looks like Spring is
getting an NPE somewhere (possibly from loading ApacheDS since there is no
logging from ADS showing up yet). If there were any calls going in to ADS,
I think you would have seen log output. It might also be some change to the
Jetty JNDI impl?
Good luck,
Chris
On 7/17/07, Wayne Johnson < wjohnson@mqsoftware.com> wrote:
>
> I am trying to upgrade our Jetty & Apache DS ( 1.0.0) server From Jetty
> 6.0.1 to Jetty 6.1.4 (or even Jetty 6.1.5rc0) and can't get Apache
> Directory Service to load. Unfortunately, the only error I seem to get is:
>
> INFO | jvm 1 | 2007/07/17 12:50:04 | 2007-07-17 12:50: 04.642::WARN: Config
> error at <New id="factory" class="
> org.springframework.context.support.FileSystemXmlApplicationContext"><Arg>jetty/server.xml</Arg><Call
> id="cfg" name="getBean"><Arg>configuration</Arg><Call id="jndi-env"
> name="toJndiEnvironment"/></Call><Call id="env"
> name="getBean"><Arg>environment</Arg><Call name="setProperty"><Arg><Get
> name="INITIAL_CONTEXT_FACTORY" class=" javax.naming.Context"/></Arg><Arg>
> org.apache.directory.server.jndi.ServerContextFactory</Arg></Call><Call
> name="putAll"><Arg><Ref id="jndi-env"/></Arg></Call></Call></New>
> INFO | jvm 1 | 2007/07/17 12:50:04 | Configuration Exception: null
>
> I'm not sure if this is a problem in Jetty, or Apache DS, or our
> configuration. Any ideas? Any hints on how to configure logging for a bit
> more information? I tried adding a log4j.appender for directory service
> but still nothing.
>
> I'll also post to the Jetty mailing list as well. Thanks.
>
> Wayne Johnson
> Senior Software Engineer
> MQSoftware, Inc.
> 1660 S Highway 100
> Minneapolis, MN 55416
> (952) 345-8628
>
>
>