September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-435) PointToPoint delivery with multiple consumers and selectors is broken

by Tim Fox (JIRA)

PointToPoint delivery with multiple consumers and selectors is broken --------------------------------------------------------------------- Key: JBMESSAGING-435 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-435 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.CR3 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.0.2 The temporary "hack" fix put in to address JBMESSAGING-275 also breaks point to point delivery. If there is a queue with multiple competing consumers with different selectors. If a messages doesn't match the first consumer but does match the second consumer, because it is "arrested" in the first consumer, then the point to point router does not try it with the second consumer. Instead of "hacking the hack" we should fix all of this properly when we do JBMESSAGING-275 -- 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

2
6
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-425) Naming of Pipe and Distributed Pipe

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-425?page=all ] Tim Fox closed JBMESSAGING-425. ------------------------------- Resolution: Done > Naming of Pipe and Distributed Pipe > ----------------------------------- > > Key: JBMESSAGING-425 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-425 > Project: JBoss Messaging > Issue Type: Task > Affects Versions: 1.0.1.CR3 > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Minor > Fix For: 1.2.0.Alpha1 > > > The "Pipe" instance is basically a reliable channel that forwards from input to output. > However the "DistributedPipe" is not a channel at all and seems to be just an abstraction of a remote connection, so seems to have no relation whatsoever to a "Pipe". > Suggestion is to rename these classes to something that makes a bit more sense and is less confusing. -- 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-422) Move channel mapper logic into Queue, Topic, Subscription classes

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-422?page=all ] Tim Fox closed JBMESSAGING-422. ------------------------------- Resolution: Done Fix Version/s: 1.2.0.Alpha1 (was: 1.2.1) > 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.0.Alpha1 > > > 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, 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. ------------------------------- 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

[JBoss JIRA] Closed: (JBMESSAGING-404) Remove Channel::deliver(Receiver r) method

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-404?page=all ] Tim Fox closed JBMESSAGING-404. ------------------------------- Resolution: Done > Remove Channel::deliver(Receiver r) method > ------------------------------------------ > > Key: JBMESSAGING-404 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-404 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.Alpha1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > This method is used to effectively do a synchronous receive() on a channel. > The functionality could be more simply implemented by doing adding a MessageReference receive() method. > This would also help in a clustered environment since we would have one less network RPC. > Most of the complexity here is in updating tests. -- 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-361) WireFormatTest.testNullResponse(), testDeactivateResponse() fragments invalid

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-361?page=all ] Tim Fox closed JBMESSAGING-361. ------------------------------- Resolution: Done > WireFormatTest.testNullResponse(), testDeactivateResponse() fragments invalid > ----------------------------------------------------------------------------- > > Key: JBMESSAGING-361 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-361 > Project: JBoss Messaging > Issue Type: Sub-task > Components: JMS Facade > Affects Versions: 1.0.0 > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Fix For: 1.2.0.Alpha1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Switching to jboss-serialization 1.0.0.CR7 uncovered what apparently seems to be an invalid test section in WireFormatTest > public void testNullResponse() throws Exception > { > MessagingMarshallable mm = new MessagingMarshallable((byte)77, null); > InvocationResponse resp = new InvocationResponse(null, mm, false, null); > ByteArrayOutputStream bos = new ByteArrayOutputStream(); > JBossObjectOutputStream oos = new JBossObjectOutputStream(bos); > > wf.write(resp, oos); > oos.flush(); > > ByteArrayInputStream bis = new ByteArrayInputStream(bos.toByteArray()); > DataInputStream dis = new DataInputStream(bis); > > // First byte should be version > assertEquals(77, dis.readByte()); > ........... > } > It doesn't make sense to me to write stuff to a JBossObjectOutputStream and then try to read the serialized content using a DataInputStream, and yet this is what this test section does. JBoss Serialization doesn't guarantee this in its public contract. > Excerpt form a conversation with Clebert: > flanker707: Does JBossSerialization guarantee that something written with on a JBossObjectOutuptStream can be read with DataInputStream? > Clebert Suconic: no... I didn't mean to > flanker707: is this in the public contract? > Clebert Suconic: If you use the same thing with ObjectInputStream.. you would have the same problem > testNullResponse(), testDeactivateResponse() sections commented out until clarified. -- 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-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 closed JBMESSAGING-332. ------------------------------- Resolution: Done Fix Version/s: (was: 1.2.1) 1.2.0.Alpha1 > 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.0.Alpha1 > > 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] Closed: (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 closed JBMESSAGING-310. ------------------------------- Fix Version/s: (was: 1.2.1) Resolution: Done Fix Version/s: 1.2.0.Alpha1 > 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.0.Alpha1 > > 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] Closed: (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 closed JBMESSAGING-269. ------------------------------- Resolution: Done > 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] Closed: (JBMESSAGING-267) Re-enable distributed tests

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-267?page=all ] Tim Fox closed JBMESSAGING-267. ------------------------------- Resolution: Done > 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

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