[esb-issues] [JBoss JIRA] Created: (JBESB-1563) Extends jms-jca-provider to support activation-config properties
Extends jms-jca-provider to support activation-config properties
----------------------------------------------------------------
Key: JBESB-1563
URL: http://jira.jboss.com/jira/browse/JBESB-1563
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Documentation, Examples, Transports
Affects Versions: 4.2.1 CP1
Reporter: Daniel Bevenius
Fix For: 4.3
We would like to be able to specify activation-config properties for the jms-jca-provider.
This would give us a jms redelivery functionality by simple configuration.
The reason for this extension is that we have listeners that are not gateways, but still
need to be able to set properties like dLQMaxResent.
This is the suggestion:
<jms-jca-provider
name="JBossMessaging"
....
<jms-bus
busid="quickstartGwChannel">
....
</jms-bus>
<activation-config>
<property name="dLQMaxResent" value="12"/>
<property name="dLQJNDIName"
value="/queue/quickstart_jms_transacted_error"/>
<property name="reconnectInterval"
value="1000"/>
</activation-config>
</jms-jca-provider>
This requires an update to the jbossesb-1.0.1.xsd and modifying JmsListenerMapper.
The gain here is that we can then specify the number of times that we should try to
redeliver a message. One can also specify an interval so that the message is not
redelivered straight away.
I noticed that jca seems to have the dLQMaxResent but the JMS queue definitions also have
their own.
If one has set dLQMaxResent to a value larger then the JMS queues MaxDeliveryAttempts
value, then the JMS queues value will kickin. But by simply increasing MaxDeliveryAttempts
to larger value then dLQMaxResent everything works.
I've verified this by modifying the jms_transacted quickstart and trying it out.
--
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