[jboss-jira] [JBoss JIRA] Commented: (JBAS-4522) Remoting Connector attribute "socketTimeout" in jboss-service.xml should be "timeout"

[Ron Sigal (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12426766#action_12426766 ] 

Ron Sigal commented on JBAS-4522:
---------------------------------

On the server side, the default is 60000 ms.  For the socket and bisocket transports, the default is 1800000 (30 minutes) on the client side.

> Remoting Connector attribute "socketTimeout" in jboss-service.xml should be "timeout"
> -------------------------------------------------------------------------------------
>
>                 Key: JBAS-4522
>                 URL: https://jira.jboss.org/jira/browse/JBAS-4522
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA,  JBossAS-5.0.0.Beta3, JBossAS-Branch_4_0
>            Reporter: Ron Sigal
>            Assignee: Dimitris Andreadis
>             Fix For: JBossAS-5.0.0.CR2, JBossAS-4.2.4.GA
>
>
> I noticed that in jboss-service.xml, the ""jboss.remoting:service=Connector,transport=socket" MBean has a "socketTimeout" parameter.
> The "socketTimeout" parameter, which was specific to the socket transport, has been obsolete since Remoting 1.4.1 (see JBREM-329).  It was replaced by "timeout", which is used by all transports.

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