[
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.
