July 2006 - jboss-jira - Jboss List Archives

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

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-229?page=all ] Ovidiu Feodorov reopened JBMESSAGING-229: ----------------------------------------- > 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, 12 months

1
0
0 / 0

[JBoss JIRA] Reopened: (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 reopened JBMESSAGING-255: ----------------------------------------- > 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 > > > 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, 12 months

1
0
0 / 0

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

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-247?page=all ] Ovidiu Feodorov reopened JBMESSAGING-247: ----------------------------------------- > 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 > > > 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, 12 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-240) Review reference counting in the database

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-240?page=all ] Ovidiu Feodorov reopened JBMESSAGING-240: ----------------------------------------- > Review reference counting in the database > ----------------------------------------- > > Key: JBMESSAGING-240 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-240 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Messaging Core Persistence > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Fix For: 1.2 > > > Review reference counting in the database (there is a race condition there), and also add a switch to avoid it for the non-distributed case (and avoid the performance hit) -- 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, 12 months

1
0
0 / 0

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

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-235?page=all ] Ovidiu Feodorov reopened JBMESSAGING-235: ----------------------------------------- > 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 > > > 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, 12 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-87) Light-weight JMS 1.1 / JGroups package

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-87?page=all ] Ovidiu Feodorov updated JBMESSAGING-87: --------------------------------------- Fix Version/s: 1.4 (was: 1.2) > 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 > Assigned To: Ovidiu Feodorov > Fix For: 1.4 > > > 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

19 years, 12 months

1
0
0 / 0

[JBoss JIRA] Reopened: (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 reopened JBMESSAGING-331: ----------------------------------------- > 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 > > > 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, 12 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-404) Remove Channel::deliver(Receiver r) method

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-404?page=all ] Ovidiu Feodorov updated JBMESSAGING-404: ---------------------------------------- Fix Version/s: 1.2.0.Alpha1 (was: 1.2) > Remove Channel::deliver(Receiver r) method > ------------------------------------------ > > Key: JBMESSAGING-404 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-404 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.Alpha1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > This method is used to effectively do a synchronous receive() on a channel. > The functionality could be more simply implemented by doing adding a MessageReference receive() method. > This would also help in a clustered environment since we would have one less network RPC. > Most of the complexity here is in updating tests. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-184) Transparent client fail-over

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-184?page=all ] Ovidiu Feodorov updated JBMESSAGING-184: ---------------------------------------- Fix Version/s: 1.2.0.Beta1 (was: 1.2.0.Alpha1) > Transparent client fail-over > ---------------------------- > > Key: JBMESSAGING-184 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-184 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Clustering > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: 1.2.0.Beta1 > > -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-2489) Creation of identical jar artifacts.

by Ruel Loehr (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2489?page=all ] Ruel Loehr closed JBAS-2489. ---------------------------- Resolution: Done This was done committed in jboss head. The 4.0 version uses the jboss-jmx-core jar by renaming it jboss-jmx.jar and placing it in ${install.client}. The jboss-jmx-core.jar is not identical to jboss-jmx.jar in branch_4_0. > Creation of identical jar artifacts. > ------------------------------------ > > Key: JBAS-2489 > URL: http://jira.jboss.com/jira/browse/JBAS-2489 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMX > Environment: WinXP > Reporter: Ruel Loehr > Assigned To: Ruel Loehr > Priority: Minor > Fix For: JBossAS-5.0.0.Beta > > > Building the jmx module produces 3 jar artifacts: > 1) jboss-jmx.jar > 2) jboss-jmx-core.jar > 3) jboss-jmx-testsuite > jboss-jmx.jar and jboss-jmx-core.jar are identical and only jboss-jmx.jar is used in the distribution. JBoss-jmx-core.jar seems to be a remnant from older days. Should it be 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

19 years, 12 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