April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-321) Use lock free queues for JDK1.5

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-321?page=all ] Tim Fox updated JBMESSAGING-321: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > Use lock free queues for JDK1.5 > ------------------------------- > > Key: JBMESSAGING-321 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-321 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Messaging Core > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Optional > Fix For: 2.0.0 Beta 1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > JDK1.5 concurrent classes utilise processor Compare and Swap (CAS) instructions to allow wait free (lock free) data struictures to be created. > We could detect whether the user is running JDK1.5 and use non blocking synchronization in our queues. Should improve concurrency. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-196) Port JBossMQ XIL2 support to Messaging

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-196?page=all ] Tim Fox closed JBMESSAGING-196. ------------------------------- Resolution: Won't Fix > Port JBossMQ XIL2 support to Messaging > -------------------------------------- > > Key: JBMESSAGING-196 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-196 > Project: JBoss Messaging > Issue Type: Task > Components: JMS Remoting > Reporter: John Fawcett > Priority: Optional > 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-244) Enable quotas for users

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-244?page=all ] Tim Fox updated JBMESSAGING-244: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > Enable quotas for users > ----------------------- > > Key: JBMESSAGING-244 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-244 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Priority: Optional > Fix For: 2.0.0 Beta 1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Investigate whether we need to provide quotas functionality for users. I.e. limit number of messages able to send per sec etc. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-438) Allow ports used by JBossMessaging to be mapped using ServiceBindingManager

by Tim Fox (JIRA)

Allow ports used by JBossMessaging to be mapped using ServiceBindingManager --------------------------------------------------------------------------- Key: JBMESSAGING-438 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-438 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Fix For: 1.0.1.GA -- 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, 3 months

4
12
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-211) Destination programmatic deployment example/integration test

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-211?page=all ] Tim Fox updated JBMESSAGING-211: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > Destination programmatic deployment example/integration test > ------------------------------------------------------------ > > Key: JBMESSAGING-211 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-211 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Priority: Optional > Fix For: 2.0.0 Beta 1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Write the corresponing docs/example/programmatic-deployment integration test. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-378) Use memory leak detection within the testsuite

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-378?page=all ] Tim Fox updated JBMESSAGING-378: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > Use memory leak detection within the testsuite > ---------------------------------------------- > > Key: JBMESSAGING-378 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-378 > Project: JBoss Messaging > Issue Type: Task > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: 2.0.0 Beta 1 > > Original Estimate: 2 minutes > Remaining Estimate: 2 minutes > > Clebert's stuff. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-301) Use Hermes in top of Messaging

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-301?page=all ] Tim Fox updated JBMESSAGING-301: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > Use Hermes in top of Messaging > ------------------------------ > > Key: JBMESSAGING-301 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-301 > Project: JBoss Messaging > Issue Type: Task > Components: Configuration and Management > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: 2.0.0 Beta 1 > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-357) Update the Messaging Core documentation

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-357?page=all ] Tim Fox updated JBMESSAGING-357: -------------------------------- Fix Version/s: Miscellaneous (was: Unscheduled) > Update the Messaging Core documentation > --------------------------------------- > > Key: JBMESSAGING-357 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-357 > Project: JBoss Messaging > Issue Type: Task > Components: Documentation and Training > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Miscellaneous > > Original Estimate: 1 week > Remaining Estimate: 1 week > -- 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, 3 months

1
0
0 / 0

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

by Tim Fox (JIRA)

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

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-354) Start a database with use case info

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-354?page=all ] Tim Fox closed JBMESSAGING-354. ------------------------------- Resolution: Incomplete Description > Start a database with use case info > ----------------------------------- > > Key: JBMESSAGING-354 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-354 > 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

19 years, 3 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