January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-989) Core refactoring

by Tim Fox (JIRA)

Core refactoring ---------------- Key: JBMESSAGING-989 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-989 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta 1 Core refactoring- The old core classes are in dire need of reviewing and refactoring. The hierarchy of channel classes should be collapsed for simplicity, since there is only one real implementation of a channel. And the router class should be re-examined - do we need iterator etc Do we need iterator on the channel? All classes should be made cluster aware (including router). We can simplify things a *lot*! -- 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

18 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-751) Check and test failover behaviour when delegate methods are executing

by Tim Fox (JIRA)

Check and test failover behaviour when delegate methods are executing --------------------------------------------------------------------- Key: JBMESSAGING-751 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-751 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Fix For: 1.2.0.CR1 Currently failover will kick in if a connection error is detected during the invocation of any XXXDelegate method which makes a remote call, although only some of these are tested. We need to a) Make sure failure of all methods that make a remote call should be tested, e.g. connection start/stop, connection.sendTransaction, session.commit/rollback, cancel, cancelDeliveries etc b) We need to analyse whether *all* these method invocations need to be retried on the new server after failover is complete. It may be the case that only some should be retried -- 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

18 years, 5 months

4
9
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-868) Ordering issue when mixing unicast and multicast

by Tim Fox (JIRA)

Ordering issue when mixing unicast and multicast ------------------------------------------------ Key: JBMESSAGING-868 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-868 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.CR1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 When routing a set of messages to nodes in a cluster, if some are routed using unicast and others using multicast (as an optimisation), then earlier messages can "overtake" later sent messages, so they are received in the wrong order on the recipient. This caused DefaultClusteredPostOfficeTest::testClusteredNonPersistentRouteWithFilterRecoverable to fail because messages were received out of order -- 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

18 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-815) Extra message created if server fails when send and ACK are synchronized

by Clebert Suconic (JIRA)

Extra message created if server fails when send and ACK are synchronized ------------------------------------------------------------------------ Key: JBMESSAGING-815 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-815 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.SP3 Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.2.0.CR1 -- 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

18 years, 5 months

4
15
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-839) Recover deliveries does not deal with paged references

by Tim Fox (JIRA)

Recover deliveries does not deal with paged references ------------------------------------------------------ Key: JBMESSAGING-839 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-839 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox Priority: Minor Fix For: 1.2.0.GA When recovering deliveries ChannelSupport::recoverDeliveries after failover then there is a small possibility that the deliveries are not in memory but paged in storage - we should cater for this situation. -- 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

18 years, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-872) Convert destinations to ints

by Tim Fox (JIRA)

Convert destinations to ints ---------------------------- Key: JBMESSAGING-872 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-872 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Ovidiu Feodorov Destination implementations JBossQueue and JBossTopic are currently not much more than just Strings identifiers. When sending a message the destination (and possibly the replyto) need to be serialized with the message. If the Destinations are just identifiers then they could represented as ints making there less bytes to serialize. This could be significant for destinations with long names, e.g. 100 bytes -> 4 bytes (per message) -- 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

18 years, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-873) Down cache optimisation

by Tim Fox (JIRA)

Down cache optimisation ----------------------- Key: JBMESSAGING-873 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-873 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 If there are no persistent messages in storage then when paging we can avoid flushing the downCache and loading from the db and just transfer from the downcache to the in memory list when loading -- 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

18 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-676) Unreliable link scenario

by Ovidiu Feodorov (JIRA)

Unreliable link scenario ------------------------ Key: JBMESSAGING-676 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-676 Project: JBoss Messaging Issue Type: Feature Request Reporter: Ovidiu Feodorov Fix For: 1.2.0.Beta2 -- 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

18 years, 5 months

3
11
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-608) Add a new compatibity and stress test layer based on JMS CTS

by Ovidiu Feodorov (JIRA)

Add a new compatibity and stress test layer based on JMS CTS ------------------------------------------------------------ Key: JBMESSAGING-608 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-608 Project: JBoss Messaging Issue Type: Task Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.1 http://jmscts.sourceforge.net/index.html The stress part is especially interesting. -- 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

18 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-543) Use a file based transaction logger instead of logging in the database

by Tim Fox (JIRA)

Use a file based transaction logger instead of logging in the database ---------------------------------------------------------------------- Key: JBMESSAGING-543 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-543 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Currently we are logging prepared state transactions in the database. Instead, we should utilise a tried and tested transaction logger for performance reasons. We should evaluate both JBoss TS objectstore, and HOWL to take this role -- 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

18 years, 5 months

3
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008