For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 5 replies, 3 voices, and was last updated 21 years, 10 months ago by
iloginc.
-
AuthorPosts
-
ilogincMemberHello,
I get this exception when I try to shutdown the JBoss jboss-4.0.0DR3 with the Eclipse 3.0M8 compliant version of the MyEclipse:
————————————————————————————
————————————————————————————
javax.naming.NamingException: Could not dereference object [Root exception is javax.naming.CommunicationException [Root exception is java.lang.ClassNotFoundException: org.jboss.jmx.adaptor.rmi.RMIAdaptor (no security manager: RMI class loader disabled)]] at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:969)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:612)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:506)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at org.jboss.Shutdown.main(Shutdown.java:182)
Caused by: javax.naming.CommunicationException [Root exception is java.lang.ClassNotFoundException: org.jboss.jmx.adaptor.rmi.RMIAdaptor (no security manager: RMI class loader disabled)] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:651)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:506)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:963)
… 4 more
Caused by: java.lang.ClassNotFoundException: org.jboss.jmx.adaptor.rmi.RMIAdaptor (no security manager: RMI class loader disabled) at sun.rmi.server.LoaderHandler.loadProxyClass(LoaderHandler.java:531)
at java.rmi.server.RMIClassLoader$2.loadProxyClass(RMIClassLoader.java:639)
at java.rmi.server.RMIClassLoader.loadProxyClass(RMIClassLoader.java:309)
at sun.rmi.server.MarshalInputStream.resolveProxyClass(MarshalInputStream.java:241)
at java.io.ObjectInputStream.readProxyDesc(ObjectInputStream.java:1469)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1432)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1626)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
at java.rmi.MarshalledObject.get(MarshalledObject.java:135)
at org.jnp.interfaces.MarshalledValuePair.get(MarshalledValuePair.java:30)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:549)
… 7 more
Exception in thread “main”
————————————————————————————
————————————————————————————The startup process goes fine.
This is the config in the JBoss 4 panel:
Server Name : default
XML Document Builder Factory Class: org.apache.crimson.jaxp.DocumentBuilderFactoryImpl
SAX Parser Factory Class: org.apache.crimson.jaxp.SAXParserFactoryImpl
Optional Program Arguments:
Optional Shutdown Argument: –shutdownEnv:
Eclipse 3.0M8
JDK 1.4.2_04
MyEclipse: EnterpriseWorkbenchInstaller_030702.exe
JBoss: jboss-4.0.0DR3Has anyone had this before?
Any ideas how to solve it??
Thanks,
CleoApril 15, 2004 at 10:37 am #206036
Riyad KallaMemberCleo,
This is strange, I’ll ask our resident JBoss masters to weigh in on this.April 15, 2004 at 10:43 am #206039
Riyad KallaMemberCleo,
It seems our resident JBoss guy is out of the office this week, we are going to try and research this for you anyway and see what we find out. FOr the time being, if JBoss process isn’t stopping, killing it from the debug view should do the trick.Please stay tuned.
April 15, 2004 at 11:51 am #206053
ilogincMemberRiyad,
Thanks for looking into it.
Yeah, killing the process is what I am currently doing (as a workaround) , but (as you know) that does not give JBoss and all its services the chance do their cleanup as they should.
I will be checking back often to hear from you on this.
Thanks again.
CleoApril 19, 2004 at 5:26 pm #206172
Scott AndersonParticipantI just verified this problem on JBoss 4.0DR3. Looks like they’ve changed their configuration a bit so the shutdown connection needs a bit of work. I opened a bug report and we’ll take care of it in the next release. Thanks for taking the time to report it.
April 19, 2004 at 11:43 pm #206186
ilogincMemberWill this fix be available in for Eclipse 3.0M9 whenever it comes out? This is what I am currently using (3.0M8).
Thanks,
Cleo -
AuthorPosts
