-
1. Re: Unable to consume more than 777,000 messages
ataylor Jul 29, 2009 5:45 AM (in response to jbmuser)I cant open the attachment, can you upload a tar archive
-
2. Re: Unable to consume more than 777,000 messages
jbmuser Jul 29, 2009 7:41 AM (in response to jbmuser)Hi Jeff,
I have attached all the java files in JIRA.
Thanks
Bijith -
3. Re: Unable to consume more than 777,000 messages
jbmuser Aug 3, 2009 1:13 AM (in response to jbmuser)Hi Andy,
Any update on this issue? I noticed that setting Client Window Size to 0 resolves this issue but that would cause receiveNoWait() API to return null most of the times.
Thanks
Bijith -
4. Re: Unable to consume more than 777,000 messages
ataylor Aug 3, 2009 3:48 AM (in response to jbmuser)Yeah, Ive managed to recreate it and there is a bug there.
One thing that exacerbates the issue is that you are acknowledging every message when you only need to ack 1.
from the spec:CLIENT_ACKNOWLEDGE - With this option, a client acknowledges a
message by calling the message's acknowledge method. Acknowledging a
consumed message automatically acknowledges the receipt of all messages
that have been delivered by its session.
If you change this then you should be able to consume all the messages. -
5. Re: Unable to consume more than 777,000 messages
jbmuser Aug 3, 2009 5:33 AM (in response to jbmuser)mm....Thanks Andy. It worked after changing the ACKs as you suggested.
Bijith -
6. Re: Unable to consume more than 777,000 messages
jbmuser Aug 3, 2009 6:22 AM (in response to jbmuser)If I want to process messages and acknowledge each message only if the processing succeeds, How would I do that in JBM? i.e I want to consume all messages but ACK only a few of them. I mean something like Java Message Queue's Message.acknowledgeThisMessage().
Thanks
Bijith -
7. Re: Unable to consume more than 777,000 messages
timfox Aug 3, 2009 6:24 AM (in response to jbmuser)There is no such method Message.acknowledgeThisMethod() on the JMS API.
JMS does not support the acknowledgement of specific messages. This is not specific to JBoss Messaging. -
8. Re: Unable to consume more than 777,000 messages
jbmuser Aug 3, 2009 8:50 AM (in response to jbmuser)mm.. it seems I need to think of an alternative solution. Anyways, thank you Andy and Tim. I appreciate your help.
Thanks
Bijith -
9. Re: Unable to consume more than 777,000 messages
timfox Aug 3, 2009 9:21 AM (in response to jbmuser)The JBM core api is more powerful than the JMS API in that if you call message.acknowledge() it will acknowledge all messages up to and including that one that have been delivered on the session.
This differs from the JMS message.acknowledge() which acknowledges *all* messages that have been delivered on that session up until the time when you call it.
There is a subtle but important difference there. -
10. Re: Unable to consume more than 777,000 messages
genman Aug 4, 2009 5:36 PM (in response to jbmuser)The solution I have used in the past is to create a new JMS session for every message I want to acknowledge separately.
-
11. Re: Unable to consume more than 777,000 messages
genman Aug 4, 2009 5:36 PM (in response to jbmuser)The solution I have used in the past is to create a new JMS session for every message I want to acknowledge separately.
-
12. Re: Unable to consume more than 777,000 messages
jbmuser Aug 4, 2009 11:54 PM (in response to jbmuser)Thanks genman, However, I don't think I can adopt this approach as I have millions of messages to consume.
Bijith -
13. Re: Unable to consume more than 777,000 messages
adridi Aug 6, 2009 11:47 AM (in response to jbmuser)Bijith,
I saw that Andy closed your Jira saying that fix was done.
I have the same problem like you - Is it working for you with trunk build?
Thought Andy will comment what he fixed but didnt see any explanation.
At my company we're thinking to use the JBoss core API instead of JMS - I see benefit on that but not sure how it will evolve in the future.
Thanks,
Abdel -
14. Re: Unable to consume more than 777,000 messages
adridi Aug 6, 2009 5:23 PM (in response to jbmuser)As I still see the problem, I cloned the jira; JBMESSAGING-1691 and added my test case as recommended by Tim.
The new Jira is: https://jira.jboss.org/jira/browse/JBMESSAGING-1704
Abdel