[jira] Commented: (FILEUPLOAD-106) parseRequest randomly throws Stream ended unexpectedly

[ http://issues.apache.org/jira/browse/FILEUPLOAD-106?page=comments#action_12412207 ] Gerald Turner commented on FILEUPLOAD-106: -- User error! The client was running two threads sharing instances of HttpClient FilePart[] while uploading to two

[jira] Created: (FILEUPLOAD-106) parseRequest randomly throws Stream ended unexpectedly

Environment: The client and server environments are all Solaris 9, Java 1.4.2_05, JBoss 3.2.5 running Tomcat 5.0.26 using the default 8080 connector, and separated by a few LANs with very low latency (2ms). Reporter: Gerald Turner Hello, I have an application using FileUpload which intermittently

[jira] Updated: (FILEUPLOAD-106) parseRequest randomly throws Stream ended unexpectedly

[ http://issues.apache.org/jira/browse/FILEUPLOAD-106?page=all ] Gerald Turner updated FILEUPLOAD-106: - Attachment: commons-fileupload-1.2-SNAPSHOT-initCause.patch Patch which adds Throwable.initCause to various rethrows in FileUploadBase

Re: DBCP deadlock patch

Feb 2003, Gerald Turner wrote: Has anyone looked at the bug #16581? I've attached a patch which merely propagates the idle eviction properties to BasicDataSourceFactory. -- Gerald TurnerEmail: [EMAIL PROTECTED]Phone: (503) 788-1720 GPG: 0xFA8CD6D5 21D9 B2E8 7FE7 F19E 5F7D 4D0C

DBCP deadlock patch

Has anyone looked at the bug #16581? I've attached a patch which merely propagates the idle eviction properties to BasicDataSourceFactory. -- Gerald TurnerEmail: [EMAIL PROTECTED]Phone: (503) 788-1720 GPG: 0xFA8CD6D5 21D9 B2E8 7FE7 F19E 5F7D 4D0C 3FA0 810F FA8C D6D5