In my work area I found
./server/default/deploy/jmx-rmi-adaptor.sar/META-INF/MANIFEST.MF
Specification-Title: JBoss-3.0.4RC1
Specification-Version: 3.0.4RC1
Implementation-Version: 3.0.4RC1 Date:200211010051
Implementation-Title: JBoss-3.0.4RC1 CVSTag=Branch_3_0
Not sure if this is common to everybody else though.
Well I just did a ./build.sh clean and that seems to have fixed things.
08:06:20,493 INFO [Server] JBoss (MX MicroKernel) [3.0.4
Date:200211050757] Started in 0m:22s:738ms
This brings me to question though .. if I'm online via ppp and I
startup "all" via ./build.sh run-jboss it won't come all the way up.
The last thing reported in the log is
08:11:37,154 INFO [DefaultPartition] Initializing
08:11:37,202 INFO [ClusterPartition] Created
08:11:37,203 INFO [HASessionStateService] Creating
08:11:37,222 INFO [HASessionStateService] Created
08:11:37,224 INFO [HANamingService] Creating
08:11:37,294 INFO [HANamingService] Created
08:11:37,296 INFO [JRMPInvokerHA] created
08:11:37,296 INFO [ClusterPartition] Starting
08:11:37,297 INFO [ClusterPartition] Connecting to channel
If I start up "default"
it will come all the way up.
So, what is it that holds things up when I'm online via ppp and is
there anything I can do so that I can bring up "all" when I'm online?
-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
