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

[572 byte] By [AlfredTheGreya] at [2007-11-27 3:36:59]
# 1
i've seen a lot of reports of that. I'm pretty sure it's in the SSL or JCE part of JDK 1.6. The stack trace is coming from the SSL handshake: at that point it hasn't started serializing yet.
ejpa at 2007-7-12 8:40:15 > top of Java-index,Core,Core APIs...
# 2
Thanks for the reply. I was having a hard time tracking down the frequency of this problem.Do you know whether this has been written up as a bug?Thanks again for responding.-Dennis
AlfredTheGreya at 2007-7-12 8:40:15 > top of Java-index,Core,Core APIs...
# 3
Not sure about that, but it's been discussed quite a bit in the JSSE forum. That's the place to look.
ejpa at 2007-7-12 8:40:15 > top of Java-index,Core,Core APIs...
# 4
Moving to : http://forum.java.sun.com/thread.jspa?threadID=5167489&tstart=0I posted more info found using -Djavax.net.debug=allLet me know if this gives any clues. Thank you!-DennisMessage was edited by: AlfredTheGrey
AlfredTheGreya at 2007-7-12 8:40:15 > top of Java-index,Core,Core APIs...