The log4j classes have been in the lib/ext directory for quite a while now
(at least a month) as the Log4jService requires this.
I just pulled down a clean cvs co and built it and the server came up
without any problems. This is at Wed Apr 25 21:47:24 GMT. The
jbosstest suite is running normally against the build.
----- Original Message -----
From: "Chris Kimpton" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 25, 2001 10:20 AM
Subject: Re: [JBoss-dev] jboss daily test results
> Hi,
>
>
> >From: "Scott M Stark" <[EMAIL PROTECTED]>
> >
> >Something is amiss with your server as these errors are all related to
> >the JMX connector not being bound in JNDI and I don't see this
> >problem. When I run the tests I am seeing the same errors as before.
>
> Perhaps it ran during the middle of a set of commits and got an inconsistent
> snapshot - it currently runs around 2:30AM GMT - I wonder if a few hours
> later maybe better.
>
>
> I tried to re-run the tests now, but the server fails to start - complains
> about not finding log4j classes - but it runs when these are added to the
> system classpath - does jaas now use these and thus the Class-Path in the
> manifest need to be updated? and the jar moved to dist/lib ?
>
> Regards,
> Chris
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
