[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1733) Update settings in remoting-bisocket-service.xml

[Ron Sigal (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBMESSAGING-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12486487#action_12486487 ] 

Ron Sigal commented on JBMESSAGING-1733:
----------------------------------------

This looks very good.  

Thinking about it some more, I have some reservations about including "writeTimeout" in this group, though.  Originally, the write timeout facility arose from a forum discussion (http://www.jboss.org/index.html?module=bb&op=viewtopic&t=152107&postdays=0&postorder=asc&start=10), where the source of the problem was pulling the network cable.  I guess a firewall that kills inactive connections is similar, but the other parameters in the previous comment should work around the firewall problem.  The write timeout facility also arose recently in a support case, but it's not clear to me what caused the problem in that case.

So, maybe "writeTimeout" could be given its own comment, letting people know the facility is available if, for some reason, they need it.

> Update settings in remoting-bisocket-service.xml
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1733
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1733
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>    Affects Versions: 1.4.0.SP3.CP08
>            Reporter: Justin Bertram
>            Assignee: Howard Gao
>             Fix For: 1.4.0.SP3.CP09
>
>
> Several fixes are going into JBoss Remoting 2.2.3.SP1 (JBREM-1146, JBREM-1147, JBREM-1152) to resolve an issue where JBoss Messaging connections can fail because of a firewall closing its connection.  The settings in remoting-bisocket-service.xml should be changed to accommodate these fixes.  Changes involved will likely be:
>  -reduce "pingFrequency"
>  -reduce "pingWindowFactor"
>  -increase "numberOfCallRetries"
>  -add "generalizeSocketException" and set to "true"
> You will also likely need to change the way JBoss Messaging performs its remoting checks as these settings are likely to cause an error unless "disableRemotingChecks" is set on the connection factory which uses this configuration.
> Please coordinate with Ron Sigal for validation.

-- 
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