[
https://issues.apache.org/jira/browse/QPID-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068946#comment-14068946
]
Matheus Morais commented on QPID-2969:
--------------------------------------
Hi,
I was doing a test and now I can see the following error:
[IoReceiver - localhost/127.0.0.1:5672] INFO
org.apache.qpid.client.security.DynamicSaslRegistrar - Additional SASL
providers successfully registered.
[IoReceiver - localhost/127.0.0.1:5672] INFO
org.apache.qpid.client.security.CallbackHandlerRegistry - Callback handlers
available for SASL mechanisms: [EXTERNAL, GSSAPI, CRAM-MD5-HASHED, CRAM-MD5,
AMQPLAIN, PLAIN, ANONYMOUS, SCRAM-SHA-1, SCRAM-SHA-256]
[main] INFO org.apache.qpid.client.AMQConnection - Connection 1 now connected
from /127.0.0.1:42256 to localhost/127.0.0.1:5672
Exception in thread "main" javax.naming.CommunicationException [Root exception
is java.rmi.UnmarshalException: failed to unmarshal class java.lang.Object;
nested exception is:
java.io.InvalidClassException:
org.apache.qpid.client.AMQAnyDestination; no valid constructor]
at
weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:74)
at
weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:472)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:428)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at QueueSend.init(QueueSend.java:53)
at QueueSend.main(QueueSend.java:91)
Caused by: java.rmi.UnmarshalException: failed to unmarshal class
java.lang.Object; nested exception is:
java.io.InvalidClassException:
org.apache.qpid.client.AMQAnyDestination; no valid constructor
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:245)
at
weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
at
weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at weblogic.jndi.internal.ServerNamingNode_1036_WLStub.lookup(Unknown
Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:424)
... 4 more
Caused by: java.io.InvalidClassException:
org.apache.qpid.client.AMQAnyDestination; no valid constructor
at
java.io.ObjectStreamClass$ExceptionInfo.newInvalidClassException(ObjectStreamClass.java:150)
at
java.io.ObjectStreamClass.checkDeserialize(ObjectStreamClass.java:768)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1772)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at
weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:208)
at
weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:599)
at
weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:204)
at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:243)
... 8 more
Maybe something is missing from class AMQAnyDestination?
> AMQConnectionFactory is not Serializable
> ----------------------------------------
>
> Key: QPID-2969
> URL: https://issues.apache.org/jira/browse/QPID-2969
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.8
> Reporter: Gordon Sim
> Labels: serialization
> Attachments:
> 0001-QPID-2969-Make-AMQConnectionFactory-and-AMQDestinati.patch
>
>
> It should be, in order to allow it to be stored in JNDI.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
