[JBoss JIRA] Created: (JBRULES-2870) Option to bypass the package authentication in rule agent
by Jian Zhi (JIRA)
Option to bypass the package authentication in rule agent
---------------------------------------------------------
Key: JBRULES-2870
URL: https://issues.jboss.org/browse/JBRULES-2870
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.1.1.FINAL
Reporter: Jian Zhi
Assignee: Mark Proctor
GUVNOR-133 (Rules Agent provides access to all users' rules without authentication) added a new feature to authenticate the user in Rule agent. We would like to have this function as an optional feature. When we evaluate the rule in the application we would like to turn off the authentication, so at the runtime the user authentication is bypassed when the package is fetched through URL.
In 5.1.1 release we got IO Exception when RuleAgent.ENABLE_BASIC_AUTHENTICATION is set to false.
java.io.IOException: Server returned HTTP response code: 401 for URL: http://localhost:8080/drools-guvnor/org.drools.guvnor.Guvnor/package/XXX/...
14:23:04,941 ERROR [STDERR] at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1313)
14:23:04,941 ERROR [STDERR] at org.drools.agent.HttpClientImpl.fetchPackage(HttpClientImpl.java:77)
14:23:04,941 ERROR [STDERR] at org.drools.agent.URLScanner.readPackage(URLScanner.java:171)
14:23:04,942 ERROR [STDERR] at org.drools.agent.URLScanner.getChangeSet(URLScanner.java:143)
14:23:04,942 ERROR [STDERR] at org.drools.agent.URLScanner.loadPackageChanges(URLScanner.java:119)
14:23:04,942 ERROR [STDERR] at org.drools.agent.RuleAgent.checkForChanges(RuleAgent.java:429)
14:23:04,942 ERROR [STDERR] at org.drools.agent.RuleAgent.refreshRuleBase(RuleAgent.java:381)
14:23:04,942 ERROR [STDERR] at org.drools.agent.RuleAgent.configure(RuleAgent.java:366)
14:23:04,942 ERROR [STDERR] at org.drools.agent.RuleAgent.init(RuleAgent.java:266)
14:23:04,942 ERROR [STDERR] at org.drools.agent.RuleAgent.newRuleAgent(RuleAgent.java:206)
14:23:04,942 ERROR [STDERR] at org.drools.agent.RuleAgent.newRuleAgent(RuleAgent.java:166)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBRULES-2852) SingleThreadedObjectStore.isEmpty() implementation returns true when objects are in store
by Radai Rosenblatt (JIRA)
SingleThreadedObjectStore.isEmpty() implementation returns true when objects are in store
-----------------------------------------------------------------------------------------
Key: JBRULES-2852
URL: https://issues.jboss.org/browse/JBRULES-2852
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.1.1.FINAL
Reporter: Radai Rosenblatt
Assignee: Mark Proctor
SingleThreadedObjectStore, line 88:
public boolean isEmpty() {
return this.assertMap != null;
}
i dont understand the logic here, but with a store with a single object (both assertmap and identitymap are non-null) this returns true, while there are values that can be iterated. this means that for an entry point using this store, isEmpty() returns true while toArray() returns a non-empty array ...
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBRULES-2841) BinaryHeapQueueAgendaGroup fails to return top salience item
by k s (JIRA)
BinaryHeapQueueAgendaGroup fails to return top salience item
------------------------------------------------------------
Key: JBRULES-2841
URL: https://issues.jboss.org/browse/JBRULES-2841
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.1.1.FINAL
Reporter: k s
Assignee: Mark Proctor
We have come across a case where the rules engine does not fire the top priority (top salience) rule. After a lot of careful debugging, it seems that the BinaryHeapQueueAgendaGroup implementation (and most likely the supporting BinaryHeapQueue) has a bug. It is not a common case and it was hard to reproduce. We have put together a junit test to show the problem. The test "replays" the trace from the case where we show the error (sparing you from all the complexity of the actual rules and produced it). I will attach the JUnit test and the trace file that drives the test.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (EJBTHREE-1166) jta-data-source / non-jta-data-source
by Jesper Pedersen (JIRA)
jta-data-source / non-jta-data-source
-------------------------------------
Key: EJBTHREE-1166
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1166
Project: EJB 3.0
Issue Type: Bug
Environment: JBoss AS: SVN / trunk (rev 68402)
jboss-ejb3-cache version="0.11.1"
jboss/jboss-ejb3-ext-api version="0.1.2.Beta1"
jboss/jboss-ejb3-impl version="0.1.2.Beta1"
Reporter: Jesper Pedersen
I get the following:
persistence.units:ear=rasp-sender.ear,unitName=e-akten-test -> java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a non-jta-data-source for a RESOURCE_LOCAL enabled persistence context named: e-akten-test
persistence.units:ear=rasp-sender.ear,unitName=e-akten -> java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a jta-data-source for a JTA enabled persistence context named: e-akten
The EJB3 persistence spec section 6.2.1.5 states:
"In Java EE environments, the jta-data-source and non-jta-data-source elements are used
to specify the global JNDI name of the JTA and/or non-JTA data source to be used by the persistence
provider. If neither is specified, the deployer must specify a JTA data source at deployment or a JTA
data source must be provided by the container, and a JTA EntityManagerFactory will be created to cor-
respond to it."
I'm counting on the last case -- data source must be provided by container + entity manager.
Hope this helps !
--
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
15 years, 2 months