Hi all,

I have almost exactly the same problem. Any help is much appreciated.
14:53:33,708 ERROR [NamingService] Starting failed jboss:service=Naming
  | java.lang.ClassCastException: javax.naming.CompoundName
  |         at 
org.jboss.naming.NamingService.startService(NamingService.java:235)
  |         at 
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
  |         at 
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
  |         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  |         at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  |         at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  |         at java.lang.reflect.Method.invoke(Method.java:585)
  | ...
  | 
I'm messing around with the original installation, and am probably missing some 
thing (or possibly using a 4.0.0 artefact). I get this exception at the very 
beginning of JBoss' startup.

On line 235 of NamingService, there's the following:
String value = (String) env.get(key);
This seems the suggest that there's a problem with the enviroment. This is also 
what I've been tinkering with, but I'm having a tough time localizing the 
cause. I don't know why I'm getting a CompoundName instead of a String.

Thanks!

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3885482#3885482

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3885482


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to