October 2007 - jboss-jira - Jboss List Archives

[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: -------------------------------- Priority: Minor (was: Major) > 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 > Priority: Minor > 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-153) Support for very large messages

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-153?page=all ] Tim Fox updated JBMESSAGING-153: -------------------------------- Summary: Support for very large messages (was: JBoss Messaging should be capable of handling real big files (tens of megabytes possibly a hundred)) > Support for very large messages > ------------------------------- > > Key: JBMESSAGING-153 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-153 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Messaging Core > Affects Versions: 1.0.0 alpha PR3 > Reporter: Karl de Boer > Fix For: 2.0.0 Beta 1 > > Original Estimate: 4 minutes > Remaining Estimate: 4 minutes > > As dicussed during JBW Barcelona i want to ask to investigate if it is posible to reliably sent very big messages from one jboss messaging node to another one (most likely on top of HTTPS(S). The business case is: mulitple organisations working in one workflow on digitally signed documents where Quality of Service is extremely important for instance patent applications. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-377) Competing consumer on subscriptions

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-377?page=all ] Tim Fox updated JBMESSAGING-377: -------------------------------- Priority: Minor (was: Major) > Competing consumer on subscriptions > ----------------------------------- > > Key: JBMESSAGING-377 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-377 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Minor > Fix For: 2.0.0 Beta 1 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We should add an ability to have competing consumers on (durable) subscriptions. This will allow us to load balance processing of messages from a durable subscription across multiple consumers. -- 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, 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: -------------------------------- Priority: Minor (was: Major) > 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 > Priority: Minor > 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-406) Enabled local persistent storage per node

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=comments#action_12... ] Tim Fox commented on JBMESSAGING-406: ------------------------------------- Currently messages are persisted via a RDBMs which is shared by all nodes in the cluster. This provides a bottleneck. Also RDBMs are not well suited for persisting queue like data. Each node should have its own persistent store for performance and scalability. For failover all persistent stores should available by all nodes on a shared file system (e.g. GFS) - failover then becomes a simple matter of reopening the file based store on a different node on failover. Where a shared filesystem is not available we will have to consider replicating to a buddy. The best candidate for implementing local persistence currently is Berkely DB. However, due to the Berkely DB licence we cannot distribute it with JBM, therefore it would be up to the user to drop the Berkely DB jar in manually as part of the install. We we would also need to provide a very simple JDBC PersistenceManager implementation to allow to run the tests and play about with the default distribution - this can work with HSQLDB. > Enabled local persistent storage per node > ----------------------------------------- > > Key: JBMESSAGING-406 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Critical > Fix For: 2.0.0 Beta 1 > > > Implement non shared file based persistent store. > Look at whether we can re-use stuff (ObjectStore) from JBoss Transactions to implement this. > Also look at HOWL. http://howl.objectweb.org/ -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-406) Enabled local persistent storage per node

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=all ] Tim Fox updated JBMESSAGING-406: -------------------------------- Summary: Enabled local persistent storage per node (was: Enable file based persistent stores) Issue Type: Task (was: Feature Request) Priority: Critical (was: Major) > Enabled local persistent storage per node > ----------------------------------------- > > Key: JBMESSAGING-406 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Critical > Fix For: 2.0.0 Beta 1 > > > Implement non shared file based persistent store. > Look at whether we can re-use stuff (ObjectStore) from JBoss Transactions to implement this. > Also look at HOWL. http://howl.objectweb.org/ -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-25) Microcontainer integration

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-25?page=comments#action_123... ] Tim Fox commented on JBMESSAGING-25: ------------------------------------ We should also remove all references to JNDI from our core POJOs. JBM should be usable, embedded without any use of JNDI. All JNDI usage should occur in a separate layer. > Microcontainer integration > -------------------------- > > Key: JBMESSAGING-25 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-25 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Aaron Walker > Priority: Critical > Fix For: 2.0.0 Beta 1 > > Attachments: JBMESSAGING-26.tar > > > We should POJOify all our current MBean services and allow the microcontainer to enforce dependencies. > The microcontainer can also provide MBean interfaces transparently if needed. > This task is critical in allowing an "embedded JBM". > This is critical to kick start ESB. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-25) Microcontainer integration

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-25?page=all ] Tim Fox updated JBMESSAGING-25: ------------------------------- Description: We should POJOify all our current MBean services and allow the microcontainer to enforce dependencies. The microcontainer can also provide MBean interfaces transparently if needed. This task is critical in allowing an "embedded JBM". This is critical to kick start ESB. was: We should POJOify all our current MBean services and allow the microcontainer to enforce dependencies. The microcontainer can also provide MBean interfaces transparently if needed. This task is critical in allowing an "embedded JBM". This is critical to kick start ESB Priority: Critical (was: Major) > Microcontainer integration > -------------------------- > > Key: JBMESSAGING-25 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-25 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Aaron Walker > Priority: Critical > Fix For: 2.0.0 Beta 1 > > Attachments: JBMESSAGING-26.tar > > > We should POJOify all our current MBean services and allow the microcontainer to enforce dependencies. > The microcontainer can also provide MBean interfaces transparently if needed. > This task is critical in allowing an "embedded JBM". > This is critical to kick start ESB. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-259) Activate compression in marshaller

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-259?page=all ] Tim Fox closed JBMESSAGING-259. ------------------------------- Resolution: Rejected > Activate compression in marshaller > ---------------------------------- > > Key: JBMESSAGING-259 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-259 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Minor > Fix For: 2.0.0 Beta 1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Activate compression in marshaller for messages > x bytes. Make it configurable -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1051) A bean without a security domain doesn't propagate caller

by Carlo de Wolf (JIRA)

A bean without a security domain doesn't propagate caller --------------------------------------------------------- Key: EJBTHREE-1051 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1051 Project: EJB 3.0 Issue Type: Bug Components: Security Reporter: Carlo de Wolf Assigned To: Anil Saldhana In rev 65440 I changed the stateful unit test so that StatelessBean does have a security domain. But it should also work without one. -- 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, 2 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007