[JBoss JIRA] (WFLY-11518) WAR deployment in 10.1.0 Final is failing itself after its successful deployment
by Srinivas ev (Jira)
[ https://issues.jboss.org/browse/WFLY-11518?page=com.atlassian.jira.plugin... ]
Srinivas ev commented on WFLY-11518:
------------------------------------
Didnt see in Wildfly 15. I dont think it is related to 1687 ticket.
Cannot proceed with Wildfly 15 as my project is at release stage.
> WAR deployment in 10.1.0 Final is failing itself after its successful deployment
> --------------------------------------------------------------------------------
>
> Key: WFLY-11518
> URL: https://issues.jboss.org/browse/WFLY-11518
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.1.0.Final
> Reporter: Srinivas ev
> Assignee: Paul Ferraro
> Priority: Major
> Labels: highavailability
>
> Setup -- Wildfly Clustered ha with pacemaker
> pcs resource enable REST
> This will internally call custom bash scripts as below.
> APP_NAME = myproject-plf-core-fm-rest-api.war
> cd $MYPROJECT_DEPLOYMENT_DIR
> $MYPROJECT_HOME/wildfly/bin/jboss-cli.sh --connect controller=$HOST_NAME:$MYPROJECT_JBOSS_PORT <<EOF
> batch
> deploy ${APP_NAME} --name=${APP_NAME} --runtime-name=${APP_NAME}
> run-batch
> exit
> war is switching with deploy/undeploy as below without the success deployment. This leading to failure of other jars deployment in the cluster.
> 2018/12/14 15:45:49,053+05:30 WARN [org.jboss.as.weld] (MSC service thread 1-8) WFLYWELD0052: Using deployment classloader to load proxy classes for module com.alu.ipprd.myproject.core.fm.common:main. Package-private access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi]
> 2018/12/14 15:45:49,162+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 143) RESTEASY002225: Deploying javax.ws.rs.core.Application: class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
> 2018/12/14 15:45:49,163+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 143) RESTEASY002200: Adding class resource com.alu.ipprd.myproject.core.fm.rest.service.web.service.CorrectiveService from Application class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
> 2018/12/14 15:45:49,169+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 143) WFLYUT0021: Registered web context: /myproject-fm-service
> 2018/12/14 15:45:49,185+05:30 INFO [org.jboss.as.server] (management-handler-thread - 13) WFLYSRV0010: Deployed "myproject-plf-core-fm-rest-api.war" (runtime-name : "myproject-plf-core-fm-rest-api.war")
> 2018/12/14 15:45:59,878+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 143) WFLYUT0022: Unregistered web context: /myproject-fm-service
> 2018/12/14 15:45:59,882+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:45:59,883+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:45:59,932+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment myproject-plf-core-fm-rest-api.war (runtime-name: myproject-plf-core-fm-rest-api.war) in 59ms
> 2018/12/14 15:45:59,944+05:30 WARN [org.jboss.as.controller] (management-handler-thread - 16) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []
> 2018/12/14 15:45:59,950+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 16) WFLYDR0002: Content removed from location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
> 2018/12/14 15:45:59,950+05:30 INFO [org.jboss.as.server] (management-handler-thread - 16) WFLYSRV0009: Undeployed "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
> 2018/12/14 15:46:03,190+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 13) WFLYDR0001: Content added at location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
> 2018/12/14 15:46:03,193+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
> 2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry slf4j-api-1.5.6.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
> 2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry slf4j-jdk14-1.5.6.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
> 2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry concurrent-1.3.2.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
> 2018/12/14 15:46:05,501+05:30 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry antlr-2.7.2.jar in /content/myproject-plf-core-fm-rest-api.war/WEB-INF/lib/jacorb-2.3.1.jbossorg-1.jar does not point to a valid jar for a Class-Path reference.
> 2018/12/14 15:46:05,510+05:30 INFO [org.jboss.as.pojo] (MSC service thread 1-4) WFLYPOJO0001: Found legacy bean/pojo namespace: urn:jboss:bean-deployer:2.0 - might be missing some xml features (potential exceptions).
> 2018/12/14 15:46:05,518+05:30 WARN [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0012: Warning while parsing vfs:/content/myproject-plf-core-fm-rest-api.war/WEB-INF/beans.xml:8 cvc-complex-type.3.2.2: Attribute 'bean-discovery-mode' is not allowed to appear in element 'beans'.
> 2018/12/14 15:46:05,519+05:30 WARN [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0012: Warning while parsing vfs:/content/myproject-plf-core-fm-rest-api.war/WEB-INF/beans.xml:8 cvc-complex-type.3.2.2: Attribute 'version' is not allowed to appear in element 'beans'.
> 2018/12/14 15:46:05,520+05:30 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Read persistence.xml for dacPersistenceUnit
> 2018/12/14 15:46:05,620+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:46:05,620+05:30 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 143) HHH000204: Processing PersistenceUnitInfo [
> name: dacPersistenceUnit
> ...]
> 2018/12/14 15:46:05,623+05:30 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment myproject-plf-core-fm-rest-api.war
> 2018/12/14 15:46:05,684+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 143) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:46:05,685+05:30 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 143) HHH000400: Using dialect: org.hibernate.dialect.MySQLDialect
> 2018/12/14 15:46:05,697+05:30 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 143) Envers integration enabled? : true
> 2018/12/14 15:46:05,795+05:30 INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService Thread Pool -- 143) HHH000397: Using ASTQueryTranslatorFactory
> 2018/12/14 15:46:06,328+05:30 WARN [org.jboss.as.weld] (MSC service thread 1-2) WFLYWELD0052: Using deployment classloader to load proxy classes for module com.alu.ipprd.myproject.core.fm.common:main. Package-private access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi]
> 2018/12/14 15:46:06,474+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 145) RESTEASY002225: Deploying javax.ws.rs.core.Application: class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
> 2018/12/14 15:46:06,475+05:30 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 145) RESTEASY002200: Adding class resource com.alu.ipprd.myproject.core.fm.rest.service.web.service.CorrectiveService from Application class com.alu.ipprd.myproject.core.fm.rest.app.ApplicationConfig$Proxy$_$$_WeldClientProxy
> 2018/12/14 15:46:06,477+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 145) WFLYUT0021: Registered web context: /myproject-fm-service
> 2018/12/14 15:46:06,493+05:30 INFO [org.jboss.as.server] (management-handler-thread - 13) WFLYSRV0010: Deployed "myproject-plf-core-fm-rest-api.war" (runtime-name : "myproject-plf-core-fm-rest-api.war")
> 2018/12/14 15:46:16,895+05:30 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 145) WFLYUT0022: Unregistered web context: /myproject-fm-service
> 2018/12/14 15:46:16,902+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 148) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:46:16,908+05:30 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 148) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'myproject-plf-core-fm-rest-api.war#dacPersistenceUnit'
> 2018/12/14 15:46:16,942+05:30 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment myproject-plf-core-fm-rest-api.war (runtime-name: myproject-plf-core-fm-rest-api.war) in 47ms
> 2018/12/14 15:46:16,956+05:30 WARN [org.jboss.as.controller] (management-handler-thread - 16) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []
> 2018/12/14 15:46:16,962+05:30 INFO [org.jboss.as.repository] (management-handler-thread - 16) WFLYDR0002: Content removed from location /opt/myproject4/MBA_EmFmTm/wildfly/standalone/data/content/8a/3345fb0e0d70b34228d63a1cdaff54de522580/content
> 2018/12/14 15:46:16,962+05:30 INFO [org.jboss.as.server] (management-handler-thread - 16) WFLYSRV0009: Undeployed "myproject-plf-core-fm-rest-api.war" (runtime-name: "myproject-plf-core-fm-rest-api.war")
> Let me know incase require any more information.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (WFLY-11543) EJB transactional method unable to commit when invoked from CDI bean with MariaDB
by Tom Jenkinson (Jira)
[ https://issues.jboss.org/browse/WFLY-11543?page=com.atlassian.jira.plugin... ]
Tom Jenkinson commented on WFLY-11543:
--------------------------------------
Thanks for the logs!
> 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: 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)
7 years
[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
> 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: 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)
7 years
[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)
7 years
[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)
7 years
[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)
7 years