[JBoss JIRA] (WFLY-11544) @Stateful EJB passivation-store missing capability references to infinispan resources
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-11544:
-----------------------------------
Summary: @Stateful EJB passivation-store missing capability references to infinispan resources
Key: WFLY-11544
URL: https://issues.jboss.org/browse/WFLY-11544
Project: WildFly
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 15.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
The cache-container and bean-cache attributes should be constrained by capability references to the associated infinispan subsystem resources.
Additionally, these attribute currently allow expressions, but they should not.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (DROOLS-3446) Data type constraints: Basic interaction/workflow
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3446?page=com.atlassian.jira.plugi... ]
Liz Clayton resolved DROOLS-3446.
---------------------------------
Resolution: Done
[~tirelli] I'm marking this Resolved, because design proposals have been created. But actual resolution is pending team review and your approval. :)
> Data type constraints: Basic interaction/workflow
> -------------------------------------------------
>
> Key: DROOLS-3446
> URL: https://issues.jboss.org/browse/DROOLS-3446
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view:
> As a user, I want to be able to set data type constraints for an input value in a Decision Table, so that this constraint is valid _*only*_ in the context of this specific input in this Decision Table.
> * From the Data Types tab:
> As a user I want the ability to define constraints for data type definitions in use within the DMN file.
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (WFLY-11543) EJB transactional method unable to commit when invoked from CDI bean with MariaDB
by Marc Anthony Puca (Jira)
[ https://issues.jboss.org/browse/WFLY-11543?page=com.atlassian.jira.plugin... ]
Marc Anthony Puca edited comment on WFLY-11543 at 12/20/18 5:02 PM:
--------------------------------------------------------------------
Added the server.log with trace for org.wildfly.transaction.client, com.arjuna and org.jboss.as.txn when the issue occurs logs.zip contains 2 files one for each scenario (no transaction and transaction idle)
was (Author: marcanthony):
Added the server.log with trace for org.wildfly.transaction.client, com.arjuna and org.jboss.as.txn when the issue occurs logs.zip contains 2 files once for each scenario
> 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
> 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)
5 years, 4 months
[JBoss JIRA] (WFLY-11543) EJB transactional method unable to commit when invoked from CDI bean with MariaDB
by Marc Anthony Puca (Jira)
[ https://issues.jboss.org/browse/WFLY-11543?page=com.atlassian.jira.plugin... ]
Marc Anthony Puca commented on WFLY-11543:
------------------------------------------
Added the server.log with trace for org.wildfly.transaction.client, com.arjuna and org.jboss.as.txn when the issue occurs logs.zip contains 2 files once for each scenario
> 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
> 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)
5 years, 4 months
[JBoss JIRA] (WFLY-11543) EJB transactional method unable to commit when invoked from CDI bean with MariaDB
by Marc Anthony Puca (Jira)
[ https://issues.jboss.org/browse/WFLY-11543?page=com.atlassian.jira.plugin... ]
Marc Anthony Puca updated WFLY-11543:
-------------------------------------
Attachment: logs.zip
> 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
> 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)
5 years, 4 months
[JBoss JIRA] (WFLY-11543) EJB transactional method unable to commit when invoked from CDI bean with MariaDB
by Alban Chadenas (Jira)
[ https://issues.jboss.org/browse/WFLY-11543?page=com.atlassian.jira.plugin... ]
Alban Chadenas commented on WFLY-11543:
---------------------------------------
Added the server.log with trace for org.wildfly.transaction.client, com.arjuna and org.jboss.as.txn when the issue occurs
> 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
> Attachments: 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)
5 years, 4 months
[JBoss JIRA] (WFLY-11543) EJB transactional method unable to commit when invoked from CDI bean with MariaDB
by Alban Chadenas (Jira)
[ https://issues.jboss.org/browse/WFLY-11543?page=com.atlassian.jira.plugin... ]
Alban Chadenas updated WFLY-11543:
----------------------------------
Attachment: server-trace.zip
> 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
> Attachments: 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)
5 years, 4 months
[JBoss JIRA] (DROOLS-3446) Data type constraints: Basic interaction/workflow
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3446?page=com.atlassian.jira.plugi... ]
Liz Clayton edited comment on DROOLS-3446 at 12/20/18 4:45 PM:
---------------------------------------------------------------
[~tirelli] [~karreiro] [~manstis] I posted proposals, for the A & B input contexts. I'm going to stop work on this specific jira until the team has had a chance to review and discuss.
was (Author: uxdlc):
[~tirelli] [~karreiro] [~manstis] I posted proposals, for the A & B input contexts. I'm going to stop work on this until the team has had a chance to review and discuss.
> Data type constraints: Basic interaction/workflow
> -------------------------------------------------
>
> Key: DROOLS-3446
> URL: https://issues.jboss.org/browse/DROOLS-3446
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view:
> As a user, I want to be able to set data type constraints for an input value in a Decision Table, so that this constraint is valid _*only*_ in the context of this specific input in this Decision Table.
> * From the Data Types tab:
> As a user I want the ability to define constraints for data type definitions in use within the DMN file.
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (DROOLS-3446) Data type constraints: Basic interaction/workflow
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3446?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3446:
-------------------------------------
[~tirelli] [~karreiro] [~manstis] I posted proposals, for the A & B input contexts. I'm going to stop work on this until the team has had a chance to review and discuss.
> Data type constraints: Basic interaction/workflow
> -------------------------------------------------
>
> Key: DROOLS-3446
> URL: https://issues.jboss.org/browse/DROOLS-3446
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view:
> As a user, I want to be able to set data type constraints for an input value in a Decision Table, so that this constraint is valid _*only*_ in the context of this specific input in this Decision Table.
> * From the Data Types tab:
> As a user I want the ability to define constraints for data type definitions in use within the DMN file.
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months