April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-185) Run objectweb JMS tests in top of JBoss Messaging

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-185?page=all ] Tim Fox updated JBMESSAGING-185: -------------------------------- Fix Version/s: 1.2.1.CR1 (was: Unscheduled) Assignee: Clebert Suconic (was: Richard Achmatowicz) > Run objectweb JMS tests in top of JBoss Messaging > ------------------------------------------------- > > Key: JBMESSAGING-185 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-185 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: Clebert Suconic > Fix For: 1.2.1.CR1 > > Original Estimate: 4 days > Remaining Estimate: 4 days > -- 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, 2 months

1
0
0 / 0

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

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-309?page=all ] Tim Fox updated JBMESSAGING-309: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > 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: 2.0.0 Beta 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-126) Possible enhanced message expiry processing

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-126?page=all ] Tim Fox updated JBMESSAGING-126: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > Possible enhanced message expiry processing > ------------------------------------------- > > Key: JBMESSAGING-126 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-126 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Messaging Core > Reporter: Ovidiu Feodorov > Fix For: 2.0.0 Beta 1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Process depending on conclusion on the forum. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-889) Need to add tests for failed over queues in DefaultRouter and RoundRobinRouter

by Tim Fox (JIRA)

Need to add tests for failed over queues in DefaultRouter and RoundRobinRouter ------------------------------------------------------------------------------ Key: JBMESSAGING-889 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-889 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.CR1 Reporter: Tim Fox Assigned To: Ovidiu Feodorov Fix For: 1.2.1 Currently there are no tests that test the new failed over queue functionality that was added -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-275) Move Selector processing IN the Channel

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-275?page=all ] Tim Fox updated JBMESSAGING-275: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > Move Selector processing IN the Channel > --------------------------------------- > > Key: JBMESSAGING-275 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-275 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Fix For: 2.0.0 Beta 1 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Currently, a consumer "arrests" a message that is being handled to it and doesn't match the Selector. That means it returns an active Delivery for it, but it doesn't forward the message to the client. This is because the consumer needs to be able to receiver further messages coming after the non-matching message, and that may potentially match the selector. > This is a poor solution that doesn't scale. We may end up with lots of non-matching messages being "arrested" by a consumer, while they could just be simply returned to the channel and forwarded to other potential consumers. > A possible (right) approach is to move selector processing in the Channel, so the message is not even handled to the non-accepting cosumer. Review this and refactor. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-387) Modify the admin console to work with Messaging while keeping JBossMQ compatibility

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-387?page=all ] Tim Fox updated JBMESSAGING-387: -------------------------------- Fix Version/s: 1.2.1.CR1 (was: Unscheduled) > Modify the admin console to work with Messaging while keeping JBossMQ compatibility > ----------------------------------------------------------------------------------- > > Key: JBMESSAGING-387 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-387 > Project: JBoss Messaging > Issue Type: Sub-task > Components: AS Integration > Reporter: Ovidiu Feodorov > Fix For: 1.2.1.CR1 > > > JSR77 > Charles -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-384) Modify jboss-head build script to include Messaging instead of JBossMQ in the "all" configuration

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-384?page=all ] Tim Fox updated JBMESSAGING-384: -------------------------------- Fix Version/s: 1.2.1.CR1 (was: Unscheduled) > Modify jboss-head build script to include Messaging instead of JBossMQ in the "all" configuration > ------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-384 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-384 > Project: JBoss Messaging > Issue Type: Sub-task > Reporter: Ovidiu Feodorov > Fix For: 1.2.1.CR1 > > > Make sure JBossMQ still works as an alternate JMS provider -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-85) Merge JBossMQ new feature requests into Messaging's list

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-85?page=all ] Tim Fox closed JBMESSAGING-85. ------------------------------ Resolution: Won't Fix This is an ongoing process so I don't think is appropriate to model as a JIRA task > Merge JBossMQ new feature requests into Messaging's list > -------------------------------------------------------- > > Key: JBMESSAGING-85 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-85 > Project: JBoss Messaging > Issue Type: Task > Components: JMS Facade > Reporter: Ovidiu Feodorov > Fix For: Unscheduled > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-147) Make jms local transactions in doubt

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-147?page=all ] Tim Fox updated JBMESSAGING-147: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > Make jms local transactions in doubt > ------------------------------------ > > Key: JBMESSAGING-147 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-147 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 2.0.0 Beta 1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > When 2PC is used, jms server "transactions" (i.e. not JTA transactions - internal server side tx) can be left "hanging" in prepared state by badly behaved or crashed clients. > However we don't want to remove them since we do not know that recovery will not occur in the future therefore we should flag them as in doubt so the administrator can come in and deal with them heuristically -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-749) Null Pointer Exception in"org.drools.reteoo.RuleTerminalNode.retractTuple"

by Michael Anstis (JIRA)

Null Pointer Exception in"org.drools.reteoo.RuleTerminalNode.retractTuple" -------------------------------------------------------------------------- Key: JBRULES-749 URL: http://jira.jboss.com/jira/browse/JBRULES-749 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.1-m1 Environment: Windows XP SP2, JVM1.4 Reporter: Michael Anstis Assigned To: Mark Proctor Attachments: Re rules-users Null Pointer Exceptioninorg.drools.reteoo.RuleTerminalNode.retractTuple.txt Null Pointer Exception thrown when running rule "Rule-4 (Null Pointer Exception)" see attachment for complete, re-producible 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

19 years, 2 months

3
8
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 April 2007