MySQL Bugs: #10371: Windows IPSEC implementation breaks connection in heavy traffic conditions

Bug #10371	Windows IPSEC implementation breaks connection in heavy traffic conditions
Submitted:	4 May 2005 21:35	Modified:	14 Jun 2005 21:55
Reporter:	Sandro Galfo	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	Connector / J	Severity:	S2 (Serious)
Version:	3.1-nightly-20050501	OS:	Windows (Windows XP Professional)
Assigned to:		CPU Architecture:	Any

Description:
I am using the standard IPSEC policy implementation from the Windows OS to encrypt and authenticate traffic to port 3306.
This all works fine unless I try to upload large amounts of data e.g. BLOBs to the server. Then I get a 'Connection reset by peer' exception. If I temporary disable the encryption/authentication policy all is working fine again.

How to repeat:
Server:
Windows XP Professional Service Pack 2
MYSQL Server 5.0.4 beta

Client:
Windows XP Professional Service Pack 2
JRE 1.5.0_02
Connector/J 3.1-nightly-20050501

Stored Procedure on the Server (LONGBLOB as IN_PARAM) called by PrepareStatement, setBinaryStream, executeUpdate()

Suggested fix:
Maybe a problem with the REVEIVE_BUFFER_SIZE or connection timeout problems

Could you please write here sample test case of client ?

Client Java application for uploading BLOBs to MySQL

Attachment: RepositoryUploader.java (text/plain), 2.55 KiB.

I have attached some files to the bug submission. Feel free to contact me when you need further information.

This seems to be an issue with Microsoft's IPSEC implementation more than the JDBC driver or the VM. There are no options that can be set from a Java application's point of view that would cause this kind of thing to happen (or to fix it).

Maybe you're exceeding an MTU somewhere along the line in the "virtual" side of your VPN?