August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-277) Setting remoting lease period to -1 breaks ASF

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-277?page=all ] Ovidiu Feodorov updated JBMESSAGING-277: ---------------------------------------- Fix Version/s: 1.2.0.Alpha1 (was: 1.0.3) > Setting remoting lease period to -1 breaks ASF > ---------------------------------------------- > > Key: JBMESSAGING-277 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-277 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Remoting > Reporter: Ovidiu Feodorov > Fix For: 1.2.0.Alpha1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > LeasePeriod == -1 is supposed to disable remoting leasing. > However, setting LeasePeriod to -1 breaks ASF. TCK tests don't pass anymore. > Whoever fixes this problem, should add a functional test so the Messaging testsuite catches this problem before TCK does. -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-309) Rename createXXXDelegate methods

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-309?page=all ] Ovidiu Feodorov updated JBMESSAGING-309: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.3) > Rename createXXXDelegate methods > -------------------------------- > > Key: JBMESSAGING-309 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-309 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Rename createXXXDelegate methods in ServerXXEndpoint classes to createXXXEndpoint, since they create endpoints, not delegates. -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-355) Remove possibility of delivery race conditions

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-355?page=all ] Ovidiu Feodorov updated JBMESSAGING-355: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.3) > Remove possibility of delivery race conditions > ---------------------------------------------- > > Key: JBMESSAGING-355 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-355 > 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 race conditions can occur on message delivery where the delivery is acknowledged or cancelled before the call to handle has returned. > In ChannelState we defensively program against this by synchronizing on the returned delivery and by dealing with the situation where the delivery does not exist in the channel state and ignoring. > See ChannelSupport::deliver() and ChannelState.cancelDelivery. > This approach has the following problems: > Complexity of code to maintain and understand. > Where acks return quickly we are likely to get contention on the lock in ChannelSupport::deliver, thus reducing throughput. > A much simpler solution enables us to remove the possibility of such race conditions and remove the corresponding lock contention. > This can be done by adding a confirm() method on Delivery. > When the receiver receives the message in it's handle() call, before dispatching the message it calls Delivery::confirm. This results in the channel adding the delivery to the channel state. Thus we can be assured that the delivery exists before any acknowledgment or cancellation comes in. > This is a very simple change. -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-246) Optimise browsing

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-246?page=all ] Ovidiu Feodorov updated JBMESSAGING-246: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.3) > Optimise browsing > ----------------- > > Key: JBMESSAGING-246 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-246 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Currently browsing is inefficient and copies the entire set of message references. Instead we should use the deque iterator + the deliveries iterator. > We should also investigate activating the browsing interceptor to batch messages. -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-197) Refactor Channel, Distributor etc so there is only one receiver per channel

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-197?page=all ] Ovidiu Feodorov updated JBMESSAGING-197: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.3) > Refactor Channel, Distributor etc so there is only one receiver per channel > --------------------------------------------------------------------------- > > Key: JBMESSAGING-197 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-197 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Tim Fox > Assigned To: Ovidiu Feodorov > Fix For: 1.2.1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently channels, allow multiple receivers. > This is unnecessary and adds extra complecity. > There is no need for a channel to ever have more than one active delivery per message reference at any one time. > Channel should be refactored to only have one receiver. > This gives us a much smaller and simpler base building block. -- 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

17 years, 10 months

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: 1.2.1 (was: 1.0.3) > 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: 1.2.1 > > 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-286) I am able to create two different durable subscriptions with same name using the same client ID on the same topic

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-286?page=all ] Ovidiu Feodorov updated JBMESSAGING-286: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.3) > I am able to create two different durable subscriptions with same name using the same client ID on the same topic > ----------------------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-286 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-286 > Project: JBoss Messaging > Issue Type: Bug > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: 1.2.1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > add test 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

17 years, 10 months

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: 1.2.0.Beta1 (was: 1.0.3) > 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: 1.2.0.Beta1 > > 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-351) EJB3 MDB example

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-351?page=all ] Ovidiu Feodorov updated JBMESSAGING-351: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.3) > EJB3 MDB example > ---------------- > > Key: JBMESSAGING-351 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-351 > Project: JBoss Messaging > Issue Type: Sub-task > Affects Versions: 1.0.0 > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: 1.2.1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > A simple EJB3 MDB example -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-312) De-monolithise persistencemanager

by Ovidiu Feodorov (JIRA)

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

17 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2006