March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBCACHE-996) Test failure - org.jboss.cache.multiplexer.BuddyGroupAssignmentTest

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-996?page=all ] Ryan Campbell updated JBCACHE-996: ---------------------------------- Fix Version/s: 2.0.0.BETA1 Affects Version/s: 2.0.0.BETA1 > Test failure - org.jboss.cache.multiplexer.BuddyGroupAssignmentTest > ------------------------------------------------------------------- > > Key: JBCACHE-996 > URL: http://jira.jboss.com/jira/browse/JBCACHE-996 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.BETA1 > Reporter: Rajesh Rajasekaran > Fix For: 2.0.0.BETA1 > > > org.jboss.cache.multiplexer.BuddyGroupAssignmentTest fails on the release distribution. > To reproduce: > run ./build.sh dist. > Unzip JBossCache-all-2.0.0.BETA1.zip > Run ant one.test -Dtest=org.jboss.cache.multiplexer.BuddyGroupAssignmentTest > <testcase classname="org.jboss.cache.multiplexer.BuddyGroupAssignmentTest" name="testRemovalFromCluster2Buddies" time="24.523"> > <failure message="10.16.7.254:60612 should be a buddy to 10.16.7.254:60606" type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError: 10.16.7.254:60612 should be a buddy to 10.16.7.254:60606 > at org.jboss.cache.buddyreplication.BuddyReplicationTestsBase.assertIsBuddy(BuddyReplicationTestsBase.java:285) > at org.jboss.cache.buddyreplication.BuddyGroupAssignmentTest.testRemovalFromCluster2Buddies(BuddyGroupAssignmentTest.java:131) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > </failure> -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBCACHE-996) Test failure - org.jboss.cache.multiplexer.BuddyGroupAssignmentTest

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-996?page=all ] Ryan Campbell reassigned JBCACHE-996: ------------------------------------- Assignee: Manik Surtani > Test failure - org.jboss.cache.multiplexer.BuddyGroupAssignmentTest > ------------------------------------------------------------------- > > Key: JBCACHE-996 > URL: http://jira.jboss.com/jira/browse/JBCACHE-996 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.BETA1 > Reporter: Rajesh Rajasekaran > Assigned To: Manik Surtani > Fix For: 2.0.0.BETA1 > > > org.jboss.cache.multiplexer.BuddyGroupAssignmentTest fails on the release distribution. > To reproduce: > run ./build.sh dist. > Unzip JBossCache-all-2.0.0.BETA1.zip > Run ant one.test -Dtest=org.jboss.cache.multiplexer.BuddyGroupAssignmentTest > <testcase classname="org.jboss.cache.multiplexer.BuddyGroupAssignmentTest" name="testRemovalFromCluster2Buddies" time="24.523"> > <failure message="10.16.7.254:60612 should be a buddy to 10.16.7.254:60606" type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError: 10.16.7.254:60612 should be a buddy to 10.16.7.254:60606 > at org.jboss.cache.buddyreplication.BuddyReplicationTestsBase.assertIsBuddy(BuddyReplicationTestsBase.java:285) > at org.jboss.cache.buddyreplication.BuddyGroupAssignmentTest.testRemovalFromCluster2Buddies(BuddyGroupAssignmentTest.java:131) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > </failure> -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBCACHE-996) Test failure - org.jboss.cache.multiplexer.BuddyGroupAssignmentTest

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-996?page=all ] Ryan Campbell moved JBQA-705 to JBCACHE-996: -------------------------------------------- Project: JBoss Cache (was: JBoss QA) Key: JBCACHE-996 (was: JBQA-705) > Test failure - org.jboss.cache.multiplexer.BuddyGroupAssignmentTest > ------------------------------------------------------------------- > > Key: JBCACHE-996 > URL: http://jira.jboss.com/jira/browse/JBCACHE-996 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Rajesh Rajasekaran > > org.jboss.cache.multiplexer.BuddyGroupAssignmentTest fails on the release distribution. > To reproduce: > run ./build.sh dist. > Unzip JBossCache-all-2.0.0.BETA1.zip > Run ant one.test -Dtest=org.jboss.cache.multiplexer.BuddyGroupAssignmentTest > <testcase classname="org.jboss.cache.multiplexer.BuddyGroupAssignmentTest" name="testRemovalFromCluster2Buddies" time="24.523"> > <failure message="10.16.7.254:60612 should be a buddy to 10.16.7.254:60606" type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError: 10.16.7.254:60612 should be a buddy to 10.16.7.254:60606 > at org.jboss.cache.buddyreplication.BuddyReplicationTestsBase.assertIsBuddy(BuddyReplicationTestsBase.java:285) > at org.jboss.cache.buddyreplication.BuddyGroupAssignmentTest.testRemovalFromCluster2Buddies(BuddyGroupAssignmentTest.java:131) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > </failure> -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4170) Background validation for JCA connection pools incorrectly returns destroyed connection

by Weston Price (JIRA)

Background validation for JCA connection pools incorrectly returns destroyed connection --------------------------------------------------------------------------------------- Key: JBAS-4170 URL: http://jira.jboss.com/jira/browse/JBAS-4170 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-5.0.0.Beta1, JBossAS-4.2.0.GA Reporter: Weston Price Assigned To: Weston Price Fix For: JBossAS-4.2.0.GA The background validation process incorrectly returns the connection listener even when the listener has failed validation. While this does not prevent the validation from working, it is an incorrect use of resources. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4159) Create the release notes for 4.2.0.CR1

by Dimitris Andreadis (JIRA)

Create the release notes for 4.2.0.CR1 -------------------------------------- Key: JBAS-4159 URL: http://jira.jboss.com/jira/browse/JBAS-4159 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Priority: Critical Fix For: JBossAS-4.2.0.CR1 It's a dirty job, but someone needs to do 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

19 years, 2 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBPM-152) ejb (SLSB) command based session facade interface

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-152?page=all ] Tom Baeyens closed JBPM-152. ---------------------------- Resolution: Done > ejb (SLSB) command based session facade interface > ------------------------------------------------- > > Key: JBPM-152 > URL: http://jira.jboss.com/jira/browse/JBPM-152 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2 > > > create an ejb interface to the jbpm apis as a stateless session bean. > the interface should have one method, to provide a Signal. > maybe we should create a stateless session bean for each of the module sessions. but then we still need to figure out a solution on what part of the graph the client wants to get... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-609) create command based session facade

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-609?page=all ] Tom Baeyens closed JBPM-609. ---------------------------- Resolution: Done > create command based session facade > ----------------------------------- > > Key: JBPM-609 > URL: http://jira.jboss.com/jira/browse/JBPM-609 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2 > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-569) improve EL expression examples in the user guide

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-569?page=all ] Tom Baeyens updated JBPM-569: ----------------------------- Fix Version/s: jBPM jPDL 3.2.1 (was: jBPM jPDL 3.2) postponed > improve EL expression examples in the user guide > ------------------------------------------------ > > Key: JBPM-569 > URL: http://jira.jboss.com/jira/browse/JBPM-569 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-539) events on cancel, suspend, resume

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-539?page=all ] Tom Baeyens updated JBPM-539: ----------------------------- Fix Version/s: jBPM jPDL 3.2.1 (was: jBPM jPDL 3.2) suspended... euh, i mean postponed > events on cancel, suspend, resume > --------------------------------- > > Key: JBPM-539 > URL: http://jira.jboss.com/jira/browse/JBPM-539 > Project: JBoss jBPM > Issue Type: Feature Request > Reporter: James Depoorter > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.1 > > > Events on cancel, suspend and resume should be available. > Preferably a "beforeXYZ" and "afterXYZ" -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4168) ejb2 sfsb passivate directory inconsistencies

by Galder Zamarreno (JIRA)

ejb2 sfsb passivate directory inconsistencies --------------------------------------------- Key: JBAS-4168 URL: http://jira.jboss.com/jira/browse/JBAS-4168 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.2.0.CR1 Reporter: Galder Zamarreno Assigned To: Scott M Stark Priority: Minor StatefulSessionFilePersistenceManager's javadoc says that passivated beans are stored in: jboss-server-data-dir/storeDirectoryName/ejb-name-unique-id However, the code actually stores them in the tmp directory: // Get the system data directory File dir = ServerConfigLocator.locate().getServerTempDir(); ServerConfigLocator.locate().getServerTempDir() points to ServerConfig.SERVER_TEMP_DIR jboss.server.temp.dir. So, the javadoc and the code are insconsistent and secondly, EJB3 SFSB cache is configured to store beans in jboss.server.data.dir via the cache loader, at least in each JBossCache managed version. The simple cache set up in EJB3 shows the same incosistency as in EJB2's StatefulSessionFilePersistenceManager. I'll create a separate JIRA for it if this one gets approved I believe we should store the beans in the same place. I can't see a reason not to do so. -- 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, 2 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 March 2007