[JUDDI-334] Marshaling error when calling getTransferToken method via the RMI custody transfer interface.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 3.0
• Fix Version/s: 3.0.1
• Component/s: core
• Assignee: Kurt Stam
• Reporter: Marek Baluch
• Created: 04/Jan/10 10:51
• Updated: 24/May/11 21:35
• Resolved: 04/Jan/10 14:03

Description

A NotSerializableException exception is thrown when trying to retrieve a transfer token via the custody transfer RMI interface. This is caused by the javax.xml.ws.Holder class because it is not serializable.

Stack trace:

error marshalling arguments; nested exception is: java.io.NotSerializableException: javax.xml.ws.Holder
sun.rmi.server.UnicastRef.invoke(UnicastRef.java:138)
at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:178)
at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:132)
at $Proxy12.getTransferToken(Unknown Source)
at org.jboss.soa.esb.qa.tests.failover.juddi.v3.JUDDIRMIPublishingTest.testCustodyTransfer(JUDDIRMIPublishingTest.java:241)
23 lines not shown

Caused by javax.xml.ws.Holder
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
at sun.rmi.server.UnicastRef.marshalValue(UnicastRef.java:274)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:178)
at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:132)
at $Proxy12.getTransferToken(Unknown Source)
at org.jboss.soa.esb.qa.tests.failover.juddi.v3.JUDDIRMIPublishingTest.testCustodyTransfer(JUDDIRMIPublishingTest.java:241)
23 lines not shown

Issue Links

• duplicates: JUDDI-252 RMI broken for Subscription API