February 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1209) Abstract out JMS selector

by Tim Fox (JIRA)

Abstract out JMS selector ------------------------- Key: JBMESSAGING-1209 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1209 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta We need to abstract out our current JMS selector so can be used in the new core. -- 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

18 years, 5 months

1
1
0 / 0

[JBoss JIRA] Deleted: (JBMESSAGING-1193) Adaptive buffering

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-1193?page=all ] Tim Fox deleted JBMESSAGING-1193: --------------------------------- > Adaptive buffering > ------------------ > > Key: JBMESSAGING-1193 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1193 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > > We can implement clever client side buffering where the consumer effectively starts off as slowConsumers = true (no buffering), then the time to process a message is measured and the buffer size computed dynamically according to that. -- 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

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1143) Acknowledge in single tx optimisation

by Tim Fox (JIRA)

Acknowledge in single tx optimisation ------------------------------------- Key: JBMESSAGING-1143 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1143 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta Current for client_ack or dups_ok we acknowledge each message in the list in a separate jdbc tx when persistent - this can be done in a single tx Furthermore, no need to send the complete list of ids to acknowledge - they will be contiguent - and can be worked out from the delivery list in the session. For a transacted session the same applies. -- 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

18 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1039) HTTP poller doesn't stop

by Tim Fox (JIRA)

HTTP poller doesn't stop ------------------------ Key: JBMESSAGING-1039 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1039 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.CR2 I have temporarily commented out clusterviewupdatetst::testUpdateMixedConnectionFactory since, once started, the HTTP poller doesn't stop. Maybe this is a bug in remoting - need to investigate. -- 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

18 years, 5 months

1
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1017) Upgrade to JGroups 2.5

by Tim Fox (JIRA)

Upgrade to JGroups 2.5 ---------------------- Key: JBMESSAGING-1017 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1017 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta 1 -- 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

18 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-934) Management Queue

by Clebert Suconic (JIRA)

Management Queue ---------------- Key: JBMESSAGING-934 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-934 Project: JBoss Messaging Issue Type: Feature Request Affects Versions: 1.2.0.SP1, 1.2.0.GA Reporter: Clebert Suconic Assigned To: Tim Fox Fix For: 1.2.1.CR1 This is an Adrian's request... We could have a management queue to create queues and topics... -- 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

18 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1021) Move client side transaction state to the server side

by Tim Fox (JIRA)

Move client side transaction state to the server side ----------------------------------------------------- Key: JBMESSAGING-1021 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1021 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta 1 Currently we hold the incomplete JMS transactional state on the client side and send it all in one go on commit. Instead we should store it on the server side. This will simplify things and allow larger transactions to be built without a large pause on commit or exhausting client side memory -- 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

18 years, 5 months

1
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1025) Add test in GroupManagementTest

by Tim Fox (JIRA)

Add test in GroupManagementTest ------------------------------- Key: JBMESSAGING-1025 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1025 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.CR2 .... that tests that failover map is created in vew order -- 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

18 years, 5 months

1
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-989) Core refactoring

by Tim Fox (JIRA)

Core refactoring ---------------- Key: JBMESSAGING-989 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-989 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta 1 Core refactoring- The old core classes are in dire need of reviewing and refactoring. The hierarchy of channel classes should be collapsed for simplicity, since there is only one real implementation of a channel. And the router class should be re-examined - do we need iterator etc Do we need iterator on the channel? All classes should be made cluster aware (including router). We can simplify things a *lot*! -- 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

18 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-875) Non durable subscription optimisation

by Tim Fox (JIRA)

Non durable subscription optimisation ------------------------------------- Key: JBMESSAGING-875 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-875 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Since non durable subscriptions only live for the life-time of the consumer the it's struck me that we don't actually need to send any acks from the client to the server as messages are acknowledged for non durable subs. Basically I think we can acknowledge them before they are sent from server to client. This is because there's no case where messages will be redelivered from the server to the non durable sub, therefore no need for acks. On session recovery and session rollback messages are redelivered locally (i.e. they are already on the client) so no need for the server to redeliver. This also means we don't need to maintain a delivery list in the server consumer endpoint in this case, and the server consumer endpoint can return a done delivery every time. -- 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

18 years, 5 months

2
6
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 February 2008