April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-87) Light-weight JMS 1.1 / JGroups package

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-87?page=all ] Tim Fox updated JBMESSAGING-87: ------------------------------- Fix Version/s: Miscellaneous (was: Unscheduled) Priority: Minor (was: Major) > Light-weight JMS 1.1 / JGroups package > -------------------------------------- > > Key: JBMESSAGING-87 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-87 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Facade > Reporter: Bela Ban > Priority: Minor > Fix For: Miscellaneous > > > Motivation: people want to use JGroups, but need to program against a standard API, like JMS 1.1. > Create a distribution which includes only the relevant parts of the JMS 1.1 implementation that runs on top of JGroups (the 'Serverless JMS' part, not the client/server part). -- 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-395) JNDI lookups fail with ClassCastException

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-395?page=all ] Tim Fox updated JBMESSAGING-395: -------------------------------- Fix Version/s: 1.2.1.CR1 (was: Unscheduled) Need to investigate whether this is still an issue > JNDI lookups fail with ClassCastException > ----------------------------------------- > > Key: JBMESSAGING-395 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-395 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Facade > Affects Versions: 1.0.1.CR1 > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Fix For: 1.2.1.CR1 > > > Changes introduced by http://jira.jboss.org/jira/browse/JBMESSAGING-390 cause JNDI lookups to fail with ClassCastException > To replicate: run the MDB smoke tests with 4.0.4.GA. -- 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-242) Investigate requirements for different routing strategies

by Tim Fox (JIRA)

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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-329) Inconsistency in return values

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-329?page=all ] Tim Fox closed JBMESSAGING-329. ------------------------------- Resolution: Won't Fix Out of date > Inconsistency in return values > ------------------------------ > > Key: JBMESSAGING-329 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-329 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: Unscheduled > > Original Estimate: 1 day, 4 hours > Remaining Estimate: 1 day, 4 hours > > Some methods return false to represent failure, others throw an exception - need to be consistent. -- 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-626) Invalid JAXB API in jboss-messaging-client.jar

by Thomas Diesler (JIRA)

Invalid JAXB API in jboss-messaging-client.jar ---------------------------------------------- Key: JBMESSAGING-626 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-626 Project: JBoss Messaging Issue Type: Bug Reporter: Thomas Diesler Assigned To: Ovidiu Feodorov JAXB-1.0 api leaks from jboss-messaging-client into jbossall-client.jar, which breaks the CTS Messaging should have a dependency on jaxb-api.jar and not redistribute the jaxb api Please fix in jbossas/branches/JEE5_TCK -- 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

5
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-454) InVM callbackserver

by Tim Fox (JIRA)

InVM callbackserver ------------------- Key: JBMESSAGING-454 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-454 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.0.1.CR3 Reporter: Tim Fox Fix For: 1.0.2 When running with both client and server invm and using the socket transport, a callbackserver is opened on the client and creates several sockets to listen for incoming requests. This uses up system resources (threads and sockets) which are never used for the invm case. -- 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

4
3
0 / 0

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

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-326?page=all ] Tim Fox closed JBMESSAGING-326. ------------------------------- Resolution: Won't Fix > 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: Unscheduled > > 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

19 years, 2 months

1
0
0 / 0

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

by Tim Fox (JIRA)

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

19 years, 2 months

1
0
0 / 0

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

by Tim Fox (JIRA)

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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-429) Implement intelligent flow control

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-429?page=all ] Tim Fox updated JBMESSAGING-429: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > Implement intelligent flow control > ---------------------------------- > > Key: JBMESSAGING-429 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-429 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Fix For: 2.0.0 Beta 1 > > > We should implement an intelligent flow control mechanism so message sending can be automatically throttled when consumers are slow to prevent messages bulding up on queues/subscriptions. -- 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

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