December 2007 - 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

15 years, 7 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

15 years, 7 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

15 years, 7 months

2
2
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

15 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1214) Discard consumer messages

by Tim Fox (JIRA)

Discard consumer messages ------------------------- Key: JBMESSAGING-1214 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1214 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta Some message data e.g. stock prices is transitory, if the consumer is slow, we don't want many messages for the consumer to build up in its subscription. We should allow for the max number of messages to keep over and above the prefetch buffer to be specified. Older messages are removed. -- 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

15 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-889) Up-port SimpleMultiplexer from Branch_4_2

by Carlo de Wolf (JIRA)

Up-port SimpleMultiplexer from Branch_4_2 ----------------------------------------- Key: EJBTHREE-889 URL: http://jira.jboss.com/jira/browse/EJBTHREE-889 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD -- 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

15 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-544) Use NBIO for connection model

by Tim Fox (JIRA)

Use NBIO for connection model ----------------------------- Key: JBMESSAGING-544 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-544 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 For throughput and scalability we need to use a non blocking IO model to provide connections between jms clients and server. Unfortunately the JBoss remoting model does not currently allows this. We can either drive JBoss Remoting to support this model (may take some time) Or write out own connection functionality - this could be fairly straightforward if we use tools such as Apache MINA. This would also solve the problem of providing a functional and performant multiplex transport. Essentially we need a bidirectional channel between jms client and server. On either end bytes can be read or witten in a non blocking fashion. On top of that we can introduce simple framing in order to provide multiplex functionality. -- 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

15 years, 7 months

3
9
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-604) Duplicate message detection

by Tim Fox (JIRA)

Duplicate message detection --------------------------- Key: JBMESSAGING-604 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-604 Project: JBoss Messaging Issue Type: Feature Request Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Whereas JMS requires once and only once *delivery* of messages, there are no such guarantees when sending messages to a queue/durable sub. This can result in duplicate messages existing in a queue or durable sub. For some clients this is unacceptable, so we should implement a feature which alerts to the presence of duplicates. This can be done by keeping a persistent cache of message (or transaction) id on the server. Entries should time out after a period of time. This will not remove duplicates 100% of the time since we cannot cache the previous values of id for ever, but only for a window. See forum thread for more details -- 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

15 years, 7 months

3
8
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1302) supported-window-states ignored ? no limitation to normal window only.

by Antoine Herzog (JIRA)

supported-window-states ignored ? no limitation to normal window only. ---------------------------------------------------------------------- Key: JBPORTAL-1302 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1302 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.4.1 Final Environment: portal 2.4.1 Reporter: Antoine Herzog Assigned To: Julien Viet In the -object.xml file, remove all window-state elements, but the normal one. <supported-window-states> <window-state>normal</window-state>  </supported-window-states> It does not change anything The min/max icons are still displayed. . And you can still ask for the maximized or minimized state. no exception, the portal still works as usual (with the "classic" all three states enabled). Is it the portal core that should prevent to use these states, if not enabled ? Or the layout strategy and rendering that should not show the icons ? (but then, the portal should warn if we type an url that ask a state that is disabled... even it is not by clicking in the window icon). -- 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

15 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1052) When running stress tests wrong log4j.xml is picked up

by Tim Fox (JIRA)

When running stress tests wrong log4j.xml is picked up ------------------------------------------------------ Key: JBMESSAGING-1052 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1052 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.CR2 When running stress tests, the log4j.xml from tests/etc, but the log4j.xml from tests/etc/stress isn't being used. This means stress tests are being run on trace logging, which is incorrect (makes them take ages) -- 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

15 years, 8 months

2
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007