January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1399) Redirect needed for www.drools.org

by Bruce Mitchener (JIRA)

Redirect needed for www.drools.org ---------------------------------- Key: JBRULES-1399 URL: http://jira.jboss.com/jira/browse/JBRULES-1399 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Bruce Mitchener Priority: Minor Right now, going to http://drools.org/ redirects you to the JBoss site, which is nice. It would be really nice if http://www.drools.org/ also redirected you to the JBoss site. -- 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

18 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1234) "mvn -Psolver clean install" results in 77 test errors. However, skipping tests apparently does result in a functional solver build.

by Martin S (JIRA)

"mvn -Psolver clean install" results in 77 test errors. However, skipping tests apparently does result in a functional solver build. ------------------------------------------------------------------------------------------------------------------------------------ Key: JBRULES-1234 URL: http://jira.jboss.com/jira/browse/JBRULES-1234 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Solver Affects Versions: 4.0.2 Environment: I am using maven 2.0.7, Java 1.6.0_02 on a single core XP3000+ Ubuntu Feisty Linux machine with 2GB of RAM. Reporter: Martin S Assigned To: Mark Proctor "mvn -Psolver clean install" results in 77 test errors. However, skipping tests (mvn clean install -Psolver -Dmaven.test.skip) apparently does result in a functional solver build and seemingly working demos. To produce the test failures I Checked out version Checked out revision 15451 by: "svn checkout http://anonsvn.labs.jboss.com/labs/jbossrules/trunk/ drools" Then I attempted a build by: "mvn -Psolver clean install", resulting in: Tests run: 17, Failures: 0, Errors: 17, Skipped: 0, Time elapsed: 81.56 sec <<< FAILURE! Results : Tests in error: testListPackages(org.drools.repository.PackageItemTest) testRulePackageItem(org.drools.repository.PackageItemTest) testPackageCopy(org.drools.repository.PackageItemTest) testPackageSnapshot(org.drools.repository.PackageItemTest) testLoadRulePackageItem(org.drools.repository.PackageItemTest) testPackageRuleVersionExtraction(org.drools.repository.PackageItemTest) testIgnoreState(org.drools.repository.PackageItemTest) testDuplicatePackageName(org.drools.repository.PackageItemTest) testPackageInstanceWrongNodeType(org.drools.repository.PackageItemTest) testLoadRulePackageItemByUUID(org.drools.repository.PackageItemTest) testAddRuleRuleItem(org.drools.repository.PackageItemTest) testGetRules(org.drools.repository.PackageItemTest) testToString(org.drools.repository.PackageItemTest) testRemoveRule(org.drools.repository.PackageItemTest) testSearchByFormat(org.drools.repository.PackageItemTest) testListArchivedAssets(org.drools.repository.PackageItemTest) testMiscProperties(org.drools.repository.PackageItemTest) testGetFormat(org.drools.repository.PackageItemTest) testPackageCheckinConfig(org.drools.repository.PackageItemTest) testTagItem(org.drools.repository.CategoryItemTest) testCreateCateories(org.drools.repository.CategoryItemTest) testGetChildTags(org.drools.repository.CategoryItemTest) testGetChildTag(org.drools.repository.CategoryItemTest) testGetFullPath(org.drools.repository.CategoryItemTest) testRemoveCategoryUneeded(org.drools.repository.CategoryItemTest) testFindArchivedAssets(org.drools.repository.ArchiveItemTest) testArchiveBooleanFlag(org.drools.repository.ArchiveItemTest) testLoadArchivedAsset(org.drools.repository.ArchiveItemTest) testFindArchivedAssetsByCategory(org.drools.repository.ArchiveItemTest) testLoadPackages(org.drools.repository.ArchiveItemTest) testFindRulesByNameArchived(org.drools.repository.ArchiveItemTest) testToString(org.drools.repository.AssetItemTest) testGetFormat(org.drools.repository.AssetItemTest) testAssetItemCreation(org.drools.repository.AssetItemTest) testGetPackageItem(org.drools.repository.AssetItemTest) testGetContent(org.drools.repository.AssetItemTest) testUpdateContent(org.drools.repository.AssetItemTest) testCategories(org.drools.repository.AssetItemTest) testUpdateCategories(org.drools.repository.AssetItemTest) testFindRulesByCategory(org.drools.repository.AssetItemTest) testRemoveTag(org.drools.repository.AssetItemTest) testGetTags(org.drools.repository.AssetItemTest) testSetStateString(org.drools.repository.AssetItemTest) testStatusStuff(org.drools.repository.AssetItemTest) testGetLastModifiedOnCheckin(org.drools.repository.AssetItemTest) testGetDateEffective(org.drools.repository.AssetItemTest) testGetDateExpired(org.drools.repository.AssetItemTest) testSaveAndCheckinDescriptionAndTitle(org.drools.repository.AssetItemTest) testGetPrecedingVersionAndRestore(org.drools.repository.AssetItemTest) testGetSucceedingVersion(org.drools.repository.AssetItemTest) testGetSuccessorVersionsIterator(org.drools.repository.AssetItemTest) testGetPredecessorVersionsIterator(org.drools.repository.AssetItemTest) testHistoryIterator(org.drools.repository.AssetItemTest) testGetTitle(org.drools.repository.AssetItemTest) testDublinCoreProperties(org.drools.repository.AssetItemTest) testAnonymousProperties(org.drools.repository.AssetItemTest) testBinaryAsset(org.drools.repository.AssetItemTest) testAddDirectories(org.drools.scm.jcr.JcrActionFactoryTest) testAddFiles(org.drools.scm.jcr.JcrActionFactoryTest) testUpdateFiles(org.drools.scm.jcr.JcrActionFactoryTest) testDefaultPackage(org.drools.repository.RulesRepositoryTest) testAddVersionARule(org.drools.repository.RulesRepositoryTest) testFindRulesByName(org.drools.repository.RulesRepositoryTest) testLoadRuleByUUIDWithConcurrentSessions(org.drools.repository.RulesRepositoryTest) testAddRuleCalendarWithDates(org.drools.repository.RulesRepositoryTest) testGetState(org.drools.repository.RulesRepositoryTest) testGetTag(org.drools.repository.RulesRepositoryTest) testListPackages(org.drools.repository.RulesRepositoryTest) testCategoriesAndSnapshots(org.drools.repository.RulesRepositoryTest) testMoveRulePackage(org.drools.repository.RulesRepositoryTest) testCopyAsset(org.drools.repository.RulesRepositoryTest) testRenameAsset(org.drools.repository.RulesRepositoryTest) testRenamePackage(org.drools.repository.RulesRepositoryTest) testCopyPackage(org.drools.repository.RulesRepositoryTest) testListStates(org.drools.repository.RulesRepositoryTest) testImportExport(org.drools.repository.RulesRepositoryTest) testExportZippedRepository(org.drools.repository.RulesRepositoryTest) Tests run: 104, Failures: 0, Errors: 77, Skipped: 0 -- 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

18 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBREM-892) CLONE -Client side connection exception is not thrown on the client side when the lease times out [JBREM-888]

by Ron Sigal (JIRA)

CLONE -Client side connection exception is not thrown on the client side when the lease times out [JBREM-888] ------------------------------------------------------------------------------------------------------------- Key: JBREM-892 URL: http://jira.jboss.com/jira/browse/JBREM-892 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP4 Reporter: Jay Howell Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) Clients that are connected that experience a lease timeout are not notified that they no longer have a connection on the server. The behavior is that clients think that they are alive, while they will no longer get any messages. Also something of note, the Server side pinger has been disabled for JBM. Note: this is an issue that can either be fixed on the remoting side or the JBM side. Discussing this with Clebert, it may be prudent to fix it on both sides. I've opened this jira to facilitate the communication about where the logic should go. Please refer to the linked jira for the JBM ticket that was opened for this same topic. -- 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

18 years, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1845) CSS cleanup & refactor

by Wesley Hales (JIRA)

CSS cleanup & refactor ---------------------- Key: JBPORTAL-1845 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1845 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Wesley Hales Assigned To: Wesley Hales Fix For: 2.6.4 Final - Extract common CSS styles to separate module. - Remove inline styles. -- 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

18 years, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1226) Deadlock occurs when deleting messages when using MySQL for persistence.

by Phillip Thurmond (JIRA)

Deadlock occurs when deleting messages when using MySQL for persistence. ------------------------------------------------------------------------ Key: JBMESSAGING-1226 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1226 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3 Reporter: Phillip Thurmond Assigned To: Tim Fox Priority: Minor This could possibly be a JDBC bug, but I thought it might be related to the way JBM is executing the SQL statements. I noticed this error when I upgraded the mysql jdbc driver from 3 to 5. The datasource remains the same. I never saw the deadlock with the older jdbc driver, but it could possibly affect other DB's as well. Please note that the transaction DOES succeed after retry, however, these are occurring very often according to the logs. Innotop (mysql monitoring tool) output for the deadlock: Deadlock Transactions __________________________________________________________________________________________ CXN ID Timestring User Host Victim Time Undo LStrcts Query Text cluster08 355 2008-01-29 17:02:09 jms perf01 No 00:00 3 4 DELETE FROM JBM_MSG_REF WHERE MESSAGE_ID=3032 AND CHANNEL_ID=82 AND STATE='C' cluster08 364 2008-01-29 17:02:09 jms perf01 Yes 00:00 0 3 DELETE FROM JBM_MSG WHERE MESSAGE_ID = 3032 AND NOT EXISTS (SELECT * FROM JBM_MSG_REF WHERE JBM_MSG_REF.MESSAGE_ID = 3032) You can see that it looks like the DELETE_MESSAGE query was executed before the DELETE_MESSAGE_REF query finished. -- 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

18 years, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (JBAS-5103) Transaction manager migration out of jboss-service.xml

by Scott M Stark (JIRA)

Transaction manager migration out of jboss-service.xml ------------------------------------------------------ Key: JBAS-5103 URL: http://jira.jboss.com/jira/browse/JBAS-5103 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Manager Affects Versions: JBossAS-5.0.0.Beta3 Reporter: Scott M Stark Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.CR1 We need to move the transaction manager related services out of the conf/jboss-service.xml to a bean descriptor in deploy along with any dependencies. -- 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

18 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1076) Missing annotation parameter in example "web-service"

by Pavel Kadlec (JIRA)

Missing annotation parameter in example "web-service" ----------------------------------------------------- Key: JBMESSAGING-1076 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1076 Project: JBoss Messaging Issue Type: Bug Components: Documentation and Training Affects Versions: 1.4.0.CR2 Environment: jbossws-native-2.0.0.GA Reporter: Pavel Kadlec Assigned To: Tim Fox Attachments: WebServiceExampleImpl-patch.java WebService annotation does not have determined parameter "serviceName" in example "web-service". The container (jbossws-native-2.0.0.GA) assigns serviceName, by default "WebServiceExampleImplService". Client asks for service "JMSSampleService". The full annotation should look like @WebService(serviceName="JMSSampleService", name="JMSSample") -- 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

18 years, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1319) debug junit test as drools application without requiring main function on junit test class

by John Franey (JIRA)

debug junit test as drools application without requiring main function on junit test class ------------------------------------------------------------------------------------------ Key: JBRULES-1319 URL: http://jira.jboss.com/jira/browse/JBRULES-1319 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 4.0.3 Environment: eclipse 3.3 x64, jrockit 6 x64, ubuntu linux 7.10 (gutsy gibbon) Reporter: John Franey Priority: Optional It is not necessary to write main methods for junit test classes. Eclipse can run, debug or profile a 'main-less' junit test simply by right clicking on a junit test class in the package browser, selecting 'run as', 'debug as' or 'profile as' -> junit test. In general, main methods are not part of junit test classes. Even when run from command line, junit tests are not required to have main methods. 'Debug as drools application' is the only action in eclipse that lets me debug drools rules. 'Debug as drools application' is available only on java classes with main methods. Junit classes generally do not have main methods. I would like to debug drools rules that a junit test is testing. In order to do so, I have to write a main method for the junit test case. Very easy to write, but I don't think it should be necessary. Regards, -- 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

18 years, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-4919) HASingletonElectionPolicySimple does not handle heterogeneous topologies

by Brian Stansberry (JIRA)

HASingletonElectionPolicySimple does not handle heterogeneous topologies ------------------------------------------------------------------------ Key: JBAS-4919 URL: http://jira.jboss.com/jira/browse/JBAS-4919 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.2.3.GA HASingletonElectionPolicySimple is just getting the current view from HAPartition and making a decision based on that, ignoring the fact that the service it's managing may not be running on all members of the cluster. The HASingletonElectionPolicy API should be changed. The isMasterReplica method should take (List<ClusterNode> newReplicants, int newViewID) rather than HAPartition. The partition is provided via dependency injection at startup, no need to pass it in the method call. HASingletonElectionPolicySimple uses the provided replicants to make its decision, not the HAPartition view. -- 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

18 years, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (JBAS-5006) org.jboss.test.naming

by Shelly McGowan (JIRA)

org.jboss.test.naming --------------------- Key: JBAS-5006 URL: http://jira.jboss.com/jira/browse/JBAS-5006 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan Assigned To: Shelly McGowan -- 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

18 years, 5 months

2
5
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 January 2008