[
https://issues.apache.org/jira/browse/QPID-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14063979#comment-14063979
]
Matheus Morais commented on QPID-2969:
--------------------------------------
Hi,
I'm trying to use Qpid C++ broker with Oracle Weblogic (10.3.6) through an
external JNDI server. When I try to post messages in a queue on the broker
using an sample implementation
(https://blogs.oracle.com/soaproactive/entry/jms_step_2_using_the), I can see
the following stacktrace:
Exception in thread "Main Thread" javax.naming.ConfigurationException [Root
exception is java.rmi.MarshalException: error marshalling return; nested
exception is:
java.io.NotSerializableException:
org.apache.qpid.client.AMQConnectionFactory]
at
weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:38)
at
weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:68)
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:392)
at QueueSend.init(QueueSend.java:50)
at QueueSend.main(QueueSend.java:91)
Caused by: java.rmi.MarshalException: error marshalling return; nested
exception is:
java.io.NotSerializableException:
org.apache.qpid.client.AMQConnectionFactory
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:237)
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.NotSerializableException:
org.apache.qpid.client.AMQConnectionFactory
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
at
weblogic.rjvm.MsgAbbrevOutputStream.writeObject(MsgAbbrevOutputStream.java:618)
at
weblogic.utils.io.ChunkedObjectOutputStream.writeObject(ChunkedObjectOutputStream.java:63)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:668)
at
weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:523)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
at
weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:119)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
I believe that is related to this bug. Anyone is looking to fix this soon?
Seems to be pretty easy to solve...
Thanks.
> 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
>
> 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]
