February 2008 - jboss-jira - Jboss List Archives

[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

[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] Closed: (JBMESSAGING-312) Refactor persistencemanager

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-312?page=all ] Tim Fox closed JBMESSAGING-312. ------------------------------- Fix Version/s: Unscheduled (was: 2.0.0 Beta) Resolution: Out of Date > Refactor persistencemanager > --------------------------- > > Key: JBMESSAGING-312 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-312 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: Unscheduled > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Refactor PersistenceManager to make less monolithic. > The PersistenceManager should really only deal with simple persistence operations, e..g. addReference, removeReference, addMessage, removeMessage etc. This makes it easy to re-implement for another type of store. > Currently the PM contains logic that belongs elsewhere e.g. in the ChannelState. > The TransactionCallback should be removed to it's own java file. > The locking operations should occur in the caller. > There should be an abstraction PMTxContext which can be passed into PM operations to group them. > This should dramatically clarify and simplify things -- 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
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-158) Tidy up tests

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-158?page=all ] Tim Fox closed JBMESSAGING-158. ------------------------------- Fix Version/s: Unscheduled (was: 2.0.0 Beta) Resolution: Out of Date > Tidy up tests > ------------- > > Key: JBMESSAGING-158 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-158 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Affects Versions: 1.0.0 alpha PR3 > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > Original Estimate: 2 days, 4 hours > Remaining Estimate: 2 days, 4 hours > > Tidy up tests: > - Some test classes (and notably MessageConsumerTest) do a lot of Connection/Session/Consumer/Producer creation in setUp(). The original idea was to separate as much boilerplate code as possible, but this leads to hard to understand tests and may lead to unexpected behavior, since the test my get "hidden" intialization it doesn't want. Refactor them and re-write each test to be as independent as possible. > - For tests that send messages in a loop, use a centrally-configured loop counter, which can be easily globally modified. Stress test are more likely to exhibit edge cases and race conditions as the number of message increases, and it should be easy to control that number globally. > Example > public class Global > { > public static final int GENERAL_COUNTER = 100; > .... > } > public class MyTest extends MessagingTestCase > { > // override if it doesn't makes sense locally > protected int NUM_MESSAGES = Global.GENERAL_COUNTER; > ... > } > > - Some tests are not in the right file. > When refactor tests, take extra care not to break their semantics, though. -- 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
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-259) Activate compression in marshaller

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-259?page=all ] Tim Fox closed JBMESSAGING-259. ------------------------------- Fix Version/s: Unscheduled (was: 2.0.0 Beta) Resolution: Out of Date > Activate compression in marshaller > ---------------------------------- > > Key: JBMESSAGING-259 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-259 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Minor > Fix For: Unscheduled > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Activate compression in marshaller for messages > x bytes. Make it configurable -- 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
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-225) Explore integrating Adrian's Microcontainer with the Messaging testing environment

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-225?page=all ] Tim Fox closed JBMESSAGING-225. ------------------------------- Fix Version/s: Unscheduled (was: 2.0.0 Beta) Resolution: Out of Date > Explore integrating Adrian's Microcontainer with the Messaging testing environment > ---------------------------------------------------------------------------------- > > Key: JBMESSAGING-225 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-225 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > -- 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
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-186) Check that all TODOs and FIXMEs correspond to known JIRA tasks

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-186?page=all ] Tim Fox closed JBMESSAGING-186. ------------------------------- Fix Version/s: Unscheduled (was: 2.0.0 Beta) Resolution: Out of Date > Check that all TODOs and FIXMEs correspond to known JIRA tasks > -------------------------------------------------------------- > > Key: JBMESSAGING-186 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-186 > Project: JBoss Messaging > Issue Type: Task > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Priority: Minor > Fix For: Unscheduled > > > .. and if not, create appropriate JIRA tasks. -- 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
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-306) Supports recovery flag

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-306?page=all ] Tim Fox closed JBMESSAGING-306. ------------------------------- Fix Version/s: Unscheduled (was: 2.0.0 Beta) Resolution: Out of Date > Supports recovery flag > ---------------------- > > Key: JBMESSAGING-306 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-306 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Minor > Fix For: Unscheduled > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Should have flag "supports XA recovery" on persistencemanager. > If = false then only tx id, not all xid fields are persisted on prepare. This should improve performance when xa recovery is not required. -- 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
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-26) Standalone Messaging configuration.

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-26?page=all ] Tim Fox closed JBMESSAGING-26. ------------------------------ Fix Version/s: Unscheduled (was: 2.0.0 Beta) Resolution: Out of Date > Standalone Messaging configuration. > ----------------------------------- > > Key: JBMESSAGING-26 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-26 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Fix For: Unscheduled > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Prepare a stripped-down JBoss configuration that will be the "stand-alone" JBoss Messaging server. > Must have at least the JNDI server, Logging, Remoting and AOP support. > We should provide a pre-packaged downloadable "standalone" config - users don't want to have to download and install the AS just so they can create a standalone installation. -- 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
0
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 February 2008