[JBoss JIRA] (DROOLS-3468) [DMN Editor] Support Decision Service invocation
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3468?page=com.atlassian.jira.plugi... ]
Jozef Marko edited comment on DROOLS-3468 at 1/2/19 9:39 AM:
-------------------------------------------------------------
[~tari_manga] I provided picture. And yes, I agree the problem is due to missing _KnowledgeRequirement_, that is why I filed an issues as our designer doesn't allow me to create such connection there.
was (Author: jomarko):
[~tari_manga] I provided picture. And yes, I agree the problem is due to missing `KnowledgeRequirement`, that is why I filed an issues as our designer doesn't allow me to create such connection there.
> [DMN Editor] Support Decision Service invocation
> ------------------------------------------------
>
> Key: DROOLS-3468
> URL: https://issues.jboss.org/browse/DROOLS-3468
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.16.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: Screenshot from 2019-01-02 15-37-21.png, a1 (1).dmn, error.log, server-error.log
>
>
> User is not able to model a DMN model where he declare a Decision service and invoke this Decision Service from other node, because the Decision Service node doesn't allow any incoming nor outgoing connections.
> h2. Acceptance criteria
> - Import attached model *a1*
> - Connect *mood* decision service and *Decision-1* decision node
> - Deploy the model
> - Try to evaluate model via a rest call
> - Check the output json doesn't contain [^error.log]
> - Check the server log doesn't contain [^server-error.log]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (DROOLS-3468) [DMN Editor] Support Decision Service invocation
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3468?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3468:
-------------------------------------
[~tari_manga] I provided picture. And yes, I agree the problem is due to missing `KnowledgeRequirement`, that is why I filed an issues as our designer doesn't allow me to create such connection there.
> [DMN Editor] Support Decision Service invocation
> ------------------------------------------------
>
> Key: DROOLS-3468
> URL: https://issues.jboss.org/browse/DROOLS-3468
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.16.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: Screenshot from 2019-01-02 15-37-21.png, a1 (1).dmn, error.log, server-error.log
>
>
> User is not able to model a DMN model where he declare a Decision service and invoke this Decision Service from other node, because the Decision Service node doesn't allow any incoming nor outgoing connections.
> h2. Acceptance criteria
> - Import attached model *a1*
> - Connect *mood* decision service and *Decision-1* decision node
> - Deploy the model
> - Try to evaluate model via a rest call
> - Check the output json doesn't contain [^error.log]
> - Check the server log doesn't contain [^server-error.log]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (DROOLS-3468) [DMN Editor] Support Decision Service invocation
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3468?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3468:
--------------------------------
Attachment: Screenshot from 2019-01-02 15-37-21.png
> [DMN Editor] Support Decision Service invocation
> ------------------------------------------------
>
> Key: DROOLS-3468
> URL: https://issues.jboss.org/browse/DROOLS-3468
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.16.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: Screenshot from 2019-01-02 15-37-21.png, a1 (1).dmn, error.log, server-error.log
>
>
> User is not able to model a DMN model where he declare a Decision service and invoke this Decision Service from other node, because the Decision Service node doesn't allow any incoming nor outgoing connections.
> h2. Acceptance criteria
> - Import attached model *a1*
> - Connect *mood* decision service and *Decision-1* decision node
> - Deploy the model
> - Try to evaluate model via a rest call
> - Check the output json doesn't contain [^error.log]
> - Check the server log doesn't contain [^server-error.log]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (WFLY-11543) EJB transactional method unable to commit when invoked from CDI bean with MariaDB
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11543?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-11543:
------------------------------------
Fix Version/s: 15.0.1
> EJB transactional method unable to commit when invoked from CDI bean with MariaDB
> ---------------------------------------------------------------------------------
>
> Key: WFLY-11543
> URL: https://issues.jboss.org/browse/WFLY-11543
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 15.0.0.Final
> Environment: WildFly 15.0.0.Final
> MariaDB 10.1.19
> Reporter: Michal Jurc
> Assignee: Scott Marlow
> Priority: Blocker
> Fix For: 15.0.1.Final, 16.0.0.Beta1
>
> Attachments: logs.zip, server-trace.zip
>
>
> Issue cloned from the [community forum|https://developer.jboss.org/thread/279303] for tracking.
> {quote}Hello,
>
> We are having issues after deploying our application in the latest Wildfly 15.0.0 Final recently released with the following exception:
> java.sql.SQLException: XAER_RMFAIL: The command cannot be executed when global transaction is in the IDLE state
>
> The error occurs when our code calls a transactional EJB method that itself calls a couple more injected SessionBean that handles the database persistence through an EntityManager
> The issue only seems to affect the MariaDB port and not oracle.{quote}
> {quote}I have hit the same problem, migrated from Wildfly 10.0.0. to 15.0.0, using MySQL, same error, similar situation, cdi managed bean that invokes 2 EJBs that use different persistent units. I dont seem to have the problem in 14.0.1 either.
>
> Another error that has surfaced is this (apologies for the weird formatting but struggled to define a simple type-up without cluttering)
>
> "javax.persistence.TransactionRequiredException: no transaction is in progress"
> Managed bean with injected ejb (with datasource2) and injected entitymanager for datasource1, code is nested as follows
>
> Managed bean method save @Transactional(value = TxType.REQUIRED)
> {
> ejb save @TransactionAttribute(TransactionAttributeType.MANDATORY)
> {
> persist
> flush
> }
>
> find with lock => LockModeType.PESSIMISTIC_WRITE at this point the "no transaction is in progress" exception is fired
>
> }
>
> Did notice that error does not occur if the invocation is purely ejb rather that cdi managed bean {quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (WFLY-11543) EJB transactional method unable to commit when invoked from CDI bean with MariaDB
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11543?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-11543:
------------------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/11961, https://github.com/wildfly/wildfly/pull/11966 (was: https://github.com/wildfly/wildfly/pull/11961)
> EJB transactional method unable to commit when invoked from CDI bean with MariaDB
> ---------------------------------------------------------------------------------
>
> Key: WFLY-11543
> URL: https://issues.jboss.org/browse/WFLY-11543
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 15.0.0.Final
> Environment: WildFly 15.0.0.Final
> MariaDB 10.1.19
> Reporter: Michal Jurc
> Assignee: Scott Marlow
> Priority: Blocker
> Fix For: 15.0.1.Final, 16.0.0.Beta1
>
> Attachments: logs.zip, server-trace.zip
>
>
> Issue cloned from the [community forum|https://developer.jboss.org/thread/279303] for tracking.
> {quote}Hello,
>
> We are having issues after deploying our application in the latest Wildfly 15.0.0 Final recently released with the following exception:
> java.sql.SQLException: XAER_RMFAIL: The command cannot be executed when global transaction is in the IDLE state
>
> The error occurs when our code calls a transactional EJB method that itself calls a couple more injected SessionBean that handles the database persistence through an EntityManager
> The issue only seems to affect the MariaDB port and not oracle.{quote}
> {quote}I have hit the same problem, migrated from Wildfly 10.0.0. to 15.0.0, using MySQL, same error, similar situation, cdi managed bean that invokes 2 EJBs that use different persistent units. I dont seem to have the problem in 14.0.1 either.
>
> Another error that has surfaced is this (apologies for the weird formatting but struggled to define a simple type-up without cluttering)
>
> "javax.persistence.TransactionRequiredException: no transaction is in progress"
> Managed bean with injected ejb (with datasource2) and injected entitymanager for datasource1, code is nested as follows
>
> Managed bean method save @Transactional(value = TxType.REQUIRED)
> {
> ejb save @TransactionAttribute(TransactionAttributeType.MANDATORY)
> {
> persist
> flush
> }
>
> find with lock => LockModeType.PESSIMISTIC_WRITE at this point the "no transaction is in progress" exception is fired
>
> }
>
> Did notice that error does not occur if the invocation is purely ejb rather that cdi managed bean {quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (DROOLS-3468) [DMN Editor] Support Decision Service invocation
by Matteo Mortari (Jira)
[ https://issues.jboss.org/browse/DROOLS-3468?page=com.atlassian.jira.plugi... ]
Matteo Mortari commented on DROOLS-3468:
----------------------------------------
[~jomarko] Can you kindly provide a screenshot of the model you tried to author, please?
I am asking as I reckon 2 issues with the .dmn file.
1. there is no KnowledgeRequirement between the Decision-1 and the Decision service, so it is normal it cannot be invoked
2. DMNDI positioning looks off, looks like the Decision Service is in the bottom right corner while most of the DRGElements are positioned in the upper left.
> [DMN Editor] Support Decision Service invocation
> ------------------------------------------------
>
> Key: DROOLS-3468
> URL: https://issues.jboss.org/browse/DROOLS-3468
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.16.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: a1 (1).dmn, error.log, server-error.log
>
>
> User is not able to model a DMN model where he declare a Decision service and invoke this Decision Service from other node, because the Decision Service node doesn't allow any incoming nor outgoing connections.
> h2. Acceptance criteria
> - Import attached model *a1*
> - Connect *mood* decision service and *Decision-1* decision node
> - Deploy the model
> - Try to evaluate model via a rest call
> - Check the output json doesn't contain [^error.log]
> - Check the server log doesn't contain [^server-error.log]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (WFLY-11504) Some hibernate tests fail with security on IBM Java 8: HHH000142
by Ondrej Kotek (Jira)
[ https://issues.jboss.org/browse/WFLY-11504?page=com.atlassian.jira.plugin... ]
Ondrej Kotek commented on WFLY-11504:
-------------------------------------
With security manager, the tests fail with IBM Java 8, pass with Oracle Java 8|11 and OpenJDK 8|11.
> Some hibernate tests fail with security on IBM Java 8: HHH000142
> ----------------------------------------------------------------
>
> Key: WFLY-11504
> URL: https://issues.jboss.org/browse/WFLY-11504
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate, Test Suite
> Affects Versions: 16.0.0.Beta1
> Environment: IBM Java 8, build 8.0.5.25 or 8.0.5.26
> Reporter: Ondrej Kotek
> Assignee: Gail Badner
> Priority: Major
> Attachments: org.jboss.as.test.integration.jpa.hibernate.entitytest.EntityTestCase-output.txt
>
>
> Seven hibernate tests fail with security on IBM Java 8, for example:
> {noformat}
> org.hibernate.HibernateException: HHH000142: Bytecode enhancement failed: org.jboss.as.test.integration.jpa.hibernate.Employee
> {noformat}
> Affected test cases:
> * {{org.jboss.as.test.integration.jpa.hibernate.entitytest.EntityTestCase}}
> * {{org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverOnetoManyJoinColumnTest}}
> * {{org.jboss.as.test.integration.jpa.hibernate.envers.basicenverstest.BasicEnversTestCase}}
> * {{org.jboss.as.test.integration.jpa.hibernate.envers.basicselectiveenverstest.BasicSelectiveEnversTestCase}}
> * {{org.jboss.as.test.integration.jpa.hibernate.envers.implementvalidityauditstrategytest.ImplementValidityAuditStrategyTestCase}}
> * {{org.jboss.as.test.integration.jpa.hibernate.envers.validityauditstrategyoninheritancetest.ValidityAuditStrategyonInheritanceTestCase}}
> * {{org.jboss.as.test.integration.jpa.hibernate.sessionfactorytest.SessionFactoryTestCase}}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months