April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBMESSAGING-10) Training Material

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-10?page=all ] Tim Fox closed JBMESSAGING-10. ------------------------------ Resolution: Won't Fix > Training Material > ----------------- > > Key: JBMESSAGING-10 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-10 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Documentation and Training > Reporter: Ivelin Ivanov > 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

19 years, 2 months

1
0
0 / 0

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

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-306?page=all ] Tim Fox updated JBMESSAGING-306: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > 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 > Fix For: 2.0.0 Beta 1 > > 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-343) Stress test with a large number of clients accessing the server in parallel

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-343?page=all ] Tim Fox updated JBMESSAGING-343: -------------------------------- Fix Version/s: 1.2.1.CR1 (was: Unscheduled) > Stress test with a large number of clients accessing the server in parallel > --------------------------------------------------------------------------- > > Key: JBMESSAGING-343 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-343 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Fix For: 1.2.1.CR1 > > > Push the limit of concurent clients to limit -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-340) Static selector queues

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-340?page=all ] Tim Fox updated JBMESSAGING-340: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > Static selector queues > ---------------------- > > Key: JBMESSAGING-340 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-340 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 2.0.0 Beta 1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > We should consider adding functionality to allow a selector to be associated with a queue in the deployment descriptor. The queue then does not accept any messages that do not match the selector. This is in addition to the standard jms functionality of specifying selectors on message consumers. > It should give better performance in those cases where it is possible to know a selector to apply to an entire queue in advance. -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-446) Start the QA process in concert with QA team

by Ovidiu Feodorov (JIRA)

Start the QA process in concert with QA team -------------------------------------------- Key: JBMESSAGING-446 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-446 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov 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

19 years, 2 months

3
5
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-379) Split large messages into fragments

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-379?page=all ] Tim Fox updated JBMESSAGING-379: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > Split large messages into fragments > ----------------------------------- > > Key: JBMESSAGING-379 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-379 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 2.0.0 Beta 1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > An alternative way of dealing with very large messages than using a streamed body, is to automatically split large messages into many small fragments and send each in it's own message. These can be automatically re-assembled at the receiver. -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-829) Split bridge test into multiple tests to prevent timeouts

by Tim Fox (JIRA)

Split bridge test into multiple tests to prevent timeouts --------------------------------------------------------- Key: JBMESSAGING-829 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-829 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.Beta2 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 The bridge test can take up to an hour to run, depending on hardware and database used. This means junit timeout has to be increased to a large value to prevent timeouts. Instead we should split the bridge test into smaller tests to prevent us having to have such a high timeout value. -- 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

19 years, 2 months

2
2
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-265) Soak tests

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-265?page=all ] Tim Fox updated JBMESSAGING-265: -------------------------------- Fix Version/s: 1.2.1.CR1 (was: Unscheduled) > Soak tests > ---------- > > Key: JBMESSAGING-265 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-265 > Project: JBoss Messaging > Issue Type: Task > Reporter: Ovidiu Feodorov > Fix For: 1.2.1.CR1 > > > A test that runs long enough and sends a significant number of messages into the server; used to detect memory leaks and failure under load -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-324) Set JMSRedelivered on recovery

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-324?page=all ] Tim Fox updated JBMESSAGING-324: -------------------------------- Fix Version/s: 1.2.1.CR1 (was: Unscheduled) > Set JMSRedelivered on recovery > ------------------------------ > > Key: JBMESSAGING-324 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-324 > Project: JBoss Messaging > Issue Type: Bug > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1.CR1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > After recovery or server restart messages aren't being delivered with JMSRedlivered=true -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-177) Server-side message persistence/caching should be done by an AOP interceptor

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-177?page=all ] Tim Fox closed JBMESSAGING-177. ------------------------------- Resolution: Won't Fix > Server-side message persistence/caching should be done by an AOP interceptor > ---------------------------------------------------------------------------- > > Key: JBMESSAGING-177 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-177 > Project: JBoss Messaging > Issue Type: Task > Components: AOP Support > Reporter: Ovidiu Feodorov > 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

19 years, 2 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 April 2007