[
http://jira.jboss.com/jira/browse/JBAS-4254?page=comments#action_12394946 ]
Galder Zamarreno commented on JBAS-4254:
----------------------------------------
AS 4.0.x has gone into maintenance mode and hence, this feature won't be
implemented. See:
http://www.redhat.com/security/updates/jboss_notes/
Legacy JRMP/Pooled/HTTP invokers will not be developed
further and they're being replaced by Remoting based invokers. For
AS/EAP 4.2.x/4.3.x, read timeout can be configured setting the timeout
parameter in the invoker configuration.
See JBREM-329.
Client read timeout setting wanted for HTTP Invoker
----------------------------------------------------
Key: JBAS-4254
URL:
http://jira.jboss.com/jira/browse/JBAS-4254
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: JBossAS-4.0.3 SP1
Reporter: Anders Welen
Assigned To: Galder Zamarreno
Priority: Minor
There is no read timeout setting to prevent client threads from hanging while using the
HTTP Invoker.
A quick fix (if you are using SUN JVM) is to use the parameter
"-Dsun.net.client.defaultReadTimeout=60000". The problem with this solution is
that it affects all connection, not just the HTTPInvoker.
A solution that works (if Java 5 is used) is to add a call to the method
"setReadTimeout(xxx)" on the "conn" variable in the method
"invoke()" in "org.jboss.invocation.http.interfaces.Util".
(The same problem exists with the standard JRMP Invoker aswell. It's just the Pooled
Invoker that has a read timeout)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira