[JBoss JIRA] (DROOLS-1094) OptaPlanner Kie server service: unable to retrieve best solution
by Rajesh Rajasekaran (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1094?page=com.atlassian.jira.plugi... ]
Rajesh Rajasekaran updated DROOLS-1094:
---------------------------------------
Labels: qe-recommend-fix-before-ga reported-by-qe (was: reported-by-qe)
> OptaPlanner Kie server service: unable to retrieve best solution
> ----------------------------------------------------------------
>
> Key: DROOLS-1094
> URL: https://issues.jboss.org/browse/DROOLS-1094
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Affects Versions: 6.4.0.CR1
> Environment: Kie server OptaPlanner service
> Reporter: Karel Suta
> Assignee: Geoffrey De Smet
> Labels: qe-recommend-fix-before-ga, reported-by-qe
>
> When I try to retrieve best solution from Solver in Kie server OptaPlanner extension, JAXB and XSTREAM works correctly but JSON doesn't. JSON marshalling isn't able to map planning variable in planning entity.
> It can be simulated using cloudbalance problem which is part of Kie server OptaPlanner integration tests. See test method testGetBestSolution in OptaplannerIntegrationTest.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (DROOLS-974) Activation group doesn't work as expected
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-974?page=com.atlassian.jira.plugin... ]
Mario Fusco reassigned DROOLS-974:
----------------------------------
Assignee: Mario Fusco (was: Mark Proctor)
> Activation group doesn't work as expected
> -----------------------------------------
>
> Key: DROOLS-974
> URL: https://issues.jboss.org/browse/DROOLS-974
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.2.0.Final, 6.3.0.Final
> Environment: Mac OS X 10.8.3
> jdk 1.7.0_60
> Reporter: Hanbing Luo
> Assignee: Mario Fusco
>
> In some rare cases activation group doesn't work as expected. For example, two rules with same ruleflow-group and activation-group but different salience are both get fired if reuse kie session.
> Some investigation notes to help address.
> 1) This issue never happen if use a new fresh kie session.
> 2) I also tried to write a drools style unit test (testActivationGroupIssue in ExecutionFlowControlTest.java) but can't reproduce this issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ELY-37) Audit Logging Integration
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/ELY-37?page=com.atlassian.jira.plugin.sys... ]
David Lloyd edited comment on ELY-37 at 3/16/16 9:08 AM:
---------------------------------------------------------
We have determined that the following events should be supported:
* Authentication initiated
* Authentication succeeded
* Authentication failed
* Authentication incomplete
* Authorization check succeeded
* Authorization check failed
* Authorization identity change (run-as)
* Session events:
** Session opened (login)
** Session closed (logout)
** Session lost (application error)
* Application events (include a user-defined category)
In addition, a session login/logout API should be made available (details forthcoming).
was (Author: dmlloyd):
We have determined that the following events should be supported:
* Authentication initiated
* Authentication succeeded
* Authentication failed
* Authentication incomplete
* Authorization check succeeded
* Authorization check failed
In addition, a session login/logout API should be made available (details forthcoming).
> Audit Logging Integration
> -------------------------
>
> Key: ELY-37
> URL: https://issues.jboss.org/browse/ELY-37
> Project: WildFly Elytron
> Issue Type: Task
> Components: API / SPI, Audit
> Reporter: Darran Lofthouse
> Assignee: Jan Kalina
> Fix For: 1.1.0.CR1
>
>
> Implement into Elytron samething like:
> https://github.com/picketbox/picketbox/tree/master/security-spi/spi/src/m...
> or
> https://github.com/wildfly/wildfly-core/tree/master/controller/src/main/j...
> or
> https://github.com/kabir/tamper-detecting-audit-log
> UPDATE:
> By discussion should be based on currently not implemented processing of **security events** - depends on it from now.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6381) CDI Event handler after transaction success fails to call transactional method
by Ján Halaša (JIRA)
Ján Halaša created WFLY-6381:
--------------------------------
Summary: CDI Event handler after transaction success fails to call transactional method
Key: WFLY-6381
URL: https://issues.jboss.org/browse/WFLY-6381
Project: WildFly
Issue Type: Feature Request
Components: CDI / Weld, EJB, JCA
Affects Versions: 10.0.0.Final
Environment: Windows 7, Java 1.8.51
Reporter: Ján Halaša
Assignee: Stuart Douglas
Attachments: AfterSuccessTest.zip, wildfly.log
Scenario:
# EJB transactional business method fires a CDI event
# The CDI event is handled by an event observer configured to receive event after its transaction succeeds (during = TransactionPhase.AFTER_SUCCESS)
# The event handler calls another EJB transactional method, but the call fails with a ResourceException, error code IJ000459 (last part of its stacktrace pasted below). Full log is attached as a file. I think, when the handler is called, the original transaction should not be there anymore and a new one should be created.
I attached a simple test web application with a servlet which triggers the sequence described before. I tried the test application on Weblogic 12.2.1 and it worked without problems. The application requires a data source - H2 in-memory is good enough, table will be created automatically by JPA.
{code:java}
Caused by: javax.resource.ResourceException: IJ000460: Error checking for a transaction
at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:424)
at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:747)
at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:138)
... 196 more
Caused by: javax.resource.ResourceException: IJ000459: Transaction is not active: tx=TransactionImple < ac, BasicAction: 0:ffffac180a71:3fd5e4ea:56e93a24:184 status: ActionStatus.COMMITTED >
at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:408)
... 198 more
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (DROOLS-1077) [POST] /containers/{id} is outdated
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1077?page=com.atlassian.jira.plugi... ]
Edson Tirelli resolved DROOLS-1077.
-----------------------------------
Fix Version/s: 6.4.0.CR2
7.0.0.Final
Resolution: Done
This was fixed as part of the following commits:
master: https://github.com/droolsjbpm/kie-docs/commit/bb6911736d932e2c9ab67f51f52...
6.4.x: https://github.com/droolsjbpm/kie-docs/commit/f1b2ebb460fe58f330fabdb4e83...
> [POST] /containers/{id} is outdated
> ------------------------------------
>
> Key: DROOLS-1077
> URL: https://issues.jboss.org/browse/DROOLS-1077
> Project: Drools
> Issue Type: Bug
> Components: docs
> Affects Versions: 6.3.0.Final
> Environment: The REST URI to send the command fire-all-rules to an running container is outdated.
> Using the URI described in the docs I get the following result:
> {code}
> 2016-02-29 17:03:26 DEBUG org.apache.http.headers - http-outgoing-0 << Allow: HEAD, DELETE, GET, OPTIONS, PUT
> 2016-02-29 17:03:26 DEBUG org.apache.http.headers - http-outgoing-0 << Content-Type: text/html;charset=utf-8
> 2016-02-29 17:03:26 DEBUG org.apache.http.headers - http-outgoing-0 << Content-Length: 1022
> 2016-02-29 17:03:26 DEBUG org.apache.http.headers - http-outgoing-0 << Date: Mon, 29 Feb 2016 20:03:58 GMT
> Exception in thread "main" java.lang.RuntimeException: Failed with HTTP error code : 405
> at org.jboss.test.arquillian.ce.decisionserver.DecisionServerSecureTest.main(DecisionServerSecureTest.java:404)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> {code}
> The correct URI is:
> . [POST] instances/containers/{id}
> After to change the REST call worked as exp
> Documentation link: https://docs.jboss.org/drools/release/6.3.0.Final/drools-docs/pdf/drools-...
> Item 22.6.7.
> Reporter: Filippe Spolti
> Assignee: Edson Tirelli
> Labels: doc, rest_api
> Fix For: 6.4.0.CR2, 7.0.0.Final
>
>
> The REST URI to send the command fire-all-rules to an running container is outdated.
> Using the URI described in the docs I get the following result:
> {code}
> 2016-02-29 17:03:26 DEBUG org.apache.http.headers - http-outgoing-0 << Allow: HEAD, DELETE, GET, OPTIONS, PUT
> 2016-02-29 17:03:26 DEBUG org.apache.http.headers - http-outgoing-0 << Content-Type: text/html;charset=utf-8
> 2016-02-29 17:03:26 DEBUG org.apache.http.headers - http-outgoing-0 << Content-Length: 1022
> 2016-02-29 17:03:26 DEBUG org.apache.http.headers - http-outgoing-0 << Date: Mon, 29 Feb 2016 20:03:58 GMT
> Exception in thread "main" java.lang.RuntimeException: Failed with HTTP error code : 405
> at org.jboss.test.arquillian.ce.decisionserver.DecisionServerSecureTest.main(DecisionServerSecureTest.java:404)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> {code}
> The correct URI is:
> . [POST] containers/instances/{id}
> After to change the REST call worked as expected.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month