January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1141) QueueBrowser sees expired messages

by Carlo de Wolf (JIRA)

QueueBrowser sees expired messages ---------------------------------- Key: JBMESSAGING-1141 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1141 Project: JBoss Messaging Issue Type: Bug Components: JMS Client Manager Affects Versions: 1.4.0.SP1 Reporter: Carlo de Wolf Assigned To: Tim Fox When I send a message which almost immediately expires, a queue browser will still show the message. sender.send(message, DeliveryMode.NON_PERSISTENT, 4, 1); Thread.sleep(2000); QueueBrowser browser = session.createBrowser(queue); Enumeration e = browser.getEnumeration(); List messages = CollectionsUtil.list(e); browser.close(); if(messages.size() == 1) { QueueReceiver receiver = session.createReceiver(dlq); message = (TextMessage) receiver.receive(2000); assertNull(message); } else { assertEquals(0, messages.size()); } -- 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, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1163) Set MessagingTimeoutFactory thread pool configurable

by Abel Munoz Alcaraz (JIRA)

Set MessagingTimeoutFactory thread pool configurable ---------------------------------------------------- Key: JBMESSAGING-1163 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1163 Project: JBoss Messaging Issue Type: Feature Request Components: Messaging Core Affects Versions: 1.4.0.SP1 Environment: All environments Reporter: Abel Munoz Alcaraz Assigned To: Tim Fox It is desirable to do the limits of MessagingTimeoutFactory's thread pool configurables: MaximumQueueSize, MaximumPoolSize, 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1015) Refactor cluster message notification

by Tim Fox (JIRA)

Refactor cluster message notification ------------------------------------- Key: JBMESSAGING-1015 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1015 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta 1 We need an abstract cluster message notification system in place. This should decouple the post office from having to handle all messages via groupMember. The groupMember should be moved out of post office. -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1148) Remove node id address mapping

by Tim Fox (JIRA)

Remove node id address mapping ------------------------------ Key: JBMESSAGING-1148 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1148 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta We can dramatically simplify the way we currently deal with node id- address mappings. We can pass in node id as additional data before call to connect so each address in the view has the extra data - this makes node id - address mapping redundant, and we can remove the join and leave messages. :) We can also remove the failovermap altogether - and generate it on the fly from the view (now it becomes trivial!!) This should vastly simplify things and remove the scope for race conditions. You can associate arbitrary data with an IpAddress, see below: | JChannel c=new JChannel(properties); Map<String,Object> m=new HashMap<String,Object>(); m.put("additional_data", new byte[]{'b', 'e', 'l', 'a'}); c.down(new Event(Event.CONFIG, m)); c.connect("bla"); IpAddress addr=(IpAddress)c.getLocalAddress(); System.out.println("address is " + addr); assertNotNull(addr.getAdditionalData()); assertEquals('b', addr.getAdditionalData()[0]); c.close();| -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-877) Optimise browsing

by Tim Fox (JIRA)

Optimise browsing ----------------- Key: JBMESSAGING-877 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-877 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Currently browsing is inefficient and copies the entire set of message references. Instead we should use the deque iterator + the deliveries iterator. We should also investigate activating the browsing interceptor to batch messages. -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-871) Optimisations

by Tim Fox (JIRA)

Optimisations ------------- Key: JBMESSAGING-871 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-871 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Super task for various performance related optimisations -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-878) Consider using multicast or reliable multicast for message delivery

by Tim Fox (JIRA)

Consider using multicast or reliable multicast for message delivery ------------------------------------------------------------------- Key: JBMESSAGING-878 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-878 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 We could use multicast or jgroups reliable multicast for delivery of messages from server to client when there are many subscribers - currently this is point to point. -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-874) INVM persistent message optimisation

by Tim Fox (JIRA)

INVM persistent message optimisation ------------------------------------ Key: JBMESSAGING-874 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-874 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-998) Impelment security for temporary destinations

by Sergey Koshcheyev (JIRA)

Impelment security for temporary destinations --------------------------------------------- Key: JBMESSAGING-998 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-998 Project: JBoss Messaging Issue Type: Feature Request Components: JMS Security Reporter: Sergey Koshcheyev Assigned To: Tim Fox There should probably be some attribute on the ConnectionFactory to set permissions required to use temporary destinations. See the forum thread for discussion. -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-784) Add Active/Passive deployment feature for JBoss Messaging in 2 node cluster (Need HA part and not Clustering part)

by Rohit Chowdhary (JIRA)

Add Active/Passive deployment feature for JBoss Messaging in 2 node cluster (Need HA part and not Clustering part) ------------------------------------------------------------------------------------------------------------------ Key: JBMESSAGING-784 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-784 Project: JBoss Messaging Issue Type: Task Components: JMS Clustering Affects Versions: 1.2.1 Reporter: Rohit Chowdhary Assigned To: Ovidiu Feodorov Need to be able to deploy JBoss Messaging nodes in a HA configuration, but not load-balanced. Such that only one node is actively serving all the requests, if the current active node goes down, then the passive node picks up the load. Reason would be: To use the available h/w resources at best. We have one dedicated physical server for running JBoss msg. Another physical server that hosts existing JBoss instance running some application. We want to use this second server running a passive JBossMsg instance. So in case when the dedicated JBossMsg goes down, then the second shared server can take the load temporarily automatically, till we bring back the dedicated up again. Other reason would be that we bring down the dedicated JBossMsg server for OS level patching, essentially minimizing the app downtime and increase availablity. -- 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, 9 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 January 2008