August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-220) Add the possibility to drop a destination.

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-220?page=all ] Ovidiu Feodorov updated JBMESSAGING-220: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.4) > Add the possibility to drop a destination. > ------------------------------------------ > > Key: JBMESSAGING-220 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-220 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Destination Manager > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: 1.2.1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Add the possiblity to administratively (and possibly programmatically) drop a destination. > Dropping a destination means that all persistent messages maintained by the destination are discarded. This is not what happens during the current deployment/undeployment of a destiantion, which currently have an activation/de-activation semantics. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-326) Improve synchronization on queue

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-326?page=all ] Ovidiu Feodorov updated JBMESSAGING-326: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.4) > Improve synchronization on queue > -------------------------------- > > Key: JBMESSAGING-326 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-326 > 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 > > For even better throughput we can remove lock contention between adds and removes on the channel state (when there are more than a few nodes on the linked list). This can be done by using fine grained locking on individual nodes of the linked list. > We need to be very careful here to make sure paging semantics are preserved. -- 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, 10 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 Ovidiu Feodorov (JIRA)

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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-373) Different persistance destinations for different JMS destinations

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-373?page=all ] Ovidiu Feodorov updated JBMESSAGING-373: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.4) > Different persistance destinations for different JMS destinations > ----------------------------------------------------------------- > > Key: JBMESSAGING-373 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-373 > Project: JBoss Messaging > Issue Type: Feature Request > Affects Versions: 1.0.0, 1.0.1.CR1 > Reporter: Milena > Assigned To: Ovidiu Feodorov > Fix For: 1.2.1 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > We need to store the messages from different queues into a different tables, ot at least to separate them somehow. > This is not possible with the current JBOSS Messaging as I was told. > The motivation behind is that since we have a very high load on some of the queues, the persistance table appears a bottleneck for the rest of the messaging. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-327) Improve concurrency for acknowledgement

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-327?page=all ] Ovidiu Feodorov updated JBMESSAGING-327: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.4) > Improve concurrency for acknowledgement > --------------------------------------- > > Key: JBMESSAGING-327 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-327 > 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 > > Improve concurrency in acknnowledgment by using ConcurrentHashSet for deliveries and removing delivery lock -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-306) Supports recovery flag

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-306?page=all ] Ovidiu Feodorov updated JBMESSAGING-306: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.4) > Supports recovery flag > ---------------------- > > Key: JBMESSAGING-306 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-306 > 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 > > Should have flag "supports XA recovery" on persistencemanager. > If = false then only tx id, not all xid fields are persisted on prepare. This should improve performance when xa recovery is not required. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-322) Deploying an MDB for a destination that doesn't exist fails.

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-322?page=all ] Ovidiu Feodorov updated JBMESSAGING-322: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.4) > Deploying an MDB for a destination that doesn't exist fails. > ------------------------------------------------------------ > > Key: JBMESSAGING-322 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-322 > Project: JBoss Messaging > Issue Type: Sub-task > Components: AS Integration > Affects Versions: 1.0.0 > Reporter: Ovidiu Feodorov > Fix For: 1.2.1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > If the destination an MDB is configured with doesn't exist, the MDB Container's JMSContainerInvoker tries to create the destination and fails because uses a non-portable interface that only works with JBossMQ. > Line 1201, org.jboss.ejb.plugins.jms.JMSContainerInvoker.createDestination() > // invoke the server to create the destination > server.invoke(new ObjectName("jboss.mq:service=DestinationManager"), ..... > -- 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, 10 months

1
0
0 / 0

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

by Ovidiu Feodorov (JIRA)

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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-180) Improve message priority algorithm

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-180?page=all ] Ovidiu Feodorov updated JBMESSAGING-180: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.4) > Improve message priority algorithm > ---------------------------------- > > Key: JBMESSAGING-180 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-180 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > The current message priority strategy is very crude and always delivers higher priority messages first if they exist. > This can cause starvation of lower priority messages. > The algorithm should be improved to prevent starvation. > It may be an idea to make the algorithm pluggable using the strategy pattern. -- 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, 10 months

1
0
0 / 0

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

by Ovidiu Feodorov (JIRA)

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

17 years, 10 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