当前位置: 代码迷 >> J2EE >> 最近开发EJB3消息驱动BEAN时遇到了一个这样的有关问题 Exception in thread "main" javax.naming.CommunicationException 网上似乎没有看到这样的有关问题 就在某个地方看到一哈 但给出的解决办法?
  详细解决方案

最近开发EJB3消息驱动BEAN时遇到了一个这样的有关问题 Exception in thread "main" javax.naming.CommunicationException 网上似乎没有看到这样的有关问题 就在某个地方看到一哈 但给出的解决办法?

热度:34   发布时间:2016-04-22 01:58:15.0
最近开发EJB3消息驱动BEAN时遇到了一个这样的问题 Exception in thread "main" javax.naming.CommunicationException 网上似乎没有看到这样的问题 就在某个地方看到一哈 但给出的解决方法??
Exception in thread "main" javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: error unmarshalling return; nested exception is:
 java.lang.ClassNotFoundException: org.jboss.mq.referenceable.ObjectRefAddr (no security manager: RMI class loader disabled)]
 at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:722)
 at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
 at javax.naming.InitialContext.lookup(Unknown Source)
 at com.lyh.ejb3.clients.JmsClient_ReservationProducer.main(JmsClient_ReservationProducer.java:40)
Caused by: java.rmi.UnmarshalException: error unmarshalling return; nested exception is:
 java.lang.ClassNotFoundException: org.jboss.mq.referenceable.ObjectRefAddr (no security manager: RMI class loader disabled)
 at sun.rmi.server.UnicastRef.invoke(Unknown Source)
 at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
 at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
 ... 3 more
Caused by: java.lang.ClassNotFoundException: org.jboss.mq.referenceable.ObjectRefAddr (no security manager: RMI class loader disabled)
 at sun.rmi.server.LoaderHandler.loadClass(Unknown Source)
 at sun.rmi.server.LoaderHandler.loadClass(Unknown Source)
 at java.rmi.server.RMIClassLoader$2.loadClass(Unknown Source)
 at java.rmi.server.RMIClassLoader.loadClass(Unknown Source)
 at sun.rmi.server.MarshalInputStream.resolveClass(Unknown Source)
 at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
 at java.io.ObjectInputStream.readClassDesc(Unknown Source)
 at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
 at java.io.ObjectInputStream.readObject0(Unknown Source)
 at java.io.ObjectInputStream.readArray(Unknown Source)
 at java.io.ObjectInputStream.readObject0(Unknown Source)
 at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
 at java.io.ObjectInputStream.readSerialData(Unknown Source)
 at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
 at java.io.ObjectInputStream.readObject0(Unknown Source)
 at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
 at java.io.ObjectInputStream.readSerialData(Unknown Source)
 at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
 at java.io.ObjectInputStream.readObject0(Unknown Source)
 at java.io.ObjectInputStream.readObject(Unknown Source)
 at sun.rmi.server.UnicastRef.unmarshalValue(Unknown Source)
 ... 6 more

最近开发EJB3消息驱动BEAN时遇到了一个这样的问题 Exception in thread "main" javax.naming.CommunicationException 网上似乎没有看到这样的问题 就在某个地方看到一哈 但给出的解决方法觉得模糊。


------解决方案--------------------
问题是什么解决的啊,我也遇到了这个问题了,急求解决方法呢。
  相关解决方案