Java libraries not found when JBoss is run as NT service

JBoss boot.log file

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?

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

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

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

Logged In: YES
user_id=95900

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

Logged In: YES
user_id=772366

I tried adding "concurrent.jar" to the classpath and got a "No
class loader available" exception.

However, making the classpath entry in the shutdown.jar the
same as the one in the run.jar (../client/getopt.jar) seems to
fix it. Maybe this is the solution.

Regards,
vladchuk

Logged In: YES
user_id=576153

I have tried Sacha's suggestions and now it works. Thanks -
Richard

Logged In: YES
user_id=95900

I don't think this can be really fixed:

1) when running Shutdown from the command line, Class-
Path entries in the manifest of shutdown.jar are required and
removing them (and putting them in the shell script instead)
would break existing client using the JAR directly instead of
the shells

2) in your scenario, you want shutdown.jar to be part of the
boot classpath, this lead to classlading issue => we must
clean its Class-Path entry to run correctly.

Furthermore, with your solution I am not even sure everything
is fine as shutdown.jar contains jndi.properties and I suspect
it may interfere with JBoss conf/jndi.properties which tend to
avoid serialization.

The easiest solution would be to put Shutdown classes (and
only these) in run.jar.

Logged In: YES
user_id=123848

If you take out shutdown.jar from your classpath, and change
your stop command to the following:

-stop org.jboss.Main -method systemExit

everything will work as expected.

I got that tip from:

http://www.gogis.nl/en/public_documentation/jboss/body.html#JBoss_service_Windows

-Frank

Logged In: YES
user_id=175228

All issues have been moved to http://jira.jboss.com. Existing
issues have been moved. New issues will be closed with this
canned reponse.