August 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9434) org.jboss.test.ejb3.singleton.unit.SingletonUnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.ejb3.singleton.unit.SingletonUnitTestCase -------------------------------------------------------- Key: JBAS-9434 URL: https://issues.jboss.org/browse/JBAS-9434 Project: Legacy JBoss Application Server 6 Issue Type: Sub-task Security Level: Public (Everyone can see) Components: EJB Reporter: Shelly McGowan Assignee: jaikiran pai Fix For: 6.1.0 DEPLOYMENTS IN ERROR: Deployment "vfs:///NotBackedUp/TRUNK/trunk/testsuite/output/lib/ejb31singleton.jar" is in error due to the following reason(s): java.lang.RuntimeException: Specified reference [EJB Reference: beanInterface 'org.jboss.test.ejb3.singleton.startup.DoSomethingView', beanName 'null', mappedName 'null', lookupName 'null', owning unit 'ComponentDeploymentContext(a)1968371370{org.jboss.metadata.ejb.jboss.JBossEnterpriseBeanMetaData.SingletonB}'] was matched by more than one EJB: [org.jboss.metadata.ejb.jboss.JBossSessionBean31MetaData@ad066ec4{SLSBTwo}, org.jboss.metadata.ejb.jboss.JBossSessionBean31MetaData@ad065ade{SLSBOne}]. Specify beanName explciitly or ensure beanInterface is unique. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1894) Transaction Rollback during client failover may cause duplicated message

by Yong Hao Gao (JIRA)

Transaction Rollback during client failover may cause duplicated message ------------------------------------------------------------------------ Key: JBMESSAGING-1894 URL: https://issues.jboss.org/browse/JBMESSAGING-1894 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.4.8.SP2, 1.4.0.SP3.CP14 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP15, 1.4.8.SP3 The following scenario shows how a duplicated message is produced: 1. A cluster of two nodes, node 1 and node 2, is up and running. 2. a message is delivered from node 1 to a consumer who receives it in a transaction. 3. for some reason the transaction is rolled back, in which the transaction is first removed from the resource manager and then redelivers the message. 4. At the same time failover happens (node 1 dead), in which it will collect the ACK list from resource manager and recover them to the new node (node 2). 5. because lack of synchronization, if in step 3 after the tx is removed and the message is re-delivered (locally) to the consumer, but before the tx is committed, the fail over happens and it won't get the message's ACK info ('cos the tx has been removed already) and the message will be failed over to node 2 and redelivered. 6. So with the successful commit of the tx, the same message is delivered twice. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
5
0 / 0

[JBoss JIRA] Created: (JBAS-8739) org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase ---------------------------------------------------------- Key: JBAS-8739 URL: https://issues.jboss.org/browse/JBAS-8739 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan Assignee: Andrew Rubinger Fix For: 6.0.0.Final All tests failing: testEarManagedComponentNames testMdb testSfsb testSlsb testSlsbLocal with: Component not found; no managed object with name "testEjb3xMetrics.jar/BEAN" in: [] Stacktrace junit.framework.AssertionFailedError: Component not found; no managed object with name "testEjb3xMetrics.jar/SLSB" in: [] at org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase.getAndTestManagedComponent(Ejb3MetricsUnitTestCase.java:453) at org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase.testSlsb(Ejb3MetricsUnitTestCase.java:255) These tests were passing with EJB 3 depchain 1.0.0-alpha-32 and failing with 1.0.0-alpha-34 (do not have results of these tests with 1.0.0-alpha-33) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-8245) Fix org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase

by Brian Stansberry (JIRA)

Fix org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase -------------------------------------------------------------- Key: JBAS-8245 URL: https://jira.jboss.org/browse/JBAS-8245 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: EJB3, Test Suite Reporter: Brian Stansberry Fix For: 6.0.0.Final http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-test... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

5
10
0 / 0

[JBoss JIRA] Created: (JBAS-8834) org.jboss.test.web.test.Enc*UnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.web.test.Enc*UnitTestCase ---------------------------------------- Key: JBAS-8834 URL: https://issues.jboss.org/browse/JBAS-8834 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan Assignee: Shelly McGowan org.jboss.test.web.test.EncXmlUnitTestCase.testAltRequestInfoServlet org.jboss.test.web.test.EncAnnotationsUnitTestCase.testAltRequestInfoServlet java.io.IOException: Expected reply code:200, actual=500 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-8835) org.jboss.test.web.test.NamingServletUnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.web.test.NamingServletUnitTestCase ------------------------------------------------- Key: JBAS-8835 URL: https://issues.jboss.org/browse/JBAS-8835 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 6.0.1 org.jboss.test.web.test.NamingServletUnitTestCase.testAppContextRoot org.jboss.test.web.test.NamingServletUnitTestCase.testGlobalContextRoot junit.framework.AssertionFailedError: FIXME: don't know what to expect naming!ROOT not bound -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8821) org.jboss.test.ejb3.async.test.AsyncSessionBeanUnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.ejb3.async.test.AsyncSessionBeanUnitTestCase ----------------------------------------------------------- Key: JBAS-8821 URL: https://issues.jboss.org/browse/JBAS-8821 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: EJB3 Reporter: Shelly McGowan Assignee: Andrew Rubinger Fix For: TBD-6.x testLocalRemote: junit.framework.AssertionFailedError: Remote async call should be able to be cancelled testLocalCancel: junit.framework.AssertionFailedError: Local async call should be able to be cancelled -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-3149) ObjectTypeNodes are not handled correctly during Marshalling

by Mark Proctor (JIRA)

ObjectTypeNodes are not handled correctly during Marshalling ------------------------------------------------------------ Key: JBRULES-3149 URL: https://issues.jboss.org/browse/JBRULES-3149 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.2.0.Final Reporter: Mark Proctor Assignee: Mark Proctor Fix For: 5.3.0.Beta1 The OTN's are not handled correctly in marshalling. This is where the facthandles are added back into the OTN directly, it doesn't obey all interfaces and super classes. This is fixed in 5.3, but it'll need to be manuall backported to 5.2.x. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-3101) Right Input triggering doesn't work for Queries

by Mark Proctor (JIRA)

Right Input triggering doesn't work for Queries ----------------------------------------------- Key: JBRULES-3101 URL: https://issues.jboss.org/browse/JBRULES-3101 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.2.0.Final Reporter: Mark Proctor Assignee: Mark Proctor Fix For: 5.3.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-3090) Use Stack Queues for Backward Chaining to avoid blow the method stack

by Mark Proctor (JIRA)

Use Stack Queues for Backward Chaining to avoid blow the method stack --------------------------------------------------------------------- Key: JBRULES-3090 URL: https://issues.jboss.org/browse/JBRULES-3090 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 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 August 2011