March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-429) Implement intelligent flow control

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-429?page=all ] Ovidiu Feodorov updated JBMESSAGING-429: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Implement intelligent flow control > ---------------------------------- > > Key: JBMESSAGING-429 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-429 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Fix For: Unscheduled > > > We should implement an intelligent flow control mechanism so message sending can be automatically throttled when consumers are slow to prevent messages bulding up on queues/subscriptions. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-353) ConnectionConsumerTest.testRedeliveryTransacted() fails on Mac OSX 10.4.6 but passes on Windows

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-353?page=all ] Ovidiu Feodorov updated JBMESSAGING-353: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > ConnectionConsumerTest.testRedeliveryTransacted() fails on Mac OSX 10.4.6 but passes on Windows > ----------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-353 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-353 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Facade, Tests and Performance > Affects Versions: 1.0.0, 1.0.1.CR1 > Environment: mac osx 10.4.6 > JDK 1.4.2_09 > JDK 1.5.0_04 > Reporter: Aaron Walker > Assigned To: Tim Fox > Fix For: Unscheduled > > Attachments: messaging-tests.trace.log > > Original Estimate: 3 days > Remaining Estimate: 3 days > > The testRedeliveryTransacted fail with the following: > 1) testRedeliveryTransacted(org.jboss.test.messaging.jms.ConnectionConsumerTest)junit.framework.AssertionFailedError: Didn't receive correct messages > at org.jboss.test.messaging.jms.ConnectionConsumerTest.testRedeliveryTransacted(ConnectionConsumerTest.java:224) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at org.jboss.test.messaging.tools.junit.SelectiveTestRunner.main(SelectiveTestRunner.java:58) > The issue revolves around the sess.rollback around line 433 in that after the rollback and the 3 messages get redelivered and on the 3rd message the following if (!tm.getJMSRedelivered()) at line 481 evaluates to true in that the getJMSRedelivered() is false when it should be true. By placing a 1ms sleep just prior to the rollback you can get the test to pass. So after my initial investigation It appears that it may be some sort of threading issue that shows up on my mac. > I will attached the TRACE log for this If you look at line 765 of the log it shows that the delivery count for the message is 0 when it should be 1 -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-217) DurableSubscription test should probe durable subscriptions instances for in-flight messages

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-217?page=all ] Ovidiu Feodorov updated JBMESSAGING-217: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > DurableSubscription test should probe durable subscriptions instances for in-flight messages > -------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-217 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-217 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Modify DurableSubscriptionTest.testDurableSubscriptionDifferentSelector() to look inside the durable subscription of in-flight messages when a durable subscription message count will be exposed and accessible via a JMX attribute, -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-170) JCA 1.5 Message Inflow

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-170?page=all ] Ovidiu Feodorov updated JBMESSAGING-170: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > JCA 1.5 Message Inflow > ---------------------- > > Key: JBMESSAGING-170 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-170 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Priority: Critical > Fix For: Unscheduled > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > See related task. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-374) AOP stack should be specifiable per connection factory

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-374?page=all ] Ovidiu Feodorov updated JBMESSAGING-374: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > AOP stack should be specifiable per connection factory > ------------------------------------------------------ > > Key: JBMESSAGING-374 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-374 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: Unscheduled > > Original Estimate: 3 days > Remaining Estimate: 3 days > > It should be possible to specifty the entire client and server aop stack configuration per connection factory -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-400) Usage of JBoss serialization should be configurable everywhere

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-400?page=all ] Ovidiu Feodorov updated JBMESSAGING-400: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Usage of JBoss serialization should be configurable everywhere > -------------------------------------------------------------- > > Key: JBMESSAGING-400 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-400 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: Unscheduled > > > There are a couple of places in the code (JDBCPersistenceManager and MessageSupport) where JBossObjectInput/Output Streams are being used directly. This should be made configurable -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-185) Run objectweb JMS tests in top of JBoss Messaging

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-185?page=all ] Ovidiu Feodorov updated JBMESSAGING-185: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Run objectweb JMS tests in top of JBoss Messaging > ------------------------------------------------- > > Key: JBMESSAGING-185 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-185 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: Richard Achmatowicz > Fix For: Unscheduled > > Original Estimate: 4 days > Remaining Estimate: 4 days > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-186) Get rid of all TODOs and FIXMEs from the code

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-186?page=all ] Ovidiu Feodorov updated JBMESSAGING-186: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Get rid of all TODOs and FIXMEs from the code > --------------------------------------------- > > Key: JBMESSAGING-186 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-186 > Project: JBoss Messaging > Issue Type: Task > Reporter: Ovidiu Feodorov > Fix For: Unscheduled > > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-25) Integrate ServerPeer with the 5.0 micro-container

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-25?page=all ] Ovidiu Feodorov updated JBMESSAGING-25: --------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Integrate ServerPeer with the 5.0 micro-container > ------------------------------------------------- > > Key: JBMESSAGING-25 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-25 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Critical > Fix For: Unscheduled > > Attachments: JBMESSAGING-26.tar > > Original Estimate: 1 week > Remaining Estimate: 1 week > > This is critical to kick start ESB -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-259) Activate compression in marshaller

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-259?page=all ] Ovidiu Feodorov updated JBMESSAGING-259: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Activate compression in marshaller > ---------------------------------- > > Key: JBMESSAGING-259 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-259 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: Unscheduled > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Activate compression in marshaller for messages > x bytes. Make it configurable -- 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, 1 month

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