Teemu,
This is the right place, no worries. It appears both 2.0 and HEAD exhibit the reported
problem. Do you want me to file a bug report on your behalf? Usually we prefer to have
a bugzilla ticket for all known bugs/feature requests, so the bug resolution audit
trail can be retained.
Oleg
-Original Message-
From: Teemu Tingander [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 27, 2004 08:15
To: '[EMAIL PROTECTED]'
Subject: Bug in read timout in subsequnt method execution after
Connection: keep-alive [ 2.0_RC3]
Hi !
Lets hope that this is right place to mail these issues, Im not familiar
with bugzilla so I´ll send this to here !
Apologies to everyone if this is not..
Changing read timeout ()wont affect after successful method execution using
same connection..
This seems to be a bug in HttpClient class method
executeMethod(HostConfiguration ...)..
The problematic section seems to be if section checking if connection is
open
method.setStrictMode(strictMode);
if (!connection.isOpen()) {
connection.setConnectionTimeout(connectionTimeout);
--> connection.setSoTimeout(soTimeout);
connection.open();
if (connection.isProxied() && connection.isSecure()) {
method = new ConnectMethod(method);
}
}
Problem can be solved by moving the line out of if section
method.setStrictMode(strictMode);
connection.setSoTimeout(soTimeout);
if (!connection.isOpen()) {
connection.setConnectionTimeout(connectionTimeout);
connection.open();
if (connection.isProxied() && connection.isSecure()) {
method = new ConnectMethod(method);
}
}
- Teemu
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
