March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-288) Add POJO messaging examples

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-288?page=all ] Ovidiu Feodorov updated JBMESSAGING-288: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Add POJO messaging examples > --------------------------- > > Key: JBMESSAGING-288 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-288 > Project: JBoss Messaging > Issue Type: Task > Components: Documentation and Training > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Blocker > Fix For: Unscheduled > > > Add an example that shows how to write and run a POJO MDB to docs/examples and ship it with the distribution. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-348) Automate test run against all supported databases

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-348?page=all ] Ovidiu Feodorov updated JBMESSAGING-348: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Automate test run against all supported databases > ------------------------------------------------- > > Key: JBMESSAGING-348 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-348 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Fix For: Unscheduled > > > The test suite should be run continuously against all databases we supply a configuration for. > Initially this should be: > Oracle, MSSQL, MySQL, PostgreSQL, DB2, Sybase and Derby. -- 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, 1 month

1
0
0 / 0

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

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-343?page=all ] Ovidiu Feodorov updated JBMESSAGING-343: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > 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: Unscheduled > > > 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-388) Write a JBossMQ to Messaging migration guide

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-388?page=all ] Ovidiu Feodorov updated JBMESSAGING-388: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Write a JBossMQ to Messaging migration guide > -------------------------------------------- > > Key: JBMESSAGING-388 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-388 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Documentation and Training > Reporter: Ovidiu Feodorov > Assigned To: 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-16) A PointToMultipoint should be able to do delivery on separate threads

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-16?page=all ] Ovidiu Feodorov updated JBMESSAGING-16: --------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > A PointToMultipoint should be able to do delivery on separate threads > --------------------------------------------------------------------- > > Key: JBMESSAGING-16 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-16 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Messaging Core > Affects Versions: 1.2.0.Alpha1 > Reporter: Ovidiu Feodorov > Assigned To: 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-314) Ensure Messaging core has no dependencies on the JMS facade

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-314?page=all ] Ovidiu Feodorov updated JBMESSAGING-314: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Ensure Messaging core has no dependencies on the JMS facade > ----------------------------------------------------------- > > Key: JBMESSAGING-314 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-314 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Fix For: Unscheduled > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Messaging core still has some dependencies on the jms facade. These should be factored out. -- 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, 1 month

1
0
0 / 0

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

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-158?page=all ] Ovidiu Feodorov updated JBMESSAGING-158: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > 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

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-126) Possible enhanced message expiry processing

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-126?page=all ] Ovidiu Feodorov updated JBMESSAGING-126: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Possible enhanced message expiry processing > ------------------------------------------- > > Key: JBMESSAGING-126 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-126 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Messaging Core > Reporter: Ovidiu Feodorov > Fix For: Unscheduled > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Process depending on conclusion on the forum. -- 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, 1 month

1
0
0 / 0

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

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-306?page=all ] Ovidiu Feodorov updated JBMESSAGING-306: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > 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: 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

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-329) Inconsistency in return values

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-329?page=all ] Ovidiu Feodorov updated JBMESSAGING-329: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Inconsistency in return values > ------------------------------ > > Key: JBMESSAGING-329 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-329 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: Unscheduled > > Original Estimate: 1 day, 4 hours > Remaining Estimate: 1 day, 4 hours > > Some methods return false to represent failure, others throw an exception - need to be consistent. -- 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, 1 month

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 March 2007