February 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4498) JMS Inbound Resource Adapter does not support JMS1.1

by Adrian Brock (JIRA)

JMS Inbound Resource Adapter does not support JMS1.1 ---------------------------------------------------- Key: JBAS-4498 URL: http://jira.jboss.com/jira/browse/JBAS-4498 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.2.0.GA Reporter: Adrian Brock Fix For: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta3 The JMS inbound resource adapter's server session pool does not support old JMS1.0.2b connections. The issue is with JmsServerSession::setup() that only uses the 1.1 api to create sessions. -- 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, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-3774) Synch up with the ide team on use of the VDF

by Scott M Stark (JIRA)

Synch up with the ide team on use of the VDF -------------------------------------------- Key: JBAS-3774 URL: http://jira.jboss.com/jira/browse/JBAS-3774 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment services Reporter: Scott M Stark Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.0.Beta Part of fleshing out the VDF should be the jbosside integration usecase. -- 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, 5 months

4
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1046) Edit Messages inside Destination

by Hendra Sasmita (JIRA)

Edit Messages inside Destination -------------------------------- Key: JBMESSAGING-1046 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1046 Project: JBoss Messaging Issue Type: Feature Request Components: JMS Destination Manager Reporter: Hendra Sasmita Assigned To: Tim Fox Priority: Optional For administrative purpose, operators may want to change the message's content and/or properties. As example, change all message that has content X, with content Y -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-244) Enable quotas for users

by Tim Fox (JIRA)

[ https://jira.jboss.org/jira/browse/JBMESSAGING-244?page=com.atlassian.jir... ] Tim Fox updated JBMESSAGING-244: -------------------------------- Fix Version/s: 2.1.0.beta (was: 2.0.0 Beta) > Enable quotas for users > ----------------------- > > Key: JBMESSAGING-244 > URL: https://jira.jboss.org/jira/browse/JBMESSAGING-244 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Priority: Optional > Fix For: 2.1.0.beta > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Investigate whether we need to provide quotas functionality for users. I.e. limit number of messages able to send per sec etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1324) Time sensitive queue

by Tim Fox (JIRA)

Time sensitive queue -------------------- Key: JBMESSAGING-1324 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1324 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta Add a time sensitive queue type. with this queue, specify a header JBM_TIME_LIMITED and only latest message with value of this header is retained - internally can use LinkedHashMap instead of LinkedQueue. -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-378) Use memory leak detection within the testsuite

by Tim Fox (JIRA)

[ https://jira.jboss.org/jira/browse/JBMESSAGING-378?page=com.atlassian.jir... ] Tim Fox closed JBMESSAGING-378. ------------------------------- Resolution: Out of Date > Use memory leak detection within the testsuite > ---------------------------------------------- > > Key: JBMESSAGING-378 > URL: https://jira.jboss.org/jira/browse/JBMESSAGING-378 > Project: JBoss Messaging > Issue Type: Task > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: 2.0.0 Beta > > Original Estimate: 2 minutes > Remaining Estimate: 2 minutes > > Clebert's stuff. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1167) Store the reference to the object instead of serializing object upon JBossObjectMessage.setObject.

by Jay Howell (JIRA)

Store the reference to the object instead of serializing object upon JBossObjectMessage.setObject. -------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1167 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1167 Project: JBoss Messaging Issue Type: Feature Request Affects Versions: 1.4.0.SP1 Reporter: Jay Howell Assigned To: Tim Fox Object Serialization happens in the JBossObjectMessage.setObject and then the reference to the object is set to null. This means that if you are delivering messages within the same JVM, the objects still have to go through serialization. This request is to delay serialization until it needs to be sent across the wire. This is a performance optimization aimed at preventing unnecessary serialization. -- 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, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1336) Redeploying queues with different attribute values

by Tim Fox (JIRA)

Redeploying queues with different attribute values -------------------------------------------------- Key: JBMESSAGING-1336 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1336 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta When deploying a queue using JMSManager that already exists but has a different attribute like clustered - do we update the value of the attribute in the journal? -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1443) Reconnect to same server

by Tim Fox (JIRA)

Reconnect to same server ------------------------ Key: JBMESSAGING-1443 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1443 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.0.0 Beta Add reconnect to same server functionality to ClientSessionFactoryImpl. Same failover code can be used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1312) JBM peer to peer mode

by Tim Fox (JIRA)

JBM peer to peer mode --------------------- Key: JBMESSAGING-1312 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1312 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta We should provide a peer to peer mode for JBM. Can start a server in the local process and use invm transport to talk to it. The server has null persistence manager, and communicates using JGroups or UDP to other peers for fast peer to peer transport -- 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, 5 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 February 2009