[JBoss JIRA] Created: (JBMESSAGING-1860) Enhacement - Consumer should be able to read all the messages when another node in cluster lost connection to database
9:12 a.m.
Enhacement - Consumer should be able to read all the messages when another node in cluster
lost connection to database
----------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1860
URL: https://issues.jboss.org/browse/JBMESSAGING-1860
Project: JBoss Messaging
Issue Type: Enhancement
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP12, 1.4.8.GA
Reporter: Miroslav Novak
Assignee: Miroslav Novak
There should be made an enhancement in JBM clustering.
For now the behaviour is following:
Clustered queue is used and Session_Transacted mode is used.
1. cluster of 3 nodes - A - B - C
2. send 500 to each (db status - A:500, B:500, C:500)
3. disconnect B from DB (db unchanged)
4. read C - 1000 messages read (db status A:0, B:500, C:0) - hangs
5. read A - 0 messages read (db status A:0, B:500, C:0)
6. connect B to DB (db status A:0, B:417, C:83)
7. read B - 500 messages read (db status A:0, B:0, C:0)
In step 4. consumer received 1000 from 1500 messages from nodes A and C and there are
still 500 messages left in the db.
As an enhancement there should be that client on node C in step 4. will read all the
messages from clustered queue.
Thanks,
Mirek
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:30 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1860) Enhacement - Consumer should be able to read all the messages when another node in cluster lost connection to database
[
https://issues.jboss.org/browse/JBMESSAGING-1860?page=com.atlassian.jira....
]
Miroslav Novak commented on JBMESSAGING-1860:
---------------------------------------------
For more details please see: JBPAPP-6023
Enhacement - Consumer should be able to read all the messages when
another node in cluster lost connection to database
----------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1860
URL: https://issues.jboss.org/browse/JBMESSAGING-1860
Project: JBoss Messaging
Issue Type: Enhancement
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP12, 1.4.8.GA
Reporter: Miroslav Novak
Assignee: Miroslav Novak
There should be made an enhancement in JBM clustering.
For now the behaviour is following:
Clustered queue is used and Session_Transacted mode is used.
1. cluster of 3 nodes - A - B - C
2. send 500 to each (db status - A:500, B:500, C:500)
3. disconnect B from DB (db unchanged)
4. read C - 1000 messages read (db status A:0, B:500, C:0) - hangs
5. read A - 0 messages read (db status A:0, B:500, C:0)
6. connect B to DB (db status A:0, B:417, C:83)
7. read B - 500 messages read (db status A:0, B:0, C:0)
In step 4. consumer received 1000 from 1500 messages from nodes A and C and there are
still 500 messages left in the db.
As an enhancement there should be that client on node C in step 4. will read all the
messages from clustered queue.
Thanks,
Mirek
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:34 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBMESSAGING-1860) Enhacement - Consumer should be able to read all the messages when another node in cluster lost connection to database
[
https://issues.jboss.org/browse/JBMESSAGING-1860?page=com.atlassian.jira....
]
Miroslav Novak edited comment on JBMESSAGING-1860 at 4/27/11 10:33 AM:
-----------------------------------------------------------------------
For more details please see: JBPAPP-6023 and JBPAPP-6117
was (Author: mnovak):
For more details please see: JBPAPP-6023
Enhacement - Consumer should be able to read all the messages when
another node in cluster lost connection to database
----------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1860
URL: https://issues.jboss.org/browse/JBMESSAGING-1860
Project: JBoss Messaging
Issue Type: Enhancement
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP12, 1.4.8.GA
Reporter: Miroslav Novak
Assignee: Miroslav Novak
There should be made an enhancement in JBM clustering.
For now the behaviour is following:
Clustered queue is used and Session_Transacted mode is used.
1. cluster of 3 nodes - A - B - C
2. send 500 to each (db status - A:500, B:500, C:500)
3. disconnect B from DB (db unchanged)
4. read C - 1000 messages read (db status A:0, B:500, C:0) - hangs
5. read A - 0 messages read (db status A:0, B:500, C:0)
6. connect B to DB (db status A:0, B:417, C:83)
7. read B - 500 messages read (db status A:0, B:0, C:0)
In step 4. consumer received 1000 from 1500 messages from nodes A and C and there are
still 500 messages left in the db.
As an enhancement there should be that client on node C in step 4. will read all the
messages from clustered queue.
Thanks,
Mirek
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:38 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1860) Enhacement - Consumer should be able to read all the messages when another node in cluster lost connection to database
[
https://issues.jboss.org/browse/JBMESSAGING-1860?page=com.atlassian.jira....
]
Miroslav Novak updated JBMESSAGING-1860:
----------------------------------------
Description:
There should be made an enhancement in JBM clustering.
For now the behaviour is following:
Clustered queue is used and Session_Transacted mode is used.
1. cluster of 3 nodes - A - B - C
2. send 500 to each (db status - A:500, B:500, C:500)
3. disconnect B from DB (db unchanged)
4. read C - 1000 messages read (db status A:0, B:500, C:0) - hangs
5. read A - 0 messages read (db status A:0, B:500, C:0)
6. connect B to DB (db status A:0, B:417, C:83)
7. read B - 500 messages read (db status A:0, B:0, C:0)
In step 4. consumer received 1000 from 1500 messages from nodes A and C and there are
still 500 messages left in the db.
As an enhancement there should be that client on node C in step 4. will read all the
messages from clustered queue and client on node C doesn't hangs.
Thanks,
Mirek
was:
There should be made an enhancement in JBM clustering.
For now the behaviour is following:
Clustered queue is used and Session_Transacted mode is used.
1. cluster of 3 nodes - A - B - C
2. send 500 to each (db status - A:500, B:500, C:500)
3. disconnect B from DB (db unchanged)
4. read C - 1000 messages read (db status A:0, B:500, C:0) - hangs
5. read A - 0 messages read (db status A:0, B:500, C:0)
6. connect B to DB (db status A:0, B:417, C:83)
7. read B - 500 messages read (db status A:0, B:0, C:0)
In step 4. consumer received 1000 from 1500 messages from nodes A and C and there are
still 500 messages left in the db.
As an enhancement there should be that client on node C in step 4. will read all the
messages from clustered queue.
Thanks,
Mirek
Enhacement - Consumer should be able to read all the messages when
another node in cluster lost connection to database
----------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1860
URL: https://issues.jboss.org/browse/JBMESSAGING-1860
Project: JBoss Messaging
Issue Type: Enhancement
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP12, 1.4.8.GA
Reporter: Miroslav Novak
Assignee: Miroslav Novak
There should be made an enhancement in JBM clustering.
For now the behaviour is following:
Clustered queue is used and Session_Transacted mode is used.
1. cluster of 3 nodes - A - B - C
2. send 500 to each (db status - A:500, B:500, C:500)
3. disconnect B from DB (db unchanged)
4. read C - 1000 messages read (db status A:0, B:500, C:0) - hangs
5. read A - 0 messages read (db status A:0, B:500, C:0)
6. connect B to DB (db status A:0, B:417, C:83)
7. read B - 500 messages read (db status A:0, B:0, C:0)
In step 4. consumer received 1000 from 1500 messages from nodes A and C and there are
still 500 messages left in the db.
As an enhancement there should be that client on node C in step 4. will read all the
messages from clustered queue and client on node C doesn't hangs.
Thanks,
Mirek
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:27 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1860) Enhancement - Consumer should be able to read all the messages when another node in cluster lost connection to database
[
https://issues.jboss.org/browse/JBMESSAGING-1860?page=com.atlassian.jira....
]
Miroslav Novak updated JBMESSAGING-1860:
----------------------------------------
Summary: Enhancement - Consumer should be able to read all the messages when another
node in cluster lost connection to database (was: Enhacement - Consumer should be able to
read all the messages when another node in cluster lost connection to database)
Enhancement - Consumer should be able to read all the messages when
another node in cluster lost connection to database
-----------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1860
URL: https://issues.jboss.org/browse/JBMESSAGING-1860
Project: JBoss Messaging
Issue Type: Enhancement
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP12, 1.4.8.GA
Reporter: Miroslav Novak
Assignee: Miroslav Novak
There should be made an enhancement in JBM clustering.
For now the behaviour is following:
Clustered queue is used and Session_Transacted mode is used.
1. cluster of 3 nodes - A - B - C
2. send 500 to each (db status - A:500, B:500, C:500)
3. disconnect B from DB (db unchanged)
4. read C - 1000 messages read (db status A:0, B:500, C:0) - hangs
5. read A - 0 messages read (db status A:0, B:500, C:0)
6. connect B to DB (db status A:0, B:417, C:83)
7. read B - 500 messages read (db status A:0, B:0, C:0)
In step 4. consumer received 1000 from 1500 messages from nodes A and C and there are
still 500 messages left in the db.
As an enhancement there should be that client on node C in step 4. will read all the
messages from clustered queue and client on node C doesn't hangs.
Thanks,
Mirek
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:31 a.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-1860) Enhancement - Consumer should be able to read all the messages when another node in cluster lost connection to database
[
https://issues.jboss.org/browse/JBMESSAGING-1860?page=com.atlassian.jira....
]
Miroslav Novak reassigned JBMESSAGING-1860:
-------------------------------------------
Assignee: Yong Hao Gao (was: Miroslav Novak)
Hi Howard,
could you please look at this enhancement and implement new behaviour. This enhancement
will make our JBM cluster solution more HA.
Thank you,
Mirek
Enhancement - Consumer should be able to read all the messages when
another node in cluster lost connection to database
-----------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1860
URL: https://issues.jboss.org/browse/JBMESSAGING-1860
Project: JBoss Messaging
Issue Type: Enhancement
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP12, 1.4.8.GA
Reporter: Miroslav Novak
Assignee: Yong Hao Gao
There should be made an enhancement in JBM clustering.
For now the behaviour is following:
Clustered queue is used and Session_Transacted mode is used.
1. cluster of 3 nodes - A - B - C
2. send 500 to each (db status - A:500, B:500, C:500)
3. disconnect B from DB (db unchanged)
4. read C - 1000 messages read (db status A:0, B:500, C:0) - hangs
5. read A - 0 messages read (db status A:0, B:500, C:0)
6. connect B to DB (db status A:0, B:417, C:83)
7. read B - 500 messages read (db status A:0, B:0, C:0)
In step 4. consumer received 1000 from 1500 messages from nodes A and C and there are
still 500 messages left in the db.
As an enhancement there should be that client on node C in step 4. will read all the
messages from clustered queue and client on node C doesn't hangs.
Thanks,
Mirek
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5586
days inactive
5586
days old
5 comments
1 participants
participants (1)
-
Miroslav Novak (JIRA)