[Bug 139] New: JBoss won't run

[email protected] Wed, 22 Jun 2005 23:24:19 -0400
Newsgroups gmane.comp.java.vm.sablevm.bugs
Message-ID <[email protected]>
http://sablevm.org/bugs/show_bug.cgi?id=139

           Summary: JBoss won't run
           Product: SableVM
           Version: trunk
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: default
        AssignedTo: [email protected]
        ReportedBy: [email protected]
         QAContact: [email protected]


I tried running jboss application server, on Suse Linux 9.1, with
sablevm-trunk-4158. I get the following error on the command line:

Warning: -server option not implemented in java-sablevm wrapper.
Warning: -Xms128m option not implemented in java-sablevm wrapper.
Warning: -Xmx128m option not implemented in java-sablevm wrapper.
00:05:13,431 INFO  [Server] Starting JBoss (MX MicroKernel)...
00:05:13,438 INFO  [Server] Release ID: JBoss [Zion] JBoss Inc.
00:05:13,441 INFO  [Server] Home Dir: /home/hfrequency/jboss-4.0.2
00:05:13,443 INFO  [Server] Home URL: file:/home/hfrequency/jboss-4.0.2/
00:05:13,445 INFO  [Server] Library URL: file:/home/hfrequency/jboss-4.0.2/lib/
00:05:13,452 INFO  [Server] Patch URL: null
00:05:13,454 INFO  [Server] Server Name: default
00:05:13,456 INFO  [Server] Server Home Dir:
/home/hfrequency/jboss-4.0.2/server/default
00:05:13,459 INFO  [Server] Server Home URL:
file:/home/hfrequency/jboss-4.0.2/server/default/
00:05:13,461 INFO  [Server] Server Data Dir:
/home/hfrequency/jboss-4.0.2/server/default/data
00:05:13,463 INFO  [Server] Server Temp Dir:
/home/hfrequency/jboss-4.0.2/server/default/tmp
00:05:13,466 INFO  [Server] Server Config URL:
file:/home/hfrequency/jboss-4.0.2/server/default/conf/
00:05:13,468 INFO  [Server] Server Library URL:
file:/home/hfrequency/jboss-4.0.2/server/default/lib/
00:05:13,471 INFO  [Server] Root Deployment Filename: jboss-service.xml
00:05:13,484 INFO  [Server] Starting General Purpose Architecture (GPA)...
Failed to boot JBoss:
java.lang.NullPointerException
   at org.jboss.mx.loading.RepositoryClassLoader.addURL
(RepositoryClassLoader.java:658)
   at java.net.URLClassLoader.addURLs (URLClassLoader.java:782)
   at java.net.URLClassLoader.URLClassLoader (URLClassLoader.java:653)
   at org.jboss.mx.loading.RepositoryClassLoader.RepositoryClassLoader
(RepositoryClassLoader.java:89)
   at org.jboss.mx.loading.UnifiedClassLoader.UnifiedClassLoader
(UnifiedClassLoader.java:95)
   at org.jboss.mx.loading.UnifiedClassLoader.UnifiedClassLoader
(UnifiedClassLoader.java:82)
   at org.jboss.mx.loading.UnifiedClassLoader3.UnifiedClassLoader3
(UnifiedClassLoader3.java:50)
   at org.jboss.mx.loading.UnifiedClassLoader3.UnifiedClassLoader3
(UnifiedClassLoader3.java:62)
   at org.jboss.mx.loading.UnifiedLoaderRepository3.newClassLoader
(UnifiedLoaderRepository3.java:143)
   at java.lang.reflect.Method.invokeNative (Method.java)
   at java.lang.reflect.Method.invoke (Method.java:616)
   at org.jboss.mx.interceptor.ReflectedDispatcher.invoke
(ReflectedDispatcher.java:141)
   at org.jboss.mx.server.Invocation.dispatch (Invocation.java:80)
   at org.jboss.mx.server.Invocation.invoke (Invocation.java:72)
   at org.jboss.mx.server.AbstractMBeanInvoker.invoke
(AbstractMBeanInvoker.java:249)
   at org.jboss.mx.server.MBeanServerImpl.invoke (MBeanServerImpl.java:644)
   at org.jboss.system.server.ServerImpl.initBootLibraries (ServerImpl.java:580)
   at org.jboss.system.server.ServerImpl.doStart (ServerImpl.java:378)
   at org.jboss.system.server.ServerImpl.start (ServerImpl.java:315)
   at org.jboss.Main.boot (Main.java:195)
   at org.jboss.Main$1.run (Main.java:463)
   at java.lang.Thread.run (Thread.java:709)
   at java.lang.VMThread.callRun (VMThread.java:124)
   at java.lang.Thread.callRun (Thread.java:397)
   at java.lang.VirtualMachine.runThread (VirtualMachine.java:137)

I used the startup script run.sh



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.