[
https://jira.jboss.org/jira/browse/EJBTHREE-2024?page=com.atlassian.jira....
]
jaikiran pai resolved EJBTHREE-2024.
------------------------------------
Fix Version/s: EJB3_1 1.0.5
Resolution: Done
Component Fix Version(s): jboss-ejb3-core:1.2.3
Timeout has now been set to 5 minutes (as discussed in forum thread)
Set a sensible timeout on EJB3 remoting connector
-------------------------------------------------
Key: EJBTHREE-2024
URL:
https://jira.jboss.org/jira/browse/EJBTHREE-2024
Project: EJB 3.0
Issue Type: Task
Components: core
Affects Versions: EJB3_1 1.0.4
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: EJB3_1 1.0.5
Recent hanging jobs on Mike have shown that the remoting client socket timeout (default =
30 mins) doesn't work because of JBREM-1188. The workaround to the issue is to
explicitly set a timeout value. Even if it wasn't a bug, the default timeout of 30
minutes is a bit too high. Maybe a timeout of 10 minutes (or lesser) would be sufficient.
I'll open a forum thread just in case someone has any inputs for a sensible timeout
value.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira