Bugzilla – Bug 1078
UnexpectedReplyCodeException can not be serialized because its private member of type reply is not serializable
Last modified: 2005-12-05 16:04:05
You need to log in before you can comment on or make changes to this bug.
UnexpectedReplyCodeException can not be serialized because its private member of type org.globus.ftp.vanilla.Reply is not serializable. As a subclass of java.lang.Exception the class org.globus.ftp.exception.UnexpectedReplyCodeException is implementing the java.io.Serializable interface and is expected to be serialized successfully if desired. In fermilab destributed application gsiftp client and the initiator of the transfer are located on two different nodes and are communicating via tcp sockets. If error occures it is reported by serializing the serializable throwable sources of errors. If class UnexpectedReplyCodeException is not expected to be seialized then it should be derived from Throwable directly and not from Exception.
Made the Reply class serializable.