[esb-issues] [JBoss JIRA] (JBESB-3739) Detect CLIENT_ACKNOWLEDGE mode using jms-provider on non-gateway queues
[
https://issues.jboss.org/browse/JBESB-3739?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3739:
------------------------------------------------
David Le Sage <dlesage(a)redhat.com> made a comment on [bug
781980|https://bugzilla.redhat.com/show_bug.cgi?id=781980]
Technical note updated. If any revisions are required, please edit the "Technical
Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services
team.
Diffed Contents:
@@ -1 +1 @@
-When using jms-provider, CLIENT_ACKNOWLEDGE mode is not accepted as a valid non-gateway
listener. Although the message is retrieved by the JmsCourier and converted into an ESB
message, the reference to the underlying JMS message is removed. Because of this, the
message remains in the non-gateway queue after ESB service has been invoked.+When using
jms-provider, CLIENT_ACKNOWLEDGE mode was not accepted as a valid non-gateway listener.
Although the message was retrieved by the JmsCourier and converted into an ESB message,
the reference to the underlying JMS message was removed. Because of this, the message
remained in the non-gateway queue after ESB service has been invoked.
Detect CLIENT_ACKNOWLEDGE mode using jms-provider on non-gateway
queues
-----------------------------------------------------------------------
Key: JBESB-3739
URL: https://issues.jboss.org/browse/JBESB-3739
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Message Store
Affects Versions: 4.11
Reporter: Tom Cunningham
Fix For: 4.11 CP1
Description of problem:
CLIENT_ACKNOWLEDGE mode is not valid for a non-gateway listener using
jms-provider.
If using the jms-provider then the message will be retrieved by the
JmsCourier and converted into an ESB message, after which there is no
longer a reference to the underlying JMS message. The JmsCourier should
be detecting this and raising an exception.
Version-Release number of selected component (if applicable):
JBoss ESB 4.10
How reproducible:
Consistently
Steps to Reproduce:
1. Modfiy jboss-esb.xml of helloworld quickstart:
<jms-provider name="JBossMQ"
connection-factory="XAConnectionFactory">
<jms-bus busid="quickstartGwChannel">
<jms-message-filter
dest-type="QUEUE"
dest-name="queue/quickstart_helloworld_Request_gw"
transacted="false"
acknowledge-mode="CLIENT_ACKNOWLEDGE"
/>
</jms-bus>
<jms-bus busid="quickstartEsbChannel">
<jms-message-filter
dest-type="QUEUE"
dest-name="queue/quickstart_helloworld_Request_esb"
transacted="false"
acknowledge-mode="CLIENT_ACKNOWLEDGE"
/>
</jms-bus>
</jms-provider>
2. Invoke ant runtest
Actual results:
Message remains in the non-gateway queue after ESB service has been invoked.
Expected results:
An exception should be raised indicating that CLIENT_ACKNOWLEDGE mode is not
supported on non-gateway queues using jms-listener.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira