-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/6277/
-----------------------------------------------------------
(Updated Nov. 15, 2012, 9:08 a.m.)
Review request for bookkeeper.
Changes
-------
Updating based on mmorel's comments.
I have also added diff's to hedwig-server to allow for unit tests for jms to
depend on HedwigHubTestBase in server.
For some reason, currently the jms tests are only working in standalone mode
from the testsuite - not sure what the problem is, but since it is orthogonal
to the patch (running them without testsuite integration directly against
hedwig works fine), I am not investigating the issue - it is better handled by
hedwig server developers !
Also note that since some of the client changes were removed based on Sijie
Guo's review comments, quite a few activemq testcases will fail.
I have verified that this is due to reverting the earlier changes (I have
uploaded the require minimal subset diffs in case it is required to add them
too).
Description
-------
Add support for JMS provider conforming to 1.1 as detailed in BOOKKEEPER-312.
The limitations are (as detailed in the bug) :
0) Due to lack of proper support for consume in face of disconnect, some tests
fail - this has to be addressed in hedwig independent of this bug.
1) Need better ways to connect to server - currently it is (sort of) hardcoded
via property file(s).
Also, need better ways to authorize to server (assuming hedwig supports this).
A subsequent bug can extend/enhance the provider to add support for this (JAAS
or whatever is expected to be supported).
2) No support for Queue's.
3) No support for noLocal : simulating it in provider.
4) We do not support NON_PERSISTENT delivery mode.
5) Calling unsubscribe on a durable subscription will fail if it was NOT
created in the current session.
6) Explicit session recovery is not supported.
and so setting the JMSRedelivered flag is simulated (best case effort).
7) Hedwig only supports marking all messages until seq-id as received : while
JMS indicates ability to acknowledge individual messages.
This distinction is currently unsupported.
8) JMS spec requires
"A connection's delivery of incoming messages can be temporarily stopped
using its stop() method. It can be restarted using its start() method. When the
connection is stopped, delivery to all the connection’s MessageConsumers is
inhibited: synchronous receives block, and messages are not delivered to
MessageListeners."
We honor this for undelivered messages from server - but if stop is called
while there are pending messages yet to be delivered to a listener (or buffered
in subscriber for receive), then they will be delivered irrespective of stop().
This addresses bug BOOKKEEPER-312.
https://issues.apache.org/jira/browse/BOOKKEEPER-312
Diffs (updated)
-----
hedwig-server/pom.xml f54b281
hedwig-server/src/test/java/org/apache/hedwig/server/HedwigHubTestBase.java
523ecdc
Diff: https://reviews.apache.org/r/6277/diff/
Testing
-------
Thanks,
Mridul
