Mailing-List: contact users-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@directory.apache.org
Received-SPF: pass (herse.apache.org: domain of chris.custine@gmail.com
 designates 66.249.90.181 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
        b=sFa9HD/JcbOFcKUSdKfyVHNjeCjzRm3p9bfaaP86M+oQV5J7DEDWyEVp9uw9Q59TmXxCIRvwUburTmUhxqJzeLV3TkeaxPB6jDoLNfVeccPOcGTDiGlRHRBUP7+BRRvhltLXSOARoZ0CFJ4D7nmyRsWhX2CcDM3+7fby1ra4ygQ=
Message-ID: <43b026c70707171157g73bc8e0al9ba953b34194b1ca@mail.gmail.com>
Date: Tue, 17 Jul 2007 12:57:12 -0600
From: "Chris Custine" <ccustine@apache.org>
Sender: chris.custine@gmail.com
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
In-Reply-To: <63BEA5E623E09F4D92233FB12A9F7943C41252@emailmn.mqsoftware.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_82473_11274903.1184698632338"
References: <63BEA5E623E09F4D92233FB12A9F7943C41252@emailmn.mqsoftware.com>

------=_Part_82473_11274903.1184698632338
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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
>
>
>

------=_Part_82473_11274903.1184698632338--