Install/Run JBoss 3.0 on NT 4.0

[hedgerow]

I've tried running JBoss 3.0.2 and 3.0.4 on my machine and get the same errors with both versions. I've read Getting Started and searched the forums, but don't see anything similar ( although I didn't look through all 1000+ responses ). Clearly one cannot just download and click; as a minimal example, I had to install the JMX extensions, which may seem obvious but are not mentioned in the manual. I have no problem paying for documentation or even contributing work to the project, but, as with any product, it should be demonstrable that it can run on a pretty vanilla box. I expect my problem is simple to someone, but when first starting with a product, setup should be clear and unambiguous, and nearly foolproof. I did see that some forum responses mentioned "different problems on different platforms/JDK versions"; I don't understand that unless they can be traced to JDK bugs. Anyhow, I've wasted about a day and a half; the product is rapidly moving beyond "free". If anyone could assist so that I could at least get through an initial startup, I would be very appreciative.

My particulars are:

WinNT 4.0, Service Pack 6a

JDK version: 1.4.1_01; JAVA_HOME is set.

The JMX version I just installed is 1.2 and jmxri.jar/jmxtools.jar are in jre/lib/ext.

J2EE 1.3.1 is loaded on my box and J2EE_Home is set; j2ee.jar is on my CLASSPATH.

JAVA_HOME\bin and J2EE_HOME\bin are on my path.

JBoss is the basic download, with Jetty.

The error I am getting is:

javax.management.InstanceNotFoundException: JMImplementation:service=LoaderRepository,name=Default


Following is both the Console and Log output. The only change I have made to to change the drive name to "X"; everything else is exactly the output.

Thanks again for any help. I actually have in mind something that would benefit the promotion of JBoss, but if I can't get it to startup, I'll have to look to something else.



CONSOLE output:
--------------

X:\jboss\bin>run
ECHO is off.
.
JBoss Bootstrap Environment
.
JBOSS_HOME: X:\jboss\bin\\..
.
JAVA: X:\java2\bin\java
.
JAVA_OPTS: -Dprogram.name=run.bat
.
CLASSPATH: ;X:\java2\lib\tools.jar;X:\jboss\bin\\run.jar
.
ECHO is off.
.
18:54:33,582 INFO [Server] JBoss Release: JBoss-3.0.4 CVSTag=JBoss_3_0_4
18:54:33,612 INFO [Server] Home Dir: X:\jboss
18:54:33,612 INFO [Server] Home URL: file:/X:/jboss/
18:54:33,622 INFO [Server] Library URL: file:/X:/jboss/lib/
18:54:33,632 INFO [Server] Patch URL: null
18:54:33,632 INFO [Server] Server Name: default
18:54:33,642 INFO [Server] Server Home Dir: X:\jboss\server\default
18:54:33,642 INFO [Server] Server Home URL: file:/X:/jboss/server/default/
18:54:33,652 INFO [Server] Server Data Dir: X:\jboss\server\default\db
18:54:33,662 INFO [Server] Server Temp Dir: X:\jboss\server\default\tmp
18:54:33,662 INFO [Server] Server Config URL: file:/X:/jboss/server/default/con
f/
18:54:33,722 INFO [Server] Server Library URL: file:/X:/jboss/server/default/li
b/
18:54:33,732 INFO [Server] Root Deployemnt Filename: jboss-service.xml
18:54:33,772 INFO [Server] Starting General Purpose Architecture (GPA)...
18:54:34,263 ERROR [Server] start failed
javax.management.InstanceNotFoundException: JMImplementation:service=LoaderRepos
itory,name=Default
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(Defaul
tMBeanServerInterceptor.java:1011)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultM
BeanServerInterceptor.java:807)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:791
)
at org.jboss.system.server.ServerImpl.initBootLibraries(ServerImpl.java:
435)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:261)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
at org.jboss.Main.boot(Main.java:148)
at org.jboss.Main$1.run(Main.java:381)
at java.lang.Thread.run(Thread.java:536)
javax.management.InstanceNotFoundException: JMImplementation:service=LoaderRepos
itory,name=Default
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(Defaul
tMBeanServerInterceptor.java:1011)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultM
BeanServerInterceptor.java:807)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:791
)
at org.jboss.system.server.ServerImpl.initBootLibraries(ServerImpl.java:
435)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:261)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
at org.jboss.Main.boot(Main.java:148)
at org.jboss.Main$1.run(Main.java:381)
at java.lang.Thread.run(Thread.java:536)
Press any key to continue . . .




LOG output:
----------

18:54:33,572 DEBUG [Server] server type: class org.jboss.system.server.ServerImpl
18:54:33,582 INFO [Server] JBoss Release: JBoss-3.0.4 CVSTag=JBoss_3_0_4
18:54:33,612 DEBUG [Server] Using config: org.jboss.system.server.ServerConfigImpl@161d36b
18:54:33,612 INFO [Server] Home Dir: X:\jboss
18:54:33,612 INFO [Server] Home URL: file:/X:/jboss/
18:54:33,622 INFO [Server] Library URL: file:/X:/jboss/lib/
18:54:33,632 INFO [Server] Patch URL: null
18:54:33,632 INFO [Server] Server Name: default
18:54:33,642 INFO [Server] Server Home Dir: X:\jboss\server\default
18:54:33,642 INFO [Server] Server Home URL: file:/X:/jboss/server/default/
18:54:33,652 INFO [Server] Server Data Dir: X:\jboss\server\default\db
18:54:33,662 INFO [Server] Server Temp Dir: X:\jboss\server\default\tmp
18:54:33,662 INFO [Server] Server Config URL: file:/X:/jboss/server/default/conf/
18:54:33,722 INFO [Server] Server Library URL: file:/X:/jboss/server/default/lib/
18:54:33,732 INFO [Server] Root Deployemnt Filename: jboss-service.xml
18:54:33,772 INFO [Server] Starting General Purpose Architecture (GPA)...
18:54:34,223 DEBUG [Server] Created MBeanServer: com.sun.jmx.mbeanserver.JmxMBeanServer@1d2068d
18:54:34,253 DEBUG [Server] Boot url list: [file:/X:/jboss/server/default/conf/]
18:54:34,253 DEBUG [Server] Creating loader for URL: file:/X:/jboss/server/default/conf/
18:54:34,263 ERROR [Server] start failed
javax.management.InstanceNotFoundException: JMImplementation:service=LoaderRepository,name=Default
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1011)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:807)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:791)
at org.jboss.system.server.ServerImpl.initBootLibraries(ServerImpl.java:435)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:261)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
at org.jboss.Main.boot(Main.java:148)
at org.jboss.Main$1.run(Main.java:381)
at java.lang.Thread.run(Thread.java:536)

[juhalindfors]

Stop installing JMX RI. Where did you get the idea you need to install this?

Just download the distro and unzip it. It's ready to run.

Also get rid of the J2EE RI. You don't need this either.

Please follow the instructions.

[hedgerow]

Thank you. As I indicated, all replies are appreciated. Although yours was not directly helpful, it did lead me to examine my jre/lib/ext directory more closely. It turns out that I had a semblance of "DLL hell", and there were some conflicts between the jars there and what JBoss wanted to use. Once I cleaned those up, JBoss started up more or less normally. I wanted to explain that to possibly help others who find similar problems on install/startup.

I don't think this changes my original point: to simply say, download, unzip and run, ignores some realities on developer and production machines. With products depending more and more on each other, the likelihood of differing, incompatible jars is there. The best thing would be a list of external dependencies to check; the least would be to say that on a clean machine with only x, y, ..., and z installed, you can download, unzip and run. I'm not trying to be particularly critical, it's simply that after wasting a day and a half, many people will just move on. For what that is worth.

I should also say that http://localhost:8082 did not and does not work on my install. While I did find a port conflict ( which also should be mentioned in a startup guide ), after resolving it, the situation was the same. I *was* able to get the page up finally by using

http://localhost:8080/jmx-console

I don't know if that was intended or not, but maybe it will help someone else.

Most of this has been very general, but again, thank you for responding, Juha Lindfors.