Do a full CTS1.4 run to check for regressions.
----------------------------------------------
Key: JBAS-4754
URL: http://jira.jboss.com/jira/browse/JBAS-4754
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Other
Reporter: Dimitris Andreadis
Fix For: JBossAS-4.2.2.GA
Before releasing, we should perform a final CTS run.
--
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
[ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-375:
-------------------------------------
One thought here.
Would it be possible to have this functionality working across a cluster too?
I.e. all messages sent using a particular value of JMSXGroupid go to the same consumer on the cluster?
> Grouping of messages with JMSXGroupId
> -------------------------------------
>
> Key: JBMESSAGING-375
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375
> Project: JBoss Messaging
> Issue Type: Feature Request
> Reporter: Tim Fox
> Assigned To: Tim Fox
> Fix For: 2.0.0 Beta 1
>
> Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt, patch-JBMESSAGING-375.txt
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue.
> This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID
--
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
[ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=all ]
Jeff Mesnil updated JBMESSAGING-375:
------------------------------------
Attachment: patch-JBMESSAGING-375.txt
simpler patch: group ID binding is handled directly in RoundRobinDistributor
> Grouping of messages with JMSXGroupId
> -------------------------------------
>
> Key: JBMESSAGING-375
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375
> Project: JBoss Messaging
> Issue Type: Feature Request
> Reporter: Tim Fox
> Assigned To: Tim Fox
> Fix For: 2.0.0 Beta 1
>
> Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt, patch-JBMESSAGING-375.txt
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue.
> This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID
--
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
TECHREVIEW: Installation Guide - Chapter:'Getting Started'
-----------------------------------------------------------
Key: JBAS-4869
URL: http://jira.jboss.com/jira/browse/JBAS-4869
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Vinu S Renish
--
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
TECHREVIEW: Installation Guide - Chapter:'Test Your Installation'
------------------------------------------------------------------
Key: JBAS-4868
URL: http://jira.jboss.com/jira/browse/JBAS-4868
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Vinu S Renish
--
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
TECHREVIEW: Installation Guide - Graphical Installation
-------------------------------------------------------
Key: JBAS-4867
URL: http://jira.jboss.com/jira/browse/JBAS-4867
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Vinu S Renish
--
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
TECHREVIEW: Installation Guide - Zip Installation
-------------------------------------------------
Key: JBAS-4866
URL: http://jira.jboss.com/jira/browse/JBAS-4866
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Vinu S Renish
--
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
Validate the JBM clustered config
---------------------------------
Key: JBAS-4865
URL: http://jira.jboss.com/jira/browse/JBAS-4865
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Fix For: JBossAS-5.0.0.Beta3
This is just a link to a JBM task : JBMESSAGING-1093
I'm just double checking the clustered configuration is okay for jboss-messaging and doing some minor adjustments, and wanted a JIRA on the JBAS for the committs I'm doing.
--
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
Post office and message updates at failover need to be transactional
--------------------------------------------------------------------
Key: JBMESSAGING-1113
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1113
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Ovidiu Feodorov
At failover updates are made via the JDBCPersistenceManager (mergeQueues) and the post office.
If the failing over server is itself killed during this process, then the system can enter an inconsistent state.
Need to make sure all database updates are performed in a single transaction.
--
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