[JBoss-dev] [ jboss-Bugs-732964 ] Java libraries not found when JBoss is run as NT service

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Bugs item #732964, was opened at 2003-05-06 01:14
Message generated for change (Comment added) made by slaboure
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=732964&group_id=22866

Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 9
Submitted By: vladchuk (vladchuk)
Assigned to: Nobody/Anonymous (nobody)
Summary: Java libraries not found when JBoss is run as NT service

Initial Comment:
JBoss version: 3.2.1
OS: Windows2000 Server SP3, WindowsXP Professional
JDK: 1.4.1_02

When attempted to run as NT service using the 
command file provided in FAQ forum and javaservice.exe
as service launcher JBoss invariably fails as follows: 
(this is the full content of the boot.log):

java.lang.NoClassDefFoundError: 
EDU/oswego/cs/dl/util/concurrent/ConcurrentReaderHas
hMap

Please see the attached file for full stack trace.

The 3.0.x version did not have this problem and every 
3.2.x (including beta releases) exibited this behavior.

----------------------------------------------------------------------

>Comment By: Sacha Labourey (slaboure)
Date: 2003-05-09 19:32

Message:
Logged In: YES 
user_id=95900

can you try by adding "../lib/concurrent.jar" to the Class-Path 
line in shutdown.jar?

----------------------------------------------------------------------

Comment By: vladchuk (vladchuk)
Date: 2003-05-09 19:09

Message:
Logged In: YES 
user_id=772366

I found a workarond for the problem: somebody put a 
classpath entry in the manifest file for the shutdown.jar 
beginning with 3.2.x. For some reason this interferes with the 
JBoss class loading. So removing that entry/manifest file/jar 
file will allow one to run successfully.

I did not try the javant service runner but I looked at the 
configuration and it appears that it runs fine because there is
no "shutdown.jar" in the configuration classpath. I bet that if 
that is addad it will exhibit the behavior I described.

I can close the bug but it is not really fixed until someone 
explains the behavior and/or fixes the "shutdown.jar".

Regards,
vladchuk

----------------------------------------------------------------------

Comment By: Sacha Labourey (slaboure)
Date: 2003-05-09 15:14

Message:
Logged In: YES 
user_id=95900

Can you please try with the tool provided in JBoss CVS: 
contrib/ntservice.

There's even a 3.2 configuration file that I've tested and works.

Close this bug if that tool solves your problem

cheers,

sacha

----------------------------------------------------------------------

Comment By: Greg Emerick (gemerick)
Date: 2003-05-07 23:09

Message:
Logged In: YES 
user_id=539251

I am having the same problem on 3.2.1 (3.2.0 is fine). I got 
around this by excluding shutdown.jar from the classpath.  
So jboss will start, but not stop, as a service.  Here is my 
javaservice cmd to get it going:

JavaService -install default %Java_Home%
\jre\bin\server\jvm.dll -Xms768m -Xmx768m -
Djava.class.path=%Java_Home%\lib\tools.jar;%
JBoss_Home%\bin\run.jar; -start org.jboss.Main -params -c %
2 -stop org.jboss.Shutdown -params -S -out %JBoss_Home%
\server\%2\log\stdout.log -err %JBoss_Home%\server\%2
\log\stderr.log -current %JBoss_Home%\bin

----------------------------------------------------------------------

Comment By: Richard Maher (rmaher)
Date: 2003-05-07 20:49

Message:
Logged In: YES 
user_id=576153

I am experiencing the same problem. I can not run version 
3.2.1 as an NT service. Can someone please help?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=732964&group_id=22866