May 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-857) HTTP stress tests fail

by Ovidiu Feodorov (JIRA)

HTTP stress tests fail ---------------------- Key: JBMESSAGING-857 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-857 Project: JBoss Messaging Issue Type: Bug Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.GA The HTTP stress tests have been temporarily commented out. To be enabled and fixed for 1.2.0.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

18 years, 2 months

3
11
0 / 0

[JBoss JIRA] Closed: (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 closed JBMESSAGING-87. ------------------------------ Resolution: Out of Date > 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: Unscheduled > > > 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1086) Implement Database updater

by Tim Fox (JIRA)

Implement Database updater -------------------------- Key: JBMESSAGING-1086 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1086 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta 1 JBM 2.0 will use local persistent storage per node, in most cases non relational. Some users still like to see their messages in a database. We should implement a component that can optionally run on each node, that intermittently checks the local storage to new messages / delete messages and updates a shared database with the message data. Hibernate should be used for this component so it can work with any supported RDBMs. -- 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
4
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-210) ServerPeer.createTopic(...)/createQueue(...) implementation suboptimal

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-210?page=all ] Tim Fox closed JBMESSAGING-210. ------------------------------- Fix Version/s: Unscheduled (was: 2.0.0 Beta) Resolution: Out of Date > ServerPeer.createTopic(...)/createQueue(...) implementation suboptimal > ---------------------------------------------------------------------- > > Key: JBMESSAGING-210 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-210 > Project: JBoss Messaging > Issue Type: Task > Components: Configuration and Management > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > Original Estimate: 1 day > Remaining Estimate: 1 day > > ServerPeer.createTopic(...)/createQueue(...) are JMX managed operations that allow to programatically create a JMS destination. The implementation is suboptimal in that it parses a literal representation of an destination MBean configuration and deploys the resulted org.w3c.dom.Element. It also accesses directly ServiceCreator and UnifiedClassLoader3 interfaces. Review the implementation. -- 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: (JBMESSAGING-1040) Update to Java 5 GUIDs

by Tim Fox (JIRA)

Update to Java 5 GUIDs ---------------------- Key: JBMESSAGING-1040 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1040 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta 1 Since we are now Java 5 only, we can update to Java 5 guids. We can also get rid of the message id generator stuff. -- 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

[JBoss JIRA] Created: (JBMESSAGING-662) Implement XAResource.forget()

by Juha Lindfors (JIRA)

Implement XAResource.forget() ----------------------------- Key: JBMESSAGING-662 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-662 Project: JBoss Messaging Issue Type: Task Components: Messaging Core Reporter: Juha Lindfors Assigned To: Juha Lindfors This is currently a no-op. -- 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

3
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1206) Add scheduled delivery and destination to SendPacket

by Tim Fox (JIRA)

Add scheduled delivery and destination to SendPacket ---------------------------------------------------- Key: JBMESSAGING-1206 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1206 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Alpha They don't really belong in the message. Uncomment ScheduledDeliveryTest when this is complete -- 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
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1208) Convert messages to write to buffer directly

by Tim Fox (JIRA)

Convert messages to write to buffer directly -------------------------------------------- Key: JBMESSAGING-1208 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1208 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta Currently our message classes write / read themselves using a DataInput/OutputStream. This is then converted to a byte[] which is used to set the MINA buffer. With our new transport this is a sub optimal way of doing things. Instead, our messages should write themselves directly to an abstraction which wraps the MINA buffer, eliminating unnecessary copying. -- 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

[JBoss JIRA] Updated: (JBMESSAGING-381) Add param on destination to disable persistence

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-381?page=all ] Tim Fox updated JBMESSAGING-381: -------------------------------- Fix Version/s: 2.0.0 Alpha (was: 2.0.0 Beta) > Add param on destination to disable persistence > ----------------------------------------------- > > Key: JBMESSAGING-381 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-381 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Jeff Mesnil > Fix For: 2.0.0 Alpha > > Attachments: patch-JBMESSAGING-381.txt > > Original Estimate: 1 day > Remaining Estimate: 1 day > > We should add a configuration param on destinations which id true prevents messages being persisted even if they are persistent. > This should give equivalent functionality to the JBossMQ NullPersistenceManager. > in some circumstances uses want to override persistence for messages but have no access to change the delivery mode at the sender. -- 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: (JBMESSAGING-1191) BDB PM memory usage

by Tim Fox (JIRA)

BDB PM memory usage ------------------- Key: JBMESSAGING-1191 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1191 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta BDB JE copies any byte arrays and stores them in its cache. This means the message payload can exist in two places in memory. To avoid this, after persisting a P message, we can drop the payload, and lazily retrieve it from the cache at delivery. This technique may also provides a means to avoid paging.. -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2008