Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

running jboss 4.0 Startup Error

1 view
Skip to first unread message

Scott

unread,
Mar 17, 2004, 5:44:39 PM3/17/04
to
Hello,

I am new to jboss and the following error is generated upon startup
(run.bat).

17:39:38,012 INFO [Server] Starting JBoss (MX MicroKernel)...
17:39:38,022 INFO [Server] Release ID: JBoss [Zion] 4.0.0DR3 (build:
CVSTag=HEAD date=200403161350)
17:39:38,022 INFO [Server] Home Dir: D:\jboss-4.0.0DR3
17:39:38,022 INFO [Server] Home URL: file:/D:/jboss-4.0.0DR3/
17:39:38,022 INFO [Server] Library URL: file:/D:/jboss-4.0.0DR3/lib/
17:39:38,022 INFO [Server] Patch URL: null
17:39:38,022 INFO [Server] Server Name: default
17:39:38,022 INFO [Server] Server Home Dir:
D:\jboss-4.0.0DR3\server\default
17:39:38,022 INFO [Server] Server Home URL:
file:/D:/jboss-4.0.0DR3/server/default/
17:39:38,042 INFO [Server] Server Data Dir:
D:\jboss-4.0.0DR3\server\default\data
17:39:38,042 INFO [Server] Server Temp Dir:
D:\jboss-4.0.0DR3\server\default\tmp
17:39:38,042 INFO [Server] Server Config URL:
file:/D:/jboss-4.0.0DR3/server/default/conf/
17:39:38,042 INFO [Server] Server Library URL:
file:/D:/jboss-4.0.0DR3/server/default/lib/
17:39:38,042 INFO [Server] Root Deployment Filename:
jboss-service.xml
17:39:38,042 INFO [Server] Starting General Purpose Architecture
(GPA)...
17:39:39,855 INFO [ServerInfo] Java version: 1.3.1_01,Sun
Microsystems Inc.
17:39:39,855 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM
1.3.1_01,Sun Microsystems Inc.
17:39:39,855 INFO [ServerInfo] OS-System: Windows 2000 5.0,x86
17:39:39,935 INFO [ServiceController] Controller MBean online
17:39:40,115 INFO [MainDeployer] Started
jboss.system:service=MainDeployer
17:39:40,306 INFO [MainDeployer] Adding deployer:
org.jboss.deployment.JARDeployer@309468
17:39:40,316 INFO [JARDeployer] Started
jboss.system:service=JARDeployer
17:39:40,356 INFO [MainDeployer] Adding deployer:
org.jboss.deployment.SARDeployer@66aa18
17:39:40,396 INFO [SARDeployer] Started
jboss.system:service=ServiceDeployer
17:39:40,396 INFO [Server] Core system initialized
17:39:40,416 INFO [MainDeployer] Starting deployment of package:
file:/D:/jboss-4.0.0DR3/server/default/conf/jboss-service.xml
17:39:46,114 WARN [NestedThrowable] Duplicate throwable nesting of
same base type: class org.jboss.deployment.DeploymentException is
assignable from: class org.jboss.deployment.DeploymentException
17:39:46,114 ERROR [MainDeployer] could not create deployment:
file:/D:/jboss-4.0.0DR3/server/default/conf/jboss-service.xml
org.jboss.deployment.DeploymentException: create operation failed for
package file:/D:/jboss-4.0.0DR3/server/default/conf/jboss-service.xml;
- nested throwable: (org.jboss.deployment.DeploymentException: -
nested throwable: (java.lang.reflect.UndeclaredThrowableException))
at org.jboss.deployment.SARDeployer.create(SARDeployer.java:229)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:672)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:636)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:620)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:74)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:70)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:168)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:469)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:174)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:384)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:291)
at org.jboss.Main.boot(Main.java:144)
at org.jboss.Main$1.run(Main.java:389)
at java.lang.Thread.run(Thread.java:484)
+ nested throwable:

Can anyone offer any assistance in what may be causing this error.

Thanks in advance,

Scott

Scott

unread,
Mar 19, 2004, 7:47:29 AM3/19/04
to
This turned out to be a path/classpath jvm issue which has been resolved.
0 new messages