[
https://jira.jboss.org/jira/browse/JBMESSAGING-1487?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1487:
-----------------------------------------
Also note before 1.4.0.SP3-CP05 the values in config are 10 sec and 5 sec each, but they
don't take effect as those params are not passed to remoting layer. So effectively
remoting defaults are used which is 2 sec and 1 sec respectively. See
https://jira.jboss.org/jira/browse/JBMESSAGING-1482
Change the remoting socket client ping period and ping timeout to
reasonable values
-----------------------------------------------------------------------------------
Key: JBMESSAGING-1487
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1487
Project: JBoss Messaging
Issue Type: Task
Affects Versions: 1.4.0.SP3.CP05, 1.4.2.GA
Environment: All platforms
Reporter: Howard Gao
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP06, 1.4.3.GA
Currently ping period and timeout in remoting-bisocket-service.xml are 2sec and 1 sec, as
<attribute name="validatorPingPeriod"
isParam="true">2000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">1000</attribute>
This is too short in a normal application environment. We need to make these parameters
to a longer period.
Please note: changing these figures has implications on all tests who rely on timing
(like Thread.sleep()) to get correct results. Verify and make all tests pass for new
values.
--
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