[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-851) Issue with remoting MAX_RETRIES

[Tim Fox (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-851?page=all ]

Tim Fox updated JBMESSAGING-851:
--------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017573#4017573
              Description: 
Currently remoting socket/bisocket transport MAX_RETRIES attribute is non configurable via the xml remoting config.

This means if a client is making a lot of concurrent invocations and they take some significant time to execute then, the client invocations may timeout and throw an exception back to the client, since they have waited longer than 30 seconds (MAX_RETRIES * 1000 ms) to obtain a connection from the pool.

This may be unacceptable to the client who is quite happy to wait an indefinite period (or at least a period longer than 30 seconds) to obtain a connection.

MAX_RETRIES (currently hardcoded to 30) needs to be configurable via the xml config.

Also the sleep interval (currently 1000 ms) needs to be made configurable too.

See forum thread for a real world example of this problem.

  was:
Currently remoting socket/bisocket transport MAX_RETRIES attribute is non configurable via the xml remoting config.

This means if a client is making a lot of concurrent invocations and they take some significant time to execute then, the client invocations may timeout and throw an exception back to the client, since they have waited longer than 30 seconds (MAX_RETRIES * 1000 ms) to obtain a connection from the pool.

This may be unacceptable to the client who is quite happy to wait an indefinite period (or at least a period longer than 30 seconds) to obtain a connection.

MAX_RETIES (currently hardcoded to 30) needs to be configurable via the xml config.

Also the sleep interval (currently 1000 ms) needs to be made configurable too.

See forum thread for a real world example of this problem.


> Issue with remoting MAX_RETRIES
> -------------------------------
>
>                 Key: JBMESSAGING-851
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-851
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Ron Sigal
>             Fix For: 1.2.1, 1.0.1.SP5
>
>
> Currently remoting socket/bisocket transport MAX_RETRIES attribute is non configurable via the xml remoting config.
> This means if a client is making a lot of concurrent invocations and they take some significant time to execute then, the client invocations may timeout and throw an exception back to the client, since they have waited longer than 30 seconds (MAX_RETRIES * 1000 ms) to obtain a connection from the pool.
> This may be unacceptable to the client who is quite happy to wait an indefinite period (or at least a period longer than 30 seconds) to obtain a connection.
> MAX_RETRIES (currently hardcoded to 30) needs to be configurable via the xml config.
> Also the sleep interval (currently 1000 ms) needs to be made configurable too.
> See forum thread for a real world example of this problem.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira