August 2006 - jboss-jira - Jboss List Archives

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

by Ovidiu Feodorov (JIRA)

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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-122) Implement the stats and monitoring MBean operations on destinations

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-122?page=all ] Ovidiu Feodorov updated JBMESSAGING-122: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.5) > Implement the stats and monitoring MBean operations on destinations > ------------------------------------------------------------------- > > Key: JBMESSAGING-122 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-122 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Configuration and Management > Affects Versions: 1.0.0 alpha PR1 (non-clustered) > Reporter: Tim Fox > Assigned To: Alex Fu > Priority: Critical > Fix For: 1.2.1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Implement all the statistics and monitoring MBean operations on topics and queues, to bring up to level of functionality of JBossMQ. > E.g. message counts, message lists, subscription lists etc. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-313) INVM persistent message optimisation

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-313?page=all ] Ovidiu Feodorov updated JBMESSAGING-313: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.5) > INVM persistent message optimisation > ------------------------------------ > > Key: JBMESSAGING-313 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-313 > 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 > > For persistent messages sent in vm, the message gets converted to a byte[] before db storage, it then gets converted back to a payload on recepipt - this is unnecessary - for the invm case. We should deal with it optimally. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-91) Administrative destinations

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-91?page=all ] Ovidiu Feodorov updated JBMESSAGING-91: --------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.5) > Administrative destinations > --------------------------- > > Key: JBMESSAGING-91 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-91 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Facade > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: 1.2.1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Implement special destinations to allow administration over the jms protocol itself. e.g. You can send a request/response message to the "AdminQueue" that says create me a destination or change my password, etc. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-134) Implement memory sensitive channels

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-134?page=all ] Ovidiu Feodorov updated JBMESSAGING-134: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.5) > Implement memory sensitive channels > ----------------------------------- > > Key: JBMESSAGING-134 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-134 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core Persistence > Reporter: Tim Fox > Assigned To: Ovidiu Feodorov > Fix For: 1.2.1 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Extend the message caching to spill messages on to disk when memory is tight, a la JBossMQ. > Probably re-use much of JBossMQ implementation here. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-43) Change the module name to "messaging"

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-43?page=all ] Ovidiu Feodorov updated JBMESSAGING-43: --------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.5) > Change the module name to "messaging" > ------------------------------------- > > Key: JBMESSAGING-43 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-43 > Project: JBoss Messaging > Issue Type: Task > Components: Build System > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Minor > Fix For: 1.2.1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Changing the CVS module name from "jms" to "messaging". Things to change: > * the module's directory name > * CVSROOT/modules > * tools/etc/buildmagic/modules.ent > * tools/etc/buildmagic/modules.xml > * jms/tests/build.xml > * jms/build.xml -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-242) Investigate requirements for different routing strategies

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-242?page=all ] Ovidiu Feodorov updated JBMESSAGING-242: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.4) > Investigate requirements for different routing strategies > --------------------------------------------------------- > > Key: JBMESSAGING-242 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-242 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Investigate whether we need to provide routers with different strategies, a la ReceiversImpl in JBossMQ -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-319) Enable the Messaging build to use component-info.xml and versioned dependencies

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-319?page=all ] Ovidiu Feodorov updated JBMESSAGING-319: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.5) > Enable the Messaging build to use component-info.xml and versioned dependencies > ------------------------------------------------------------------------------- > > Key: JBMESSAGING-319 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-319 > Project: JBoss Messaging > Issue Type: Task > Components: Build System > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: 1.2.1 > > Original Estimate: 3 days > Remaining Estimate: 3 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-175) Unnecessary junit.timeout2 used by tests/build.xml

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-175?page=all ] Ovidiu Feodorov updated JBMESSAGING-175: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.5) > Unnecessary junit.timeout2 used by tests/build.xml > -------------------------------------------------- > > Key: JBMESSAGING-175 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-175 > Project: JBoss Messaging > Issue Type: Task > Components: Build System > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Priority: Minor > Fix For: 1.2.1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Instead of using junit.timeout2 we should figure out why the normal timeout is not picked up in Tim's case. Revert to using junit.timeout. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-300) Deadlock detection

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-300?page=all ] Ovidiu Feodorov updated JBMESSAGING-300: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.4) > Deadlock detection > ------------------ > > Key: JBMESSAGING-300 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-300 > 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 > > Add deadlock detection in pm, so can run with isolation level of repeatable_read. Now requires isolation level of read_committed -- 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, 11 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