Uh oh!
There was an error while loading. Please reload this page.
Add "Serializable" to some classes (#194) - #195
Conversation
During app development using the Azure Java SDK, certain errors were not handled properly, causing NotSerializable exceptions. This changes adds the interface marker to appropriate classes.
Jianghao Lu (jianghaolu)
commented
Aug 18, 2017
itmustbesid How are you serializing them? We serialize some of these types upon every request through Jackson and it has been working for us. |
itmustbesid
commented
Aug 21, 2017
Our setup is a little complex -- we are using a remoting service between two tomcat instances: when the 'client' makes an API call involving the Azure SDK, that request is sent to the 'server'. From what I can tell, the 'server' encounters a CloudError and tries to send that response back to the 'client' ... at this point, we see the error: org.springframework.remoting.RemoteAccessException: Could not access HTTP invoker remote service at [https://127.0.0.2:8443/dt-remote-invoker/remoting/RemotingService]; nested exception is java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: com.microsoft.azure.CloudError Caused by: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: com.microsoft.azure.CloudError Caused by: java.io.NotSerializableException: com.microsoft.azure.CloudError |
itmustbesid
commented
Aug 29, 2017
Jianghao Lu (@jianghaolu) I wondered if you had any more thoughts about this issue and the corresponding pull request? I know it's bad practice to "push" ones own pull requests, but our project manager is hoping this issue can be addressed soon. Many thanks! |
During app development using the Azure Java SDK, certain errors were not handled
properly, causing NotSerializable exceptions. This changes adds the interface
marker to appropriate classes.