November 2007 - jboss-jira - Jboss List Archives

[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

16 years, 10 months

2
7
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

16 years, 10 months

4
9
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

16 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-576) Separate paging and persistence functionality

by Tim Fox (JIRA)

Separate paging and persistence functionality --------------------------------------------- Key: JBMESSAGING-576 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-576 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.Alpha1, 1.0.1.CR5 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Reference management gets complex when we have to take into account messages and refs paged and not paged to storage especially if the database is shared, this means we end up having to do extra queries to work out if the ref is alredy in the database etc. We should separate the paging functionality out, so it doesn't page to the normal persistent store, but to a separate paging store which typically would be a local file based store using HOWL or some other fast logger. -- 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

16 years, 10 months

3
5
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

16 years, 10 months

3
7
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

16 years, 10 months

3
11
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1102) JBM should use TransactionManagerLocator instead of the MBean API as that is being removed from JBAS code

by Clebert Suconic (JIRA)

JBM should use TransactionManagerLocator instead of the MBean API as that is being removed from JBAS code --------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1102 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1102 Project: JBoss Messaging Issue Type: Feature Request Affects Versions: 1.4.0.GA Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.4.0.SP1, AS 5.0 Integration, EAP 4.3 Integration -- 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

16 years, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1128) Message not routed from one node to node with only consumer.

by Mike Clark (JIRA)

Message not routed from one node to node with only consumer. ------------------------------------------------------------ Key: JBMESSAGING-1128 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1128 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.4.0.GA Environment: Sun JDK 1.5.0_12, JBoss EAP 4.2.0, JBoss Messaging 1.4.GA installed against the "all" configuration running on RHEL5 (CSB), MySQL 5 used as backing database. Reporter: Mike Clark Assigned To: Tim Fox In trying to reproduce behavior described in case 18885, I can reproduce the following: Start two instances of JBoss (ports-01 and ports-02 using the usual binding manager approach). Deployed a simple MDB to ports-02; simply logs messages with INFO priority. Deployed a simple MBean to both ports-01 and ports-02 that allows me to send TextMessage messages to the respective boxes from the JMX console. Messages sent to ports-02 are consumed by the MDB as expected. Messages sent to ports-01 are not consumed unless ports-02 is shutdown (normal shutdown) and restarted. The MDB on ports-02 will consume the messages queued to ports-01 regardless of whether ports-01 is up or not (ports-01 shutdown cleanly). Messages sent to ports-01 are, of course, seen in the database as soon as they are submitted (I'm using PERSISTENT delivery mode.) Both instances were created from a clean "all" instance. -- 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

16 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1094) Integrate JSR-77

by Clebert Suconic (JIRA)

Integrate JSR-77 ---------------- Key: JBMESSAGING-1094 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1094 Project: JBoss Messaging Issue Type: Task Reporter: Clebert Suconic Assigned To: Tim Fox Fix For: AS 5.0 Integration, EAP 4.3 Integration -- 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

16 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1099) Potential deadlock in shutting down server

by Tim Fox (JIRA)

Potential deadlock in shutting down server ------------------------------------------ Key: JBMESSAGING-1099 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.GA Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.SP1 Need to investigate -- 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

16 years, 10 months

3
22
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2007