[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1737) Update ClienSocketWrapper

[Ron Sigal (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBMESSAGING-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ron Sigal updated JBMESSAGING-1737:
-----------------------------------

    Description: JBossMessaging uses its own version of ClientSocketWrapper, which, since it doesn't extend Remoting's org.jboss.remoting.transport.socket.ClientSocketWrapper, can't take advantage of Remoting's new write timeout facility (see JBREM-1120 "Add a socket write timeout facility").    (was: 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.)
       Reporter: Ron Sigal  (was: Justin Bertram)


> Update ClienSocketWrapper
> -------------------------
>
>                 Key: JBMESSAGING-1737
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1737
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>    Affects Versions: 1.4.0.SP3.CP08
>            Reporter: Ron Sigal
>            Assignee: Howard Gao
>             Fix For: 1.4.0.SP3.CP09
>
>
> JBossMessaging uses its own version of ClientSocketWrapper, which, since it doesn't extend Remoting's org.jboss.remoting.transport.socket.ClientSocketWrapper, can't take advantage of Remoting's new write timeout facility (see JBREM-1120 "Add a socket write timeout facility").  

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