February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Reopened: (JBMESSAGING-268) Convert destinations to ints in message instance

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-268?page=all ] Ovidiu Feodorov reopened JBMESSAGING-268: ----------------------------------------- > Convert destinations to ints in message instance > ------------------------------------------------ > > Key: JBMESSAGING-268 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-268 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Destination implementations JBossQueue and JBossTopic are currently not much more than just Strings identifiers. > When sending a message the destination (and possibly the replyto) need to be serialized with the message. > If the Destinations are just identifiers then they could represented as ints making there less bytes to serialize. > This could be significant for destinations with long names, e.g. 100 bytes -> 4 bytes (per message) -- 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] Reopened: (JBMESSAGING-246) Optimise browsing

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-246?page=all ] Ovidiu Feodorov reopened JBMESSAGING-246: ----------------------------------------- > Optimise browsing > ----------------- > > Key: JBMESSAGING-246 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-246 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Currently browsing is inefficient and copies the entire set of message references. Instead we should use the deque iterator + the deliveries iterator. > We should also investigate activating the browsing interceptor to batch messages. -- 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] Reopened: (JBMESSAGING-162) Consider implementing different message delivery optimisations

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-162?page=all ] Ovidiu Feodorov reopened JBMESSAGING-162: ----------------------------------------- > Consider implementing different message delivery optimisations > -------------------------------------------------------------- > > Key: JBMESSAGING-162 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-162 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Facade > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Minor > Fix For: 1.2.1 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Consideri implementing different different message delivery optimisations. > e.g. client side buffering > multicast (both reliable and unreliable) > these could be selected by using special, jboss specific ack modes -- 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-851) Issue with remoting MAX_RETRIES

by Tim Fox (JIRA)

Issue with remoting MAX_RETRIES ------------------------------- Key: JBMESSAGING-851 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-851 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Ron Sigal Fix For: 1.0.1.SP5, 1.2.1 Currently remoting socket/bisocket transport MAX_RETRIES attribute is non configurable via the xml remoting config. This means if a client is making a lot of concurrent invocations and they take some significant time to execute then, the client invocations may timeout and throw an exception back to the client, since they have waited longer than 30 seconds (MAX_RETRIES * 1000 ms) to obtain a connection from the pool. This may be unacceptable to the client who is quite happy to wait an indefinite period (or at least a period longer than 30 seconds) to obtain a connection. MAX_RETIES (currently hardcoded to 30) needs to be configurable via the xml config. Also the sleep interval (currently 1000 ms) needs to be made configurable too. See forum thread for a real world example of this problem. -- 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

2
9
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-286) I am able to create two different durable subscriptions with same name using the same client ID on the same topic

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-286?page=all ] Ovidiu Feodorov closed JBMESSAGING-286. --------------------------------------- Fix Version/s: 1.2.0.GA (was: 1.2.1) Resolution: Done Consolidating 1.2.0.GA > I am able to create two different durable subscriptions with same name using the same client ID on the same topic > ----------------------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-286 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-286 > Project: JBoss Messaging > Issue Type: Bug > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Fix For: 1.2.0.GA > > Original Estimate: 1 day > Remaining Estimate: 1 day > > add test 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

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-266) Remove Routable

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-266?page=all ] Ovidiu Feodorov closed JBMESSAGING-266. --------------------------------------- Fix Version/s: 1.2.0.GA (was: 1.2.1) Resolution: Done Consolidating 1.2.0.GA > Remove Routable > --------------- > > Key: JBMESSAGING-266 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-266 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Critical > Fix For: 1.2.0.GA > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Remove Routable interface. > Have interface MessageReference which represents things that can be routed. > Have interface Payload (TBD) which every MessageReference has, this contains data that is not necessarty for routing. > We would then have a subclass of Payload called JMSPayload which contains all the jms stuff,not needed for routing. > A jms message would extend Message Reference and contain fields such as delivery count. > The jms message would contain a Payload interface and delegate for that for other attributes -- 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] Reopened: (JBMESSAGING-286) I am able to create two different durable subscriptions with same name using the same client ID on the same topic

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-286?page=all ] Ovidiu Feodorov reopened JBMESSAGING-286: ----------------------------------------- > I am able to create two different durable subscriptions with same name using the same client ID on the same topic > ----------------------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-286 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-286 > Project: JBoss Messaging > Issue Type: Bug > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Fix For: 1.2.0.GA > > Original Estimate: 1 day > Remaining Estimate: 1 day > > add test 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

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-266) Remove Routable

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-266?page=all ] Ovidiu Feodorov reopened JBMESSAGING-266: ----------------------------------------- > Remove Routable > --------------- > > Key: JBMESSAGING-266 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-266 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Critical > Fix For: 1.2.0.GA > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Remove Routable interface. > Have interface MessageReference which represents things that can be routed. > Have interface Payload (TBD) which every MessageReference has, this contains data that is not necessarty for routing. > We would then have a subclass of Payload called JMSPayload which contains all the jms stuff,not needed for routing. > A jms message would extend Message Reference and contain fields such as delivery count. > The jms message would contain a Payload interface and delegate for that for other attributes -- 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: (JBAS-3900) Get the 4.0-compatibility tests passing

by Dimitris Andreadis (JIRA)

Get the 4.0-compatibility tests passing --------------------------------------- Key: JBAS-3900 URL: http://jira.jboss.com/jira/browse/JBAS-3900 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR1 -- 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

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-900) Decide on ClusteredConnectionFactoryTest.testGetAOPBounce()

by Ovidiu Feodorov (JIRA)

Decide on ClusteredConnectionFactoryTest.testGetAOPBounce() ----------------------------------------------------------- Key: JBMESSAGING-900 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-900 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Clebert Suconic Fix For: 1.2.0.GA Decide whether ClusteredConnectionFactoryTest.testGetAOPBounce() (currently commented out) is semantically correct. If it is, make sure it passes. If not, delete it. -- 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

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