[jboss-jira] [JBoss JIRA] Commented: (JBAS-4522) Remoting Connector attribute "socketTimeout" in jboss-service.xml should be "timeout"
Ron Sigal (JIRA)
jira-events at lists.jboss.org
Tue Aug 5 19:52:56 EDT 2008
[ https://jira.jboss.org/jira/browse/JBAS-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12423751#action_12423751 ]
Ron Sigal commented on JBAS-4522:
---------------------------------
Given that the default values are currently in effect, it occurs to me that, when the change is made, the "timeout" parameter should be commented out.
> 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
> 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
More information about the jboss-jira
mailing list