December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Assigned: (JBMESSAGING-287) RemotingTest.testConnectionListener() invalid

by Juha Lindfors (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-287?page=all ] Juha Lindfors reassigned JBMESSAGING-287: ----------------------------------------- Assignee: Juha Lindfors (was: Ovidiu Feodorov) > RemotingTest.testConnectionListener() invalid > --------------------------------------------- > > Key: JBMESSAGING-287 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-287 > Project: JBoss Messaging > Issue Type: Bug > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: Juha Lindfors > Priority: Minor > Fix For: 1.0.2.CR1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I commented out that test because I wanted a clean test run for the release and also because I think the test is invalid. > After the client connects I assume there is a separate thread that renews the lease on server, so even if the main thread sleeps for 5 secs, the client renews its lease and the ConnectionListener doesn't get called. Please verify my assumption and either fix the test or remove 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

17 years, 9 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBMESSAGING-355) Remove possibility of delivery race conditions

by Juha Lindfors (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-355?page=all ] Juha Lindfors reassigned JBMESSAGING-355: ----------------------------------------- Assignee: Juha Lindfors (was: Tim Fox) > Remove possibility of delivery race conditions > ---------------------------------------------- > > Key: JBMESSAGING-355 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-355 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Juha Lindfors > Fix For: 1.0.2.CR1 > > Attachments: race-condition.log > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently race conditions can occur on message delivery where the delivery is acknowledged or cancelled before the call to handle has returned. > In ChannelState we defensively program against this by synchronizing on the returned delivery and by dealing with the situation where the delivery does not exist in the channel state and ignoring. > See ChannelSupport::deliver() and ChannelState.cancelDelivery. > This approach has the following problems: > Complexity of code to maintain and understand. > Where acks return quickly we are likely to get contention on the lock in ChannelSupport::deliver, thus reducing throughput. > A much simpler solution enables us to remove the possibility of such race conditions and remove the corresponding lock contention. > This can be done by adding a confirm() method on Delivery. > When the receiver receives the message in it's handle() call, before dispatching the message it calls Delivery::confirm. This results in the channel adding the delivery to the channel state. Thus we can be assured that the delivery exists before any acknowledgment or cancellation comes in. > This is a very simple change. -- 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

17 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-125) Ambiguity on setters

by Adrian Brock (JIRA)

Ambiguity on setters -------------------- Key: JBMICROCONT-125 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-125 Project: JBoss MicroContainer Issue Type: Task Components: BeanInfo Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock There is an ambiguity when it comes to javabeans with only setters, e.g. setSomething(Integer); setSomething(String); Currently, the implementation cannot use the getter to decide which is the correct setter. Instead it says that 'something" is not a property if there are multiple setters. Maybe this can be relaxed and we let the Configurator pick which one based upon what users decides to use? -- 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

17 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-670) Redirection of connection if server is not failover server

by Ovidiu Feodorov (JIRA)

Redirection of connection if server is not failover server ---------------------------------------------------------- Key: JBMESSAGING-670 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-670 Project: JBoss Messaging Issue Type: Sub-task Components: JMS Clustering Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta1 Redirection of connection if server is not failover server. Needs to cope with multiple hops. -- 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

17 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-516) Clustering

by Tim Fox (JIRA)

Clustering ---------- Key: JBMESSAGING-516 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-516 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Beta1 Implement clustering as described in: http://wiki.jboss.org/wiki/Wiki.jsp?page=NewClusteringDesign -- 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

17 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-615) Add sufficient tracing for a customer environment

by Tim Fox (JIRA)

Add sufficient tracing for a customer environment ------------------------------------------------- Key: JBMESSAGING-615 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-615 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Fix For: 1.2.0.Beta1 Ensure there is sufficient logging at trace level to ensure problems in a customer environment can be diagnosed. -- 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

17 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-519) Transparent failover / HA

by Tim Fox (JIRA)

Transparent failover / HA ------------------------- Key: JBMESSAGING-519 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-519 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox -- 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

17 years, 9 months

3
11
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-671) Recreate delivery list on the server when failure occurs

by Ovidiu Feodorov (JIRA)

Recreate delivery list on the server when failure occurs -------------------------------------------------------- Key: JBMESSAGING-671 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-671 Project: JBoss Messaging Issue Type: Sub-task Components: JMS Clustering Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Critical 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

17 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-685) session.commit on an empty transaction causes NPE

by Clebert Suconic (JIRA)

session.commit on an empty transaction causes NPE ------------------------------------------------- Key: JBMESSAGING-685 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-685 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Beta1 Reporter: Clebert Suconic Assigned To: Clebert Suconic Priority: Blocker Fix For: 1.2.0.Beta1 this will cause a NPE: JBossConnectionFactory factory = (JBossConnectionFactory) ic[1].lookup("/ConnectionFactory"); Connection conn = cf.createConnection(); JBossSession session = (JBossSession) conn.createSession(true, Session.SESSION_TRANSACTED); session.commit(); [junit] java.lang.NullPointerException [junit] at org.jboss.jms.tx.ClientTransaction.clearMessages(ClientTransaction.java:116) [junit] at org.jboss.jms.tx.ResourceManager.rollbackLocal(ResourceManager.java:230) [junit] at org.jboss.jms.tx.ResourceManager.commitLocal(ResourceManager.java:208) [junit] at org.jboss.jms.client.container.TransactionAspect.handleCommit(TransactionAspect.java:106) [junit] at org.jboss.aop.advice.org.jboss.jms.client.container.TransactionAspect14.invoke(TransactionAspect14.java) [junit] at org.jboss.jms.client.delegate.ClientSessionDelegate$commit_8461082169793485964.invokeNext(ClientSessionDelegate$commit_8461082169793485964.java) [junit] at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:177) [junit] at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:117) [junit] at org.jboss.jms.client.delegate.ClientSessionDelegate$commit_8461082169793485964.invokeNext(ClientSessionDelegate$commit_8461082169793485964.java) [junit] at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:69) [junit] at org.jboss.jms.client.delegate.ClientSessionDelegate$commit_8461082169793485964.invokeNext(ClientSessionDelegate$commit_8461082169793485964.java) [junit] at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107) [junit] at org.jboss.jms.client.delegate.ClientSessionDelegate$commit_8461082169793485964.invokeNext(ClientSessionDelegate$commit_8461082169793485964.java) [junit] at org.jboss.jms.client.delegate.ClientSessionDelegate.commit(ClientSessionDelegate.java) [junit] at org.jboss.jms.client.JBossSession.commit(JBossSession.java:165) [junit] at org.jboss.test.messaging.jms.clustering.HATest.testEmptyCommit(HATest.java:96) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] at java.lang.reflect.Method.invoke(Method.java:585) [junit] at junit.framework.TestCase.runTest(TestCase.java:154) [junit] at junit.framework.TestCase.runBare(TestCase.java:127) [junit] at junit.framework.TestResult$1.protect(TestResult.java:106) [junit] at junit.framework.TestResult.runProtected(TestResult.java:124) [junit] at junit.framework.TestResult.run(TestResult.java:109) [junit] at junit.framework.TestCase.run(TestCase.java:118) [junit] at junit.framework.TestSuite.runTest(TestSuite.java:208) [junit] at junit.framework.TestSuite.run(TestSuite.java:203) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:672) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:567) -- 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

17 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-687) Fix clone on HAAspect::performClientSideFailover

by Clebert Suconic (JIRA)

Fix clone on HAAspect::performClientSideFailover ------------------------------------------------ Key: JBMESSAGING-687 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-687 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Beta1 Reporter: Clebert Suconic Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta1 HAAspect::performClientSideFailover is cloning state.children because we are using the oldSession to create new objects. We should use newSession to create failedOver objects. This issue is somehow related to JBMESSAGING-686, as this will lead to faiilures when closing the connection. -- 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

17 years, 9 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2006