September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Reopened: (JBMESSAGING-332) Consider how best to factor paging logic out of channel state

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-332?page=all ] Tim Fox reopened JBMESSAGING-332: --------------------------------- > Consider how best to factor paging logic out of channel state > ------------------------------------------------------------- > > Key: JBMESSAGING-332 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-332 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Need to consider whether to make paging strategy pluggable and factor current implementation out into a concrete implementation. -- 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, 8 months

1
0
0 / 0

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

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-310?page=all ] Tim Fox reopened JBMESSAGING-310: --------------------------------- > 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, 8 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-269) Review ChannelMapper interface for possible functionality separation

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-269?page=all ] Tim Fox reopened JBMESSAGING-269: --------------------------------- > Review ChannelMapper interface for possible functionality separation > -------------------------------------------------------------------- > > Key: JBMESSAGING-269 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-269 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Priority: Minor > Fix For: 1.2.0.Alpha1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently, ChannelMapper seem to cram two different sets of concerns (core channel to destination mapping and durable subscription management) under the same interface. Review the interface (and the implementation) in search for a better solution, possibly involving service separation (DurableSubscriptionStore and ChannelMapper). -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-267) Re-enable distributed tests

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-267?page=all ] Tim Fox reopened JBMESSAGING-267: --------------------------------- > Re-enable distributed tests > --------------------------- > > Key: JBMESSAGING-267 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-267 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.Alpha1 > > > Distributed destination tests have been disabled until after the 1.0 release since it is time consuming to keep them working when 1.0 will not include distributed destinations and the implementation is likely to change anyway after 1.0. > These tests should be re-enabled and adjusted as necessary for the 1.2 release. > All tests in org.jboss.test.messaging.core.distributed and sub packages have been disabled. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-228) Re-enable DistributedTopicTest testDistributedTopic_2() and testDistributedTopic_4()

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-228?page=all ] Tim Fox reopened JBMESSAGING-228: --------------------------------- > Re-enable DistributedTopicTest testDistributedTopic_2() and testDistributedTopic_4() > ------------------------------------------------------------------------------------- > > Key: JBMESSAGING-228 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-228 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Fix For: 1.2.0.Alpha1 > > > I have overridden org.jboss.test.messaging.core.distributed.topic.base.DistributedTopicTestBase's testDistributedTopic_2() and testDistributedTopic_4(() > because they don't match the current assumption that a Channel has only one receiver, and still we want a clean test run. > Adjust tests accordingly and enable them when this assumption will be better wired into the core and DistributedTopic reviewed. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-200) Complete XA transaction recovery

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-200?page=all ] Tim Fox reopened JBMESSAGING-200: --------------------------------- > Complete XA transaction recovery > -------------------------------- > > Key: JBMESSAGING-200 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-200 > Project: JBoss Messaging > Issue Type: Task > Components: JMS Facade > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Critical > Fix For: 1.2.0.Beta1 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Complete XA transaction recovery. > Most of the work is already in place for this. > The remaining pars mainly revolve around integrating with Transaction Managers e.g. Arjuna (and maybe others!) so they can obtain a handle to the XAResource in order to carry out recovery. > The mechanism for this is not specified and so will vary from Transaction Manager to transaction manager. We need to supply wrappers for each popular Transaction Manager. > We also need to complete the tests for this. (Perhaps Arjuna already has some tests we can re-use?) -- 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, 8 months

1
0
0 / 0

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

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-197?page=all ] Tim Fox reopened JBMESSAGING-197: --------------------------------- > 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: Tim Fox > Fix For: 1.2.0.Alpha1 > > 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-199) Fix or mothball remotetopic so it does not require multiple deliveries per message reference

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-199?page=all ] Tim Fox reopened JBMESSAGING-199: --------------------------------- Assignee: Tim Fox (was: Ovidiu Feodorov) > Fix or mothball remotetopic so it does not require multiple deliveries per message reference > -------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-199 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-199 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core Distributed Support > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.Alpha1 > > > Re-implement remote topic to be a router with multiple channels - one per peer. > This means it is not necessary to store receiver id persistently and there is only one delivery per reference per channel. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-192) Refactor Replicator so it won't be forced to provide noop implementation for Distributor's methods.

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-192?page=all ] Tim Fox reopened JBMESSAGING-192: --------------------------------- > Refactor Replicator so it won't be forced to provide noop implementation for Distributor's methods. > --------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-192 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-192 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core Distributed Support > Affects Versions: 1.0.0 alpha PR2 (clustered) > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Priority: Minor > Fix For: 1.2.0.Alpha1 > > > A replicator doesn't really need to implement org.jboss.messaging.core.Router, since its receivers are remote. It only needs support for > Set handle(DeliveryObserver observer, Routable routable, Transaction transaction) > However, currently the easiest way to plug a Replicator into the ChannelSupport implementation is to declare it Router. Refractor this and split the Router interface (and ChannelSupport implementation) in two distinct parts: MultiReceiver (or some other name) and Distributor. > Look for UnsupportedOperationException in org.jboss.messaging.core.distributed.replicator.Replicator. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-414) Simplify delivery hierarchy

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-414?page=all ] Tim Fox closed JBMESSAGING-414. ------------------------------- Fix Version/s: 1.2.0.Alpha1 Fix Version/s: (was: 1.2.1) Resolution: Done > Simplify delivery hierarchy > --------------------------- > > Key: JBMESSAGING-414 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-414 > Project: JBoss Messaging > Issue Type: Task > Affects Versions: 1.0.1.CR2 > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.Alpha1 > > > The current delivery hierarchy seems over complex. > A delivery only ever comes from one Receiver so the all we need is a: > Delivery interface > and > SimpleDelivery implementation > Methods like acknowledge(), cancel() should be in the Delivery interface. -- 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, 8 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 September 2006