New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JMSRA ActivationSpec property endpointPoolResizeTimeout should allow zero value #103
Comments
@glassfishrobot Commented |
@glassfishrobot Commented
--- a/src/share/java/com/sun/messaging/jms/ra/ActivationSpec.java Tue Jun 21 13:46:22 2011 -0700
+++ b/src/share/java/com/sun/messaging/jms/ra/ActivationSpec.java Tue Jun 28 10:00:49 2011 +0100
@@ -717,9 +717,10 @@
setEndpointPoolResizeTimeout(int endpointPoolResizeTimeout)
{
_loggerIM.entering(_className, "setEndpointPoolResizeTimeout()", Integer.toString(endpointPoolResizeTimeout));
- if (endpointPoolResizeTimeout < 1) {
+ // MQ-103 Allow a value of 0, which means no timeout
+ if (endpointPoolResizeTimeout < 0) {
IllegalArgumentException iae = new IllegalArgumentException(_lgrMID_EXC+"setEndpointPoolResizeTimeout:"+
- "Value must be greater than 0:"+
+ "Value must not be negative:"+
"Invalid value="+endpointPoolResizeTimeout);
_loggerIM.warning(iae.getMessage());
_loggerIM.throwing(_className, "setEndpointPoolResizeTimeout()", iae);
}} |
@glassfishrobot Commented Mar 29, 2013 5:14:20 PM com.sun.messaging.jms.ra.ActivationSpec setEndpointPoolResizeTimeout |
@glassfishrobot Commented |
|
Hi @edbratt - could you please check - and if it was fixed - let's close this issue, if it wasn't fixed - let's unbind this from 5.0 milestone. |
This fix is needed as part of the solution to GLASSFISH-4629
Currently, com.sun.messaging.jms.ra.ActivationSpec.setEndpointPoolResizeTimeout(int endpointPoolResizeTimeout) will throw an IllegalArgumentException if a value of 0 is supplied, meaning "infinite timeout".
JMSRA does not use this value. The current behaviour is that endpoints do not timeout, so in fact a value of 0 corresponds to the current behaviour but is not allowed.
Affected Versions
[4.5]
The text was updated successfully, but these errors were encountered: