You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "goldi (JIRA)" <ji...@apache.org> on 2007/11/19 20:26:26 UTC
[jira] Created: (AMQ-1496) jms.prefetchPolicy in Resource-Adapter!
jms.prefetchPolicy in Resource-Adapter!
---------------------------------------
Key: AMQ-1496
URL: https://issues.apache.org/activemq/browse/AMQ-1496
Project: ActiveMQ
Issue Type: Bug
Reporter: goldi
Fix For: 5.0.0
Testing ActiveMQ integrated in JBoss I found that the following doesn't work anymore:
<config-property-value>failover://(tcp://192.168.8.101:65001)?jms.prefetchPolicy.all=1000</config-property-value>
I got the following exception:
2007-11-16 15:08:50,734 ERROR [org.apache.activemq.ra.ActiveMQEndpointWorker] Endpoint connection to JMS broker failed: Could not create Transport. Reason: java.lang.IllegalArgumentException: Invalid connect parameters: {jms.prefetchPolicy.all=1000}
2007-11-16 15:08:50,734 ERROR [org.apache.activemq.ra.ActiveMQEndpointWorker] Endpoint will try to reconnect to the JMS broker in 30 seconds
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1496) jms.prefetchPolicy in
Resource-Adapter!
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58679#action_58679 ]
Gary Tully commented on AMQ-1496:
---------------------------------
Is this for an inbound connection to an MDB? Please add some more detail.
For an inbound connection, the prefetch is the product of maxMessagesPerSessions and maxSessions
see:
http://activemq.apache.org/activation-spec-properties.html
> jms.prefetchPolicy in Resource-Adapter!
> ---------------------------------------
>
> Key: AMQ-1496
> URL: https://issues.apache.org/activemq/browse/AMQ-1496
> Project: ActiveMQ
> Issue Type: Bug
> Reporter: goldi
> Fix For: 5.0.0
>
>
> Testing ActiveMQ integrated in JBoss I found that the following doesn't work anymore:
> <config-property-value>failover://(tcp://192.168.8.101:65001)?jms.prefetchPolicy.all=1000</config-property-value>
> I got the following exception:
> 2007-11-16 15:08:50,734 ERROR [org.apache.activemq.ra.ActiveMQEndpointWorker] Endpoint connection to JMS broker failed: Could not create Transport. Reason: java.lang.IllegalArgumentException: Invalid connect parameters: {jms.prefetchPolicy.all=1000}
> 2007-11-16 15:08:50,734 ERROR [org.apache.activemq.ra.ActiveMQEndpointWorker] Endpoint will try to reconnect to the JMS broker in 30 seconds
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1496) jms.prefetchPolicy in Resource-Adapter!
Posted by "Dong Pak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dong Pak resolved AMQ-1496.
---------------------------
Resolution: Working as Designed
Thanks for the information. Changing the default settings of maxMessagesPerSessions and maxSessions worked.
> jms.prefetchPolicy in Resource-Adapter!
> ---------------------------------------
>
> Key: AMQ-1496
> URL: https://issues.apache.org/activemq/browse/AMQ-1496
> Project: ActiveMQ
> Issue Type: Bug
> Reporter: goldi
> Fix For: 5.0.0
>
>
> Testing ActiveMQ integrated in JBoss I found that the following doesn't work anymore:
> <config-property-value>failover://(tcp://192.168.8.101:65001)?jms.prefetchPolicy.all=1000</config-property-value>
> I got the following exception:
> 2007-11-16 15:08:50,734 ERROR [org.apache.activemq.ra.ActiveMQEndpointWorker] Endpoint connection to JMS broker failed: Could not create Transport. Reason: java.lang.IllegalArgumentException: Invalid connect parameters: {jms.prefetchPolicy.all=1000}
> 2007-11-16 15:08:50,734 ERROR [org.apache.activemq.ra.ActiveMQEndpointWorker] Endpoint will try to reconnect to the JMS broker in 30 seconds
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (AMQ-1496) jms.prefetchPolicy in Resource-Adapter!
Posted by "Dong Pak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dong Pak reopened AMQ-1496:
---------------------------
Unable to change the prefetch value associated with a queue.
Please take a look at this issue again.
The ActiveMQ web console shows the prefetch value as 100 instead of 1000 or any other value specified in the ra.xml or broker-config.xml in the ActiveMQ Resource Adapter. This is supposed to be fixed in 5.0.0, but appears in version 5.3.1.
> jms.prefetchPolicy in Resource-Adapter!
> ---------------------------------------
>
> Key: AMQ-1496
> URL: https://issues.apache.org/activemq/browse/AMQ-1496
> Project: ActiveMQ
> Issue Type: Bug
> Reporter: goldi
> Fix For: 5.0.0
>
>
> Testing ActiveMQ integrated in JBoss I found that the following doesn't work anymore:
> <config-property-value>failover://(tcp://192.168.8.101:65001)?jms.prefetchPolicy.all=1000</config-property-value>
> I got the following exception:
> 2007-11-16 15:08:50,734 ERROR [org.apache.activemq.ra.ActiveMQEndpointWorker] Endpoint connection to JMS broker failed: Could not create Transport. Reason: java.lang.IllegalArgumentException: Invalid connect parameters: {jms.prefetchPolicy.all=1000}
> 2007-11-16 15:08:50,734 ERROR [org.apache.activemq.ra.ActiveMQEndpointWorker] Endpoint will try to reconnect to the JMS broker in 30 seconds
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (AMQ-1496) jms.prefetchPolicy in Resource-Adapter!
Posted by "goldi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
goldi closed AMQ-1496.
----------------------
Resolution: Fixed
Not Fiexed!
> jms.prefetchPolicy in Resource-Adapter!
> ---------------------------------------
>
> Key: AMQ-1496
> URL: https://issues.apache.org/activemq/browse/AMQ-1496
> Project: ActiveMQ
> Issue Type: Bug
> Reporter: goldi
> Fix For: 5.0.0
>
>
> Testing ActiveMQ integrated in JBoss I found that the following doesn't work anymore:
> <config-property-value>failover://(tcp://192.168.8.101:65001)?jms.prefetchPolicy.all=1000</config-property-value>
> I got the following exception:
> 2007-11-16 15:08:50,734 ERROR [org.apache.activemq.ra.ActiveMQEndpointWorker] Endpoint connection to JMS broker failed: Could not create Transport. Reason: java.lang.IllegalArgumentException: Invalid connect parameters: {jms.prefetchPolicy.all=1000}
> 2007-11-16 15:08:50,734 ERROR [org.apache.activemq.ra.ActiveMQEndpointWorker] Endpoint will try to reconnect to the JMS broker in 30 seconds
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.