[JBoss JIRA] Created: (JBMESSAGING-851) Issue with remoting MAX_RETRIES
by Tim Fox (JIRA)
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.0.1.SP5, 1.2.1
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.
--
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
19 years, 2 months
[JBoss JIRA] Closed: (JBMESSAGING-266) Remove Routable
by Ovidiu Feodorov (JIRA)
[ http://jira.jboss.com/jira/browse/JBMESSAGING-266?page=all ]
Ovidiu Feodorov closed JBMESSAGING-266.
---------------------------------------
Fix Version/s: 1.2.0.GA
(was: 1.2.1)
Resolution: Done
Consolidating 1.2.0.GA
> Remove Routable
> ---------------
>
> Key: JBMESSAGING-266
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-266
> Project: JBoss Messaging
> Issue Type: Task
> Reporter: Tim Fox
> Assigned To: Tim Fox
> Priority: Critical
> Fix For: 1.2.0.GA
>
> Original Estimate: 4 days
> Remaining Estimate: 4 days
>
> Remove Routable interface.
> Have interface MessageReference which represents things that can be routed.
> Have interface Payload (TBD) which every MessageReference has, this contains data that is not necessarty for routing.
> We would then have a subclass of Payload called JMSPayload which contains all the jms stuff,not needed for routing.
> A jms message would extend Message Reference and contain fields such as delivery count.
> The jms message would contain a Payload interface and delegate for that for other attributes
--
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
19 years, 2 months
[JBoss JIRA] Reopened: (JBMESSAGING-266) Remove Routable
by Ovidiu Feodorov (JIRA)
[ http://jira.jboss.com/jira/browse/JBMESSAGING-266?page=all ]
Ovidiu Feodorov reopened JBMESSAGING-266:
-----------------------------------------
> Remove Routable
> ---------------
>
> Key: JBMESSAGING-266
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-266
> Project: JBoss Messaging
> Issue Type: Task
> Reporter: Tim Fox
> Assigned To: Tim Fox
> Priority: Critical
> Fix For: 1.2.0.GA
>
> Original Estimate: 4 days
> Remaining Estimate: 4 days
>
> Remove Routable interface.
> Have interface MessageReference which represents things that can be routed.
> Have interface Payload (TBD) which every MessageReference has, this contains data that is not necessarty for routing.
> We would then have a subclass of Payload called JMSPayload which contains all the jms stuff,not needed for routing.
> A jms message would extend Message Reference and contain fields such as delivery count.
> The jms message would contain a Payload interface and delegate for that for other attributes
--
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
19 years, 2 months