October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1133) Janino and eclipse compiler might need to be optional for 4.1

by Geoffrey De Smet (JIRA)

Janino and eclipse compiler might need to be optional for 4.1 ------------------------------------------------------------- Key: JBRULES-1133 URL: http://jira.jboss.com/jira/browse/JBRULES-1133 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.0.GA Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Minor Fix For: FUTURE I didn't want to make this change for 4.0.x as it would require our users to put a direct dependency on either janino or eclipse-compiler. Drools-compiler needs one of both. Currently users get bloated with a transitive dependency on both. Making them optional would force them to make a dependency on one of the themselves... which makes the "hello world" program harder. As it would also force jbrms's etc tests to choose one. Why shouldn't do this before 4.1, if we even want to do this. What do you think? -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-686) Query on rule field usage information

by Michael Neale (JIRA)

Query on rule field usage information ------------------------------------- Key: JBRULES-686 URL: http://jira.jboss.com/jira/browse/JBRULES-686 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale -- 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, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1249) Allow repository location to be specified in BRMS web client

by Shahad Ahmed (JIRA)

Allow repository location to be specified in BRMS web client ------------------------------------------------------------ Key: JBRULES-1249 URL: http://jira.jboss.com/jira/browse/JBRULES-1249 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.1 Reporter: Shahad Ahmed Assigned To: Mark Proctor At present, any custom location of the repository is set in a components.xml file inside the WEB-INF directory of the BRMS war file. It would be better if the user could specify the location using the BRMS web client itself, rather than have to unzip, modify and zip up the WAR file. Perhaps this functionality could be added to the Admin section of the BRMS. One advantage of this is that users could also then work with multiple repositories (e.g. for different projects). In effect there would be an option to create a new repository (specified by a directory given by the user), open an existing repository and close a repository. -- 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, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1150) Drools 4.0 BRMS not working with geronimo-jetty6-jee5-2.0.1

by Bhagwath Vadyala (JIRA)

Drools 4.0 BRMS not working with geronimo-jetty6-jee5-2.0.1 ----------------------------------------------------------- Key: JBRULES-1150 URL: http://jira.jboss.com/jira/browse/JBRULES-1150 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: geronimo-jetty6-jee5-2.0.1 drools-4.0.1.SNAPSHOT-brms Reporter: Bhagwath Vadyala Assigned To: Mark Proctor I am trying to test and see whether Drools 4.0 BRMS works with Geronimo-jetty6-jee5-2.0.1 or not. Drools BRMS version which I am using is drools-4.0.1.SNAPSHOT-brms. It deploys fine in Geronimo but when I open the BRMS error message I am getting is HTTP ERROR:404. Please let me know whether we can make Drools 4.0 work with Geronimo-jetty version -- 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, 2 months

4
11
0 / 0

[JBoss JIRA] Created: (JBCACHE-1190) Eviction configuration should consider buddy backup regions as well.

by Manik Surtani (JIRA)

Eviction configuration should consider buddy backup regions as well. -------------------------------------------------------------------- Key: JBCACHE-1190 URL: http://jira.jboss.com/jira/browse/JBCACHE-1190 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Eviction Affects Versions: 2.0.0.GA Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.2.0.GA -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-805) Channel is set to AUTO_GET_STATE even if cache doesn't want initial state transfer

by Brian Stansberry (JIRA)

Channel is set to AUTO_GET_STATE even if cache doesn't want initial state transfer ---------------------------------------------------------------------------------- Key: JBCACHE-805 URL: http://jira.jboss.com/jira/browse/JBCACHE-805 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani The channel should probably only be set to AUTO_GET_STATE if getFetchStateOnStartup() returns true. Otherwise if the node is shunned and reconnects, a full state transfer will occur. Presumably the cache can't or doesn't want to handle that, or getFetchStateOnStartup() would not have returned true. One problem is what if getFetchStateOnStartup() returns false because the config uses a shared cache loader (so no persistent state transfer) and a cold cache at startup is OK (so no in-memory state transfer). But, following reconnect the cache is no longer "cold" -- the in-memory tree now has potentially stale data. -- 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, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-1201) OPTIMISTIC locking requires SyncCommitPhase to be true

by Brian Stansberry (JIRA)

OPTIMISTIC locking requires SyncCommitPhase to be true ------------------------------------------------------ Key: JBCACHE-1201 URL: http://jira.jboss.com/jira/browse/JBCACHE-1201 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Replication Reporter: Brian Stansberry Assigned To: Manik Surtani Fix For: 2.1.0.BETA1 When using OPTIMISTIC and REPL_SYNC, I find I need to set SyncCommitPhase=true in order for the following to work: tm.begin(); cache1.put(fqn, KEY, VALUE1); tm.commit(); assertEquals("Correct node2 value", VALUE1, cache2.get(fqn, KEY)); With SyncCommitPhase=false, cache2.get(fqn, KEY) consistently returns null. A simple sleep after the commit call will also make this test pass My understanding of distributed optimistic locking is that at the end of the prepare phase, on all nodes in the cluster the originating node's workspace modifications should have been applied to the main tree, with normal write locks held on the updated nodes. The commit call then causes the locks to be released, as in pessimistic locking. The above test result implies this is not the case. That implies more work is going on in the commit phase than is appropriate for a Synchronization.afterCompletion() callback. Test for this is o.j.c.optimistic.FullStackInterceptorTest.testAsynchronousCommit() -- 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, 2 months

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-4469) Extract the common use clustering code from the JBoss AS codebase

by Brian Stansberry (JIRA)

Extract the common use clustering code from the JBoss AS codebase ----------------------------------------------------------------- Key: JBAS-4469 URL: http://jira.jboss.com/jira/browse/JBAS-4469 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 JBAS corollary to JBCLUSTER-135. -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-442) Add SSL support for both TCP and TCP_NIO

by Bela Ban (JIRA)

Add SSL support for both TCP and TCP_NIO ---------------------------------------- Key: JGRP-442 URL: http://jira.jboss.com/jira/browse/JGRP-442 Project: JGroups Issue Type: Feature Request Affects Versions: 2.5 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6 Use SSLEngine to do this, so we only have 1 implementation for *both* TCP and TCP_NIO. This is described in http://jira.jboss.com/jira/browse/JGRP-371 and http://jira.jboss.com/jira/browse/JGRP-372 -- 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, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JGRP-601) Parallelizing test suite

by Bela Ban (JIRA)

Parallelizing test suite ------------------------ Key: JGRP-601 URL: http://jira.jboss.com/jira/browse/JGRP-601 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.x Run the following in parallel - functional tests - stack-specific tests E.g. run UDP tests in parallel with TCP Look at DTF (Distributed Test Framework) for this -- 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, 2 months

1
2
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 October 2007