Hi Christopher!
Please make sure your CLASSPATH does not point to any archive that
contains a jndi.properties (like the j2ee.jar from SUN). The server
should be able to start with an empty CLASSPATH, try that.

For future reference it would be helpful to know, if this helped. 

Thanks,
Tobias

"Christopher A. Lee" wrote:
> 
> Hi people,
> I've just downloaded the jboss-2.0-FINAL with tomcat distribution, but can't
> seem to make it run. This is the output to the console:
> 
> [d:\prj\jboss_tomcat\jboss-2.0-final\bin]run.bat
> Using configuration "default"
> [Console logging] Initialized
> [Classpath extension] Initializing
> [Classpath extension] Initialized
> [File logging] Initializing
> [File logging] Initialized
> [Classpath extension] Initializing
> [Classpath extension] Initialized
> [Classpath extension] Initializing
> [Classpath extension] Initialized
> [Info] Java version: 1.3.0,Sun Microsystems Inc.
> [Info] Java VM: Java HotSpot(TM) Client VM 1.3.0-C,Sun Microsystems Inc.
> [Info] System: Windows 2000 5.0,x86
> [Classpath extension] Initializing
> [Classpath extension] Initialized
> [JDBC] Loaded JDBC-driver:org.hsql.jdbcDriver
> [JDBC] Loaded JDBC-driver:org.enhydra.instantdb.jdbc.idbDriver
> [Webserver] Initializing
> [Webserver] Initialized
> [Hypersonic] Initializing
> [Hypersonic] Initialized
> [Naming] Initializing
> [Naming] Naming started on port 1099
> [Naming] Initialization failed
> [Naming] javax.naming.NameNotFoundException: Invalid name:
> [Naming]        at
> com.sun.enterprise.naming.java.javaURLContext.getRelativeName(javaURLContext
> .java:424)
> [Naming]        at
> com.sun.enterprise.naming.java.javaURLContext.getComponentContext(javaURLCon
> text.java:382)
> [Naming]        at
> com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:51)
> [Naming]        at javax.naming.InitialContext.lookup(Unknown Source)
> [Naming]        at
> org.jboss.naming.NamingService.initService(NamingService.java:62)
> [Naming]        at
> org.jboss.util.ServiceMBeanSupport.init(ServiceMBeanSupport.java:66)
> [Naming]        at
> org.jboss.util.ServiceMBeanSupport.preRegister(ServiceMBeanSupport.java:161)
> [Naming]        at
> com.sun.management.jmx.MBeanServerImpl.preRegisterInvoker(MBeanServerImpl.ja
> va:2245)
> [Naming]        at
> com.sun.management.jmx.MBeanServerImpl.createMBean(MBeanServerImpl.java:513)
> [Naming]        at
> javax.management.loading.MLet.getMBeansFromURL(MLet.java:523)
> [Naming]        at
> javax.management.loading.MLet.getMBeansFromURL(MLet.java:369)
> [Naming]        at org.jboss.Main.<init>(Main.java:119)
> [Naming]        at org.jboss.Main$1.run(Main.java:87)
> [Naming]        at java.security.AccessController.doPrivileged(Native
> Method)
> [Naming]        at org.jboss.Main.main(Main.java:83)
> 
> ...And lots of other NameNotFoundExceptions. I assume that this is all
> because of the naming service failing, but I have no idea how to find out
> what's wrong with my set-up since it won't work.
> 
> I'm completely green with respect to J2EE-servers, so I may be missing
> something elementary. Is there a way to run jboss in a more verbose mode and
> make Naming tell what causes it to fail?
> Any help or pointers for what to look for would be greatly appreciated.
> 
> /Christopher
> 
> --
> --------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> List Help?:          [EMAIL PROTECTED]


--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
List Help?:          [EMAIL PROTECTED]

Reply via email to