Hi All
When talking over SSL to a BEA WLI server, it responds with a
"Connection: close" header, and seems to close the socket, before Apache
Synapse (using HttpCore/NIO) could read the full message (~11K in size).
Its setting the 'Content-length' header, but when debugging the SSL
communication, we see that the full reply never reaches the client.
0580: 22 68 74 74 70 3A 2F 2F 77 77 77 2E 69 62 7A 2E "http://www.xxx.
0590: 72 72 6E 2E 66 67 6F 76 2E 62 65 2F 58 53 44 2F xxx.xxxx.xx/XSD/
05A0: 78 6D 32 35 2F 72 6E 32 D7 DF 5D F5 F3 3F F2 10 xm25/rn2..]..?..
05B0: EB C2 AF F9 C4 F7 B4 49 .......I
2008-07-10 23:49:01,959 [127.0.1.1-asankha] [I/O dispatcher 2] DEBUG
SSLIOSession I/O session sslclient-4 [interested ops: [r]; ready ops:
[r]][SSL handshake status: NOT_HANDSHAKING][1901][0][0][0]: 1448 bytes read
2008-07-10 23:49:01,959 [127.0.1.1-asankha] [I/O dispatcher 2] DEBUG
SSLIOSession I/O session sslclient-4 [interested ops: [r]; ready ops:
[r]][SSL handshake status: NOT_HANDSHAKING][1901][0][0][0]: -1 bytes read
2008-07-10 23:49:01,977 [127.0.1.1-asankha] [HttpClientWorker-2] ERROR
AxisEngine Error in extracting message properties
org.apache.axis2.AxisFault: Error in extracting message properties
Is this something possible when using "Connection: close" ? and if so,
what can a client do to prevent loosing the reply
thanks
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
