August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-422) Move channel mapper logic into Queue, Topic, Subscription classes

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-422?page=all ] Ovidiu Feodorov updated JBMESSAGING-422: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.7) > Move channel mapper logic into Queue, Topic, Subscription classes > ----------------------------------------------------------------- > > Key: JBMESSAGING-422 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-422 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > > Much of the logic in the channel mapper is very non OO and should be moved into it's appropriate places in the relevant Queue, Topic or Subscription classes. > It's currently a bit of a mess. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-400) Usage of JBoss serialization should be configurable everywhere

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-400?page=all ] Ovidiu Feodorov updated JBMESSAGING-400: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.7) > Usage of JBoss serialization should be configurable everywhere > -------------------------------------------------------------- > > Key: JBMESSAGING-400 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-400 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > > There are a couple of places in the code (JDBCPersistenceManager and MessageSupport) where JBossObjectInput/Output Streams are being used directly. This should be made 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

19 years, 11 months

1
0
0 / 0

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

by Ovidiu Feodorov (JIRA)

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

1
0
0 / 0

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

by Ovidiu Feodorov (JIRA)

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

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-310) Investigate whether rw lock on ServerConnectionEndpoint is necessary

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-310?page=all ] Ovidiu Feodorov updated JBMESSAGING-310: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.6) > Investigate whether rw lock on ServerConnectionEndpoint is necessary > -------------------------------------------------------------------- > > Key: JBMESSAGING-310 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-310 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-162) Consider implementing different message delivery optimisations

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-162?page=all ] Ovidiu Feodorov updated JBMESSAGING-162: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.6) > Consider implementing different message delivery optimisations > -------------------------------------------------------------- > > Key: JBMESSAGING-162 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-162 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Facade > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Minor > Fix For: 1.2.1 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Consideri implementing different different message delivery optimisations. > e.g. client side buffering > multicast (both reliable and unreliable) > these could be selected by using special, jboss specific ack modes -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-380) Use JBoss retro

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-380?page=all ] Ovidiu Feodorov updated JBMESSAGING-380: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.6) > Use JBoss retro > --------------- > > Key: JBMESSAGING-380 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-380 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > We should consider using JBossRetro in JBossMessaging. This will allow us to use JDK1.5 specific features in the code base, but will still run on JDK1.4. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-257) Optimisation for deliveries immediately returned as done

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-257?page=all ] Ovidiu Feodorov updated JBMESSAGING-257: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.6) > Optimisation for deliveries immediately returned as done > -------------------------------------------------------- > > Key: JBMESSAGING-257 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-257 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Optional > Fix For: 1.2.1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Optimisation: If a delivery is returned as done. There is no need to first store the reference in the channel state as is currently the case. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-330) Consider using remoting raw invocations

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-330?page=all ] Ovidiu Feodorov updated JBMESSAGING-330: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.6) > Consider using remoting raw invocations > --------------------------------------- > > Key: JBMESSAGING-330 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-330 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently we are not using raw remoting invocations so have to package/unpackage the invocation in the marshaller which cause unnecessary code and object creation and is generally messy. If we used remoting raw invocations we could simplify the wire format code. > Pings would still use normal non raw invocations so the session id is passed which is needed on the server side. -- 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, 11 months

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: 1.2.1 (was: 1.0.6) > 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: 1.2.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, 11 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 August 2006