January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBMESSAGING-140) Move responsibility for management of delivery list from receiver into channel

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-140?page=all ] Ovidiu Feodorov closed JBMESSAGING-140. --------------------------------------- Resolution: Won't Fix Fix Version/s: (was: 1.2.0.CR1) 1.2.0.Beta2 > Move responsibility for management of delivery list from receiver into channel > ------------------------------------------------------------------------------ > > Key: JBMESSAGING-140 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-140 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.Beta2 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Currently each receiver has the responsibility for managing it's list of deliveries. This is to avoid a race condition whereby the message can be acked before the call to handle has returned. > This is a high burden of responsibility for the receiver and results in a lot of unnecessary code in the receiver implementation, plus an extra hashmap lookup > We should consider whether we can give the responsibiltty to the channel. > We could still acknowledge and cancel throught the delivery object, by creating one when required and calling cancel/acknowledge on it. > the instance of delivery won't contain a message reference but just a message id. then inside delivery.cancel()/acknowledge(), it calls > channel.cancel(this) and the channel is smart enought to lookup the delivery/reference as required. > This won't require ANY changes to the receiver/channel interface and will allow us to get rid of the delivery list -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-150) TCK sould test Messaging, and not JBossMQ, by default

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-150?page=all ] Ovidiu Feodorov reopened JBMESSAGING-150: ----------------------------------------- > TCK sould test Messaging, and not JBossMQ, by default > ----------------------------------------------------- > > Key: JBMESSAGING-150 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-150 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: Prabhat Jha > Priority: Minor > Fix For: 1.2.0.CR1 > > > Modify j2eetck-mods so when Vendor Implementation config is built, it will include by default Messaging, and not MQ. Testing Messaging shouldn't require any other additional steps. > See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingTCK for the current state of affairs. > All TCK-related Messaging configuration files and build scripts are in https://svn.jboss.org/repos/messaging/trunk/src/cts/. They probably should be moved to j2eetck-mods. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-140) Move responsibility for management of delivery list from receiver into channel

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-140?page=all ] Ovidiu Feodorov reopened JBMESSAGING-140: ----------------------------------------- > Move responsibility for management of delivery list from receiver into channel > ------------------------------------------------------------------------------ > > Key: JBMESSAGING-140 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-140 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.Beta2 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Currently each receiver has the responsibility for managing it's list of deliveries. This is to avoid a race condition whereby the message can be acked before the call to handle has returned. > This is a high burden of responsibility for the receiver and results in a lot of unnecessary code in the receiver implementation, plus an extra hashmap lookup > We should consider whether we can give the responsibiltty to the channel. > We could still acknowledge and cancel throught the delivery object, by creating one when required and calling cancel/acknowledge on it. > the instance of delivery won't contain a message reference but just a message id. then inside delivery.cancel()/acknowledge(), it calls > channel.cancel(this) and the channel is smart enought to lookup the delivery/reference as required. > This won't require ANY changes to the receiver/channel interface and will allow us to get rid of the delivery list -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-178) Run TCK continuously in top of JBoss Messaging

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-178?page=all ] Ovidiu Feodorov closed JBMESSAGING-178. --------------------------------------- Resolution: Done > Run TCK continuously in top of JBoss Messaging > ---------------------------------------------- > > Key: JBMESSAGING-178 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-178 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: Prabhat Jha > Fix For: 1.2.0.Beta2 > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-178) Run TCK continuously in top of JBoss Messaging

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-178?page=all ] Ovidiu Feodorov updated JBMESSAGING-178: ---------------------------------------- Fix Version/s: (was: 1.2.0.CR1) 1.2.0.Beta2 > Run TCK continuously in top of JBoss Messaging > ---------------------------------------------- > > Key: JBMESSAGING-178 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-178 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: Prabhat Jha > Fix For: 1.2.0.Beta2 > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBMESSAGING-264) Message bridge

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-264?page=all ] Tim Fox reassigned JBMESSAGING-264: ----------------------------------- Assignee: Tim Fox (was: Ovidiu Feodorov) > Message bridge > -------------- > > Key: JBMESSAGING-264 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-264 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Chris DeLashmutt > Assigned To: Tim Fox > Fix For: 1.2.0.Beta2 > > > Provide a mechanism to forward messages from one destination to another automatically > I have had requests for this feature many times. Basically, people seem to want to be able to have a component in messaging that will automatically forward messages to another destination. This destination could be in the same messaging server or some remote destination. I'm thinking that the process must either be a daemon or an MDB, and since JBossMsg will also be available standalone I'm thinking we make it an MBean. Another KEY to making this work is the 2PC stuff from Arjuna which isn't there yet (to make the pop and the push transactional). -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-178) Run TCK continuously in top of JBoss Messaging

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-178?page=all ] Ovidiu Feodorov reopened JBMESSAGING-178: ----------------------------------------- > Run TCK continuously in top of JBoss Messaging > ---------------------------------------------- > > Key: JBMESSAGING-178 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-178 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: Prabhat Jha > Fix For: 1.2.0.CR1 > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-698) HATest::testTopicSubscriber fails

by Tim Fox (JIRA)

HATest::testTopicSubscriber fails ---------------------------------- Key: JBMESSAGING-698 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-698 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Beta1 Reporter: Tim Fox Assigned To: Clebert Suconic Fix For: 1.2.0.CR1 Only fails when run as part of the test suite. Passes when run standalone using runtest: <failure message="expected not same" type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError: expected not same at org.jboss.test.messaging.jms.clustering.HATest.testTopicSubscriber(HATest.java:1108) </failure> -- 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, 4 months

3
5
0 / 0

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

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-324?page=comments#action_12... ] Tim Fox commented on JBMESSAGING-324: ------------------------------------- This should now work. Needs to be verified. > 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, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-250) Put performance testing framework in it's own subproject

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-250?page=all ] Tim Fox closed JBMESSAGING-250. ------------------------------- Fix Version/s: 1.2.0.Beta2 Fix Version/s: (was: 1.2.1) Assignee: Ovidiu Feodorov (was: Tim Fox) Resolution: Done > Put performance testing framework in it's own subproject > -------------------------------------------------------- > > Key: JBMESSAGING-250 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-250 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Ovidiu Feodorov > Fix For: 1.2.0.Beta2 > > -- 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, 4 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 January 2007