July 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-331) Message id generator and resource manager Memory leak

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-331?page=all ] Ovidiu Feodorov updated JBMESSAGING-331: ---------------------------------------- Fix Version/s: 1.2.0.Alpha1 (was: 1.2) > Message id generator and resource manager Memory leak > ----------------------------------------------------- > > Key: JBMESSAGING-331 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-331 > Project: JBoss Messaging > Issue Type: Bug > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.Alpha1 > > > Entries are not removed from the MessageIDGeneratorFactory or ResourceManmagerFactory when there are no more connections using it. > This is leak is very small, only one entry leaks per unique server the jms client connects to, but we should address it nevertheless -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-247) Race condition - out of order delivery

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-247?page=all ] Ovidiu Feodorov updated JBMESSAGING-247: ---------------------------------------- Fix Version/s: 1.2.0.Alpha1 (was: 1.2) > Race condition - out of order delivery > -------------------------------------- > > Key: JBMESSAGING-247 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-247 > Project: JBoss Messaging > Issue Type: Bug > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.Alpha1 > > > This race condition has never actually been observed, but should be possible: > Out of sequence cancel. > Consider the following. > 1. client does a recieve(1000). > 2. This causes serverconsumerdelegate.activate() to be called. > 3. The client times out. > 4. The serverconsumerdelegate accepts a message and sends it asynch to the client consumer. > 5. serverconsumerdelegate.deactive() is called (too late though) > 6. The message arrives at the messagecallbackhandler > 7. The message is not accepted since the consumer is not receiving > 8. ServerConsumerdelegate.cancel() is called. > 9. client does another receive(1000) > 10. This causes serverconsumerdelegate.activate() to be called. > 11. A message is accepted and sent asynch to the client. > 12. The cancel is processed. And the message put back on the queue > 13. Wrong message is received at client!! > Race condition in asynchronous cancelling of message: > If consumer is waiting on receive(timeout) then times out, then just after that a message is received, it gets cancelled. > But the cancellation could happen *after* the next receive occurs giving messages out of sequence. > Solution to this is as follows: > If a message arrives late, instead of cancelling then asynchonrously, a flag is set and the message id of the missed message is recorded > in the message callback handler, then when the next receive occurs, this flag is checked and if true, then a cancel is done *before* > the next receive. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-227) Complete extension of smoke test to deploy/test non-scoped Messaging with JBoss 5.0

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-227?page=all ] Ovidiu Feodorov updated JBMESSAGING-227: ---------------------------------------- Fix Version/s: 1.2.0.Alpha1 (was: 1.2) > Complete extension of smoke test to deploy/test non-scoped Messaging with JBoss 5.0 > ----------------------------------------------------------------------------------- > > Key: JBMESSAGING-227 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-227 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Fix For: 1.2.0.Alpha1 > > > The current smoke test deploys and test a scoped sar with JBoss 4. > Some support exists to deploy and test an un-scoped sar with JBoss 5. > Complete JBoss 5.0 smoke test support so the test will deploy/test Messaging on JBoss 4 and JBoss 5 in the same run. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-229) Peristence Optimizations

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-229?page=all ] Ovidiu Feodorov updated JBMESSAGING-229: ---------------------------------------- Fix Version/s: 1.2.0.Alpha1 (was: 1.2) > Peristence Optimizations > ------------------------ > > Key: JBMESSAGING-229 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-229 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core Persistence > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Priority: Critical > Fix For: 1.2.0.Alpha1 > > > Various persistence optimizations. See subtasks for more details. > Moved to 1.2 since all the tasks for 1.0 are now 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-255) Change signature of core interfaces to deal with MessageReferences only

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-255?page=all ] Ovidiu Feodorov updated JBMESSAGING-255: ---------------------------------------- Fix Version/s: 1.2.0.Alpha1 (was: 1.2) > Change signature of core interfaces to deal with MessageReferences only > ----------------------------------------------------------------------- > > Key: JBMESSAGING-255 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-255 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Fix For: 1.2.0.Alpha1 > > > The core only really deals with refs now, not routables. We should change the signatiures of Receiver.handle (and distributor?) to handle message references not routables -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-235) Make use of the datasource mappings

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-235?page=all ] Ovidiu Feodorov updated JBMESSAGING-235: ---------------------------------------- Fix Version/s: 1.2.0.Alpha1 (was: 1.2) > Make use of the datasource mappings > ----------------------------------- > > Key: JBMESSAGING-235 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-235 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Messaging Core Persistence > Reporter: Ovidiu Feodorov > Fix For: 1.2.0.Alpha1 > > > Make use of the datasource mappings - similar what has been done for the EJB timer -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-139) Consider whether core can be refactored to remove concept of delivery

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-139?page=all ] Ovidiu Feodorov updated JBMESSAGING-139: ---------------------------------------- Fix Version/s: 1.2.0.Alpha1 (was: 1.2) > Consider whether core can be refactored to remove concept of delivery > --------------------------------------------------------------------- > > Key: JBMESSAGING-139 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-139 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Blocker > Fix For: 1.2.0.Alpha1 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-139) Consider whether core can be refactored to remove concept of delivery

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-139?page=all ] Ovidiu Feodorov reopened JBMESSAGING-139: ----------------------------------------- > Consider whether core can be refactored to remove concept of delivery > --------------------------------------------------------------------- > > Key: JBMESSAGING-139 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-139 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Blocker > Fix For: 1.2.0.Alpha1 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-227) Complete extension of smoke test to deploy/test non-scoped Messaging with JBoss 5.0

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-227?page=all ] Ovidiu Feodorov reopened JBMESSAGING-227: ----------------------------------------- > Complete extension of smoke test to deploy/test non-scoped Messaging with JBoss 5.0 > ----------------------------------------------------------------------------------- > > Key: JBMESSAGING-227 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-227 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Fix For: 1.2.0.Alpha1 > > > The current smoke test deploys and test a scoped sar with JBoss 4. > Some support exists to deploy and test an un-scoped sar with JBoss 5. > Complete JBoss 5.0 smoke test support so the test will deploy/test Messaging on JBoss 4 and JBoss 5 in the same run. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-171) Remoting timeouts

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-171?page=all ] Ovidiu Feodorov reopened JBMESSAGING-171: ----------------------------------------- > Remoting timeouts > ----------------- > > Key: JBMESSAGING-171 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-171 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Remoting > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.Alpha1 > > > Currently we are using the default remoting timeouts on our connections from client to server (and server to client for callbacks but this will disappear). > This means they timeout if idle after 30 seconds (or is it 60 seconds?). > We need to set the timeout to a more appropriate default value when used in jms. > Suggestion, default timeout to 0 (i.e. it doesn't timeout) unless overriden by config setting. > When a connection does timeout, we need to gracefully clean up. -- 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, 10 months

1
0
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 July 2006