Is this a serialization bug or https?
http://forums.java.net/jive/thread.jspa?threadID=26115
The only reason i ask, is that we are serializing plain old java objects back to the client which worked fine under 1.5 and since we have some clients moving to 1.6, we now see this error.
I'm starting to wonder if it could be right here:
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:230)
at com.mycompany.hm.callq.client.common.HttpMessage.sendPostObject(HttpMessage.java:227)
Any thoughts are greatly welcomed!
-Dennis

