reason for this mail:
I am having to work with a web server which deos not
understand the 100-continue header and as a result am
having problem uploading large files as the server
closes the connection before the entire content is
transmitted. A change for this has been addressed in
the Bugzilla
Hi Folks,
It seems that SimpleConnectionManager is unable to properly manage sessions over
multiple threads (in rc2, atleast). Is it even supposed to? (I don't see anything in
the docs that mentions yay or nay.) The problem is that
SimpleConnectionManager.getConnection() calls close on the
Hi Sam,
The SimpleHttpConnectionManager is not meant to be used by more than
one thread. Threading is not explicitly mentioned, though it is
implied by the JavaDocs.
From SimpleHttpConnectionManager: A connection manager that provides
access to a single HttpConnection. This manager makes
Hi Mike,
I had suspected as much. Luckily, we only used SimpleHttpConnectionManager for Mac
Classic's (since they use Java 1.1.8, and it wasn't really worth it to alter
MultiThreadedConnectionManager for a dwindling userbase). It wouldn't hurt to create
a new connection manager for each
