[
http://jira.jboss.com/jira/browse/JBAS-5670?page=all ]
Kevin Lohmann updated JBAS-5670:
--------------------------------
Description:
Hi *,
here's the situation:
We have JBossAS 4.2.2 with no changes. We're using the example queue 'A' (test
with a new queue was not successfull) and transacted sessions.
Every MessageConsumer and MessageProducer share the same Connection-object (changing this
didn't help) and have their own Session-object.
We use MessageConsumers with a MessageSelector and have to change the selector after a
while. So that means closing the old consumer and create an new consumer with a new
selector.
First we sent 10.000 messages through a MessageProducer and _after_ the messages have
arrived we started two consumers (and changed the selector again and again). Everything
works fine: The programm ends, all messages sent are recieved.
But then the MessageProducer runs parallel as a seperate thread.
What happens?
The programm doesn't quite (because not all messages are recieved) and the jmx-console
shows that a few messages are stuck in the "InProcess"-list. When you now close
the programm the messages return to the queue.
We tried that with not using selectors and everything worked fine. But we need to use
selectors.
I attached the test-programm.
was:
Hi *,
here's the situation:
We have JBossAS 4.2.2 with no changes. We're using the example queue 'A' (test
with a new queue was not successfull) and transacted sessions.
Every MessageConsumer and MessageProducer share the same Connection-object (changing this
didn't help) and have their own Session-object.
We use MessageConsumers with a MessageSelector and have to change the selector after a
while. So that means closing the old consumer and create an new consumer with a new
selector.
First we sent 10.000 messages through a MessageProducer and _after_ the messages have
arrived we started two consumers (and changed the selector again and again). Everything
works fine: The programm ends, all messages sent are recieved.
But then the MessageProducer runs parallel as a seperate thread.
What happens?
The programm doesn't quite (because not all messages are recieved) and the jmx-console
shows that a few messages are stuck in the "InProcess"-list. When you now close
the programm the messages return to the queue.
We tried that with not using selectors and everything worked fine. But we need to use
selectors.
I tried to attach the test-programm but i couldn't find where do to it.
Using MessageConsumers with Message Selector make messages stuck in
queue
-------------------------------------------------------------------------
Key: JBAS-5670
URL:
http://jira.jboss.com/jira/browse/JBAS-5670
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (JBossMQ)
Affects Versions: JBossAS-4.2.2.GA
Environment: Java 5.0, WinXP
Reporter: Kevin Lohmann
Assigned To: Adrian Brock
Attachments: Situation.zip
Hi *,
here's the situation:
We have JBossAS 4.2.2 with no changes. We're using the example queue 'A'
(test with a new queue was not successfull) and transacted sessions.
Every MessageConsumer and MessageProducer share the same Connection-object (changing this
didn't help) and have their own Session-object.
We use MessageConsumers with a MessageSelector and have to change the selector after a
while. So that means closing the old consumer and create an new consumer with a new
selector.
First we sent 10.000 messages through a MessageProducer and _after_ the messages have
arrived we started two consumers (and changed the selector again and again). Everything
works fine: The programm ends, all messages sent are recieved.
But then the MessageProducer runs parallel as a seperate thread.
What happens?
The programm doesn't quite (because not all messages are recieved) and the
jmx-console shows that a few messages are stuck in the "InProcess"-list. When
you now close the programm the messages return to the queue.
We tried that with not using selectors and everything worked fine. But we need to use
selectors.
I attached the test-programm.
--
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