[JBoss JIRA] (DROOLS-5618) DMN DT Analysis advanced 2NF detection
by Matteo Mortari (Jira)
Matteo Mortari created DROOLS-5618:
--------------------------------------
Summary: DMN DT Analysis advanced 2NF detection
Key: DROOLS-5618
URL: https://issues.redhat.com/browse/DROOLS-5618
Project: Drools
Issue Type: Enhancement
Components: dmn engine
Reporter: Matteo Mortari
Assignee: Matteo Mortari
Attachments: image-2020-09-03-11-07-19-348.png
In a table such as
!image-2020-09-03-11-07-19-348.png|thumbnail!
rules 4,5,6 and rules 7,8 should be candidate of 2NF violations.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (JGRP-2230) Multiple discovery protocols without MULTI_PING
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2230?page=com.atlassian.jira.plugin... ]
Bela Ban commented on JGRP-2230:
--------------------------------
Possible impl:
* The top discovery protocol catches the {{FIND_INITIAL_MBRS}} event from above and creates a {{Responses}} object
* Then, it calls {{findMembers()}} in all discovery protocols below it (might be 0)
* When a discovery response is received by the bottom-most discovery protocol, it finds the top discovery protocol and calls {{handleDiscoveryResponse()}} on it.
> Multiple discovery protocols without MULTI_PING
> -----------------------------------------------
>
> Key: JGRP-2230
> URL: https://issues.redhat.com/browse/JGRP-2230
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 5.1
>
>
> Currently, {{MULTI_PING}} is needed to forward discovery requests to multiple discovery protocols. If we change the API in 5.0, and pass a {{Responses}} object down to the discovery protocols, and each discovery protocol forwards discovery requests down (and responses up), and they all add responses to the same {{Responses}} object, then we would not need {{MULTI_PING}} any longer.
> However, this is an API change, so can be done only in 5.0.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (WFLY-13438) Database Timers: instances sporadically fail to start in a cluster
by Gregor Tudan (Jira)
[ https://issues.redhat.com/browse/WFLY-13438?page=com.atlassian.jira.plugi... ]
Gregor Tudan edited comment on WFLY-13438 at 9/3/20 3:34 AM:
-------------------------------------------------------------
[~cfang] Thanks again for looking into this!
We have this issue with the following datasource configuration:
{code:xml}
<xa-datasource jndi-name="java:/datasources/MonitoringDS" pool-name="MonitoringDS" enabled="true">
<xa-datasource-property name="PortNumber">
5432
</xa-datasource-property>
<xa-datasource-property name="DatabaseName">
monitoringdb
</xa-datasource-property>
<xa-datasource-property name="ServerName">
localhost
</xa-datasource-property>
<xa-datasource-property name="SslMode">
require
</xa-datasource-property>
<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
<driver>postgresql</driver>
<security>
<user-name>user</user-name>
<password>password</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
<validate-on-match>false</validate-on-match>
<background-validation>true</background-validation>
<background-validation-millis>10000</background-validation-millis>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
</validation>
<timeout>
<idle-timeout-minutes>10</idle-timeout-minutes>
</timeout>
</xa-datasource>
{code}
The main difference that jumps to the eye is that we are using an XA-Datasource. Could that be an issue?
was (Author: gtudan):
[~cfang] Thanks again for looking into this!
We have this issue with the following datasource configuration:
{code:java}
<xa-datasource jndi-name="java:/datasources/MonitoringDS" pool-name="MonitoringDS" enabled="true">
<xa-datasource-property name="PortNumber">
5432
</xa-datasource-property>
<xa-datasource-property name="DatabaseName">
monitoringdb
</xa-datasource-property>
<xa-datasource-property name="ServerName">
localhost
</xa-datasource-property>
<xa-datasource-property name="SslMode">
require
</xa-datasource-property>
<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
<driver>postgresql</driver>
<security>
<user-name>user</user-name>
<password>password</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
<validate-on-match>false</validate-on-match>
<background-validation>true</background-validation>
<background-validation-millis>10000</background-validation-millis>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
</validation>
<timeout>
<idle-timeout-minutes>10</idle-timeout-minutes>
</timeout>
</xa-datasource>
{code}
The main difference that jumps to the eye is that we are using an XA-Datasource. Could that be an issue?
> Database Timers: instances sporadically fail to start in a cluster
> ------------------------------------------------------------------
>
> Key: WFLY-13438
> URL: https://issues.redhat.com/browse/WFLY-13438
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 19.1.0.Final
> Reporter: Marcos Scholtz
> Assignee: Cheng Fang
> Priority: Major
>
> We use a postgresql database for persistent timers, to control the execution of scheduled tasks in a cluster. It mainly works, but when operating in a cluster and when a server-group is restarted, sometimes individual instances in the cluster fail to start because of an error when reinstating persistent timers.
> Configuration of the Datasource:
> {code}
> <xa-datasource jndi-name="java:/datasources/MonitoringDS" pool-name="MonitoringDS" enabled="true">
> <xa-datasource-property name="ServerName">
> appserver.local
> </xa-datasource-property>
> <xa-datasource-property name="PortNumber">
> 5432
> </xa-datasource-property>
> <xa-datasource-property name="DatabaseName">
> monitoringdb
> </xa-datasource-property>
> <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
> <driver>postgresql</driver>
> <security>
> <user-name>xxx</user-name>
> <password>xxx</password>
> </security>
> </xa-datasource>
> {code}
> Configuration of the timer service:
> {code}
> <timer-service thread-pool-name="default" default-data-store="batch-clustered-store">
> <data-stores>
> <file-data-store name="default-file-store" path="timer-service-data" relative-to="jboss.server.data.dir"/>
> <database-data-store name="batch-clustered-store" datasource-jndi-name="java:/datasources/MonitoringDS" database="'postgresql'" partition="${batch.partition}" refresh-interval="60000" allow-execution="true"/>
> </data-stores>
> </timer-service>
> {code}
> Note we use a system-property on the server-group to determine the partition name.
> Also, we made NO changes to the SQL statements in "timer-sql.properties".
> The timer is generated by a `@Schedule` annotation in an EJB like this:
> {code}
> @Schedule(
> dayOfMonth = "${manual.scheduler.dayofmonth:*}",
> dayOfWeek = "${manual.scheduler.dayofweek:*}",
> hour = "${manual.scheduler.hour:2/6}",
> minute = "${manual.scheduler.minute:2}"
> )
> @TransactionAttribute(TransactionAttributeType.NEVER)
> void doPostboxImport() {
> log.info("Starting Postbox Import");
> BatchRuntime.getJobOperator().start("PostboxImportBatchlet", null);
> }
> {code}
> The error we sporadically get when starting more than one instance at the same time (when all instances try to reinstate timers) is like this:
> {code}
> 14:48:28,117 WARN [com.arjuna.ats.arjuna] (ServerService Thread Pool -- 69) {"tenant": "", "clientId": ""} ARJUNA012078: Abort called illegaly on atomic action 0:ffff7f000001:-27f2652e:5eb2b20f:f
> 14:48:28,118 WARN [org.jboss.as.ejb3.timer] (ServerService Thread Pool -- 69) {"tenant": "", "clientId": ""} WFLYEJB0161: Failed to reinstate timer 'postbox-integration-service.postbox-integration-service.PostboxImport' (id=unavailable) from its persistent state: javax.transaction.NotSupportedException: WFTXN0001: A transaction is already in progress
> at org.wildfly.transaction.client@1.1.9.Final//org.wildfly.transaction.client.ContextTransactionManager.begin(ContextTransactionManager.java:60)
> at org.wildfly.transaction.client@1.1.9.Final//org.wildfly.transaction.client.ContextTransactionManager.begin(ContextTransactionManager.java:54)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.getActivePersistentTimers(TimerServiceImpl.java:984)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.restoreTimers(TimerServiceImpl.java:712)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.activate(TimerServiceImpl.java:223)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.component.EJBComponent.init(EJBComponent.java:595)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.component.stateless.StatelessSessionComponent.init(StatelessSessionComponent.java:110)
> at org.jboss.as.ee@19.1.0.Final//org.jboss.as.ee.component.BasicComponent.start(BasicComponent.java:222)
> at org.jboss.as.ee@19.1.0.Final//org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54)
> at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)
> 14:48:28,153 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 69) {"tenant": "", "clientId": ""} MSC000001: Failed to start service jboss.deployment.unit."postbox-integration-service-E-SNAPSHOT.war".component.PostboxImport.START: org.jboss.msc.service.StartException in service jboss.deployment.unit."postbox-integration-service-E-SNAPSHOT.war".component.PostboxImport.START: java.lang.RuntimeException: java.lang.NullPointerException
> at org.jboss.as.ee@19.1.0.Final//org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57)
> at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Caused by: java.lang.RuntimeException: java.lang.NullPointerException
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.persistTimer(TimerServiceImpl.java:626)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.createCalendarTimer(TimerServiceImpl.java:537)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.loadAutoTimer(TimerServiceImpl.java:388)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.restoreTimers(TimerServiceImpl.java:774)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.activate(TimerServiceImpl.java:223)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.component.EJBComponent.init(EJBComponent.java:595)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.component.stateless.StatelessSessionComponent.init(StatelessSessionComponent.java:110)
> at org.jboss.as.ee@19.1.0.Final//org.jboss.as.ee.component.BasicComponent.start(BasicComponent.java:222)
> at org.jboss.as.ee@19.1.0.Final//org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54)
> ... 8 more
> Caused by: java.lang.NullPointerException
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence.addTimer(DatabaseTimerPersistence.java:336)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.persistTimer(TimerServiceImpl.java:607)
> ... 16 more
> {code}
> The error seems similar to the one described in WFLY-13386, but the stack trace and the steps to reproduce it seem different to me, so I'm not sure if it's the same problem. The problem also existed in Wildfly 14 , we just updated to 19.1 (also hoping that his error would be corrected).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (WFLY-13438) Database Timers: instances sporadically fail to start in a cluster
by Gregor Tudan (Jira)
[ https://issues.redhat.com/browse/WFLY-13438?page=com.atlassian.jira.plugi... ]
Gregor Tudan commented on WFLY-13438:
-------------------------------------
[~cfang] Thanks again for looking into this!
We have this issue with the following datasource configuration:
{code:java}
<xa-datasource jndi-name="java:/datasources/MonitoringDS" pool-name="MonitoringDS" enabled="true">
<xa-datasource-property name="PortNumber">
5432
</xa-datasource-property>
<xa-datasource-property name="DatabaseName">
monitoringdb
</xa-datasource-property>
<xa-datasource-property name="ServerName">
localhost
</xa-datasource-property>
<xa-datasource-property name="SslMode">
require
</xa-datasource-property>
<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
<driver>postgresql</driver>
<security>
<user-name>user</user-name>
<password>password</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
<validate-on-match>false</validate-on-match>
<background-validation>true</background-validation>
<background-validation-millis>10000</background-validation-millis>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
</validation>
<timeout>
<idle-timeout-minutes>10</idle-timeout-minutes>
</timeout>
</xa-datasource>
{code}
The main difference that jumps to the eye is that we are using an XA-Datasource. Could that be an issue?
> Database Timers: instances sporadically fail to start in a cluster
> ------------------------------------------------------------------
>
> Key: WFLY-13438
> URL: https://issues.redhat.com/browse/WFLY-13438
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 19.1.0.Final
> Reporter: Marcos Scholtz
> Assignee: Cheng Fang
> Priority: Major
>
> We use a postgresql database for persistent timers, to control the execution of scheduled tasks in a cluster. It mainly works, but when operating in a cluster and when a server-group is restarted, sometimes individual instances in the cluster fail to start because of an error when reinstating persistent timers.
> Configuration of the Datasource:
> {code}
> <xa-datasource jndi-name="java:/datasources/MonitoringDS" pool-name="MonitoringDS" enabled="true">
> <xa-datasource-property name="ServerName">
> appserver.local
> </xa-datasource-property>
> <xa-datasource-property name="PortNumber">
> 5432
> </xa-datasource-property>
> <xa-datasource-property name="DatabaseName">
> monitoringdb
> </xa-datasource-property>
> <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
> <driver>postgresql</driver>
> <security>
> <user-name>xxx</user-name>
> <password>xxx</password>
> </security>
> </xa-datasource>
> {code}
> Configuration of the timer service:
> {code}
> <timer-service thread-pool-name="default" default-data-store="batch-clustered-store">
> <data-stores>
> <file-data-store name="default-file-store" path="timer-service-data" relative-to="jboss.server.data.dir"/>
> <database-data-store name="batch-clustered-store" datasource-jndi-name="java:/datasources/MonitoringDS" database="'postgresql'" partition="${batch.partition}" refresh-interval="60000" allow-execution="true"/>
> </data-stores>
> </timer-service>
> {code}
> Note we use a system-property on the server-group to determine the partition name.
> Also, we made NO changes to the SQL statements in "timer-sql.properties".
> The timer is generated by a `@Schedule` annotation in an EJB like this:
> {code}
> @Schedule(
> dayOfMonth = "${manual.scheduler.dayofmonth:*}",
> dayOfWeek = "${manual.scheduler.dayofweek:*}",
> hour = "${manual.scheduler.hour:2/6}",
> minute = "${manual.scheduler.minute:2}"
> )
> @TransactionAttribute(TransactionAttributeType.NEVER)
> void doPostboxImport() {
> log.info("Starting Postbox Import");
> BatchRuntime.getJobOperator().start("PostboxImportBatchlet", null);
> }
> {code}
> The error we sporadically get when starting more than one instance at the same time (when all instances try to reinstate timers) is like this:
> {code}
> 14:48:28,117 WARN [com.arjuna.ats.arjuna] (ServerService Thread Pool -- 69) {"tenant": "", "clientId": ""} ARJUNA012078: Abort called illegaly on atomic action 0:ffff7f000001:-27f2652e:5eb2b20f:f
> 14:48:28,118 WARN [org.jboss.as.ejb3.timer] (ServerService Thread Pool -- 69) {"tenant": "", "clientId": ""} WFLYEJB0161: Failed to reinstate timer 'postbox-integration-service.postbox-integration-service.PostboxImport' (id=unavailable) from its persistent state: javax.transaction.NotSupportedException: WFTXN0001: A transaction is already in progress
> at org.wildfly.transaction.client@1.1.9.Final//org.wildfly.transaction.client.ContextTransactionManager.begin(ContextTransactionManager.java:60)
> at org.wildfly.transaction.client@1.1.9.Final//org.wildfly.transaction.client.ContextTransactionManager.begin(ContextTransactionManager.java:54)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.getActivePersistentTimers(TimerServiceImpl.java:984)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.restoreTimers(TimerServiceImpl.java:712)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.activate(TimerServiceImpl.java:223)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.component.EJBComponent.init(EJBComponent.java:595)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.component.stateless.StatelessSessionComponent.init(StatelessSessionComponent.java:110)
> at org.jboss.as.ee@19.1.0.Final//org.jboss.as.ee.component.BasicComponent.start(BasicComponent.java:222)
> at org.jboss.as.ee@19.1.0.Final//org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54)
> at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)
> 14:48:28,153 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 69) {"tenant": "", "clientId": ""} MSC000001: Failed to start service jboss.deployment.unit."postbox-integration-service-E-SNAPSHOT.war".component.PostboxImport.START: org.jboss.msc.service.StartException in service jboss.deployment.unit."postbox-integration-service-E-SNAPSHOT.war".component.PostboxImport.START: java.lang.RuntimeException: java.lang.NullPointerException
> at org.jboss.as.ee@19.1.0.Final//org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57)
> at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Caused by: java.lang.RuntimeException: java.lang.NullPointerException
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.persistTimer(TimerServiceImpl.java:626)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.createCalendarTimer(TimerServiceImpl.java:537)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.loadAutoTimer(TimerServiceImpl.java:388)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.restoreTimers(TimerServiceImpl.java:774)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.activate(TimerServiceImpl.java:223)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.component.EJBComponent.init(EJBComponent.java:595)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.component.stateless.StatelessSessionComponent.init(StatelessSessionComponent.java:110)
> at org.jboss.as.ee@19.1.0.Final//org.jboss.as.ee.component.BasicComponent.start(BasicComponent.java:222)
> at org.jboss.as.ee@19.1.0.Final//org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54)
> ... 8 more
> Caused by: java.lang.NullPointerException
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence.addTimer(DatabaseTimerPersistence.java:336)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.persistTimer(TimerServiceImpl.java:607)
> ... 16 more
> {code}
> The error seems similar to the one described in WFLY-13386, but the stack trace and the steps to reproduce it seem different to me, so I'm not sure if it's the same problem. The problem also existed in Wildfly 14 , we just updated to 19.1 (also hoping that his error would be corrected).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (DROOLS-5434) Incorrect warning about file declaring wrong package
by Magnus Larsson (Jira)
[ https://issues.redhat.com/browse/DROOLS-5434?page=com.atlassian.jira.plug... ]
Magnus Larsson commented on DROOLS-5434:
----------------------------------------
[~mfusco] These problems re-appeared and I did some quick testing. I think it should have been the *packageNameFromFolder* = getRelativePackageName( packageNameForFolder);. Attaching an image of debug output below, _packageNameForFile_ is already containing the correct package (read from the .drl file), but _packageNameForFolder_ contains the spring-boot prefix, thus the warning still appears in the log. Sorry for the delayed response, I just found it again by chance.
!image-2020-09-03-09-20-10-089.png!
> Incorrect warning about file declaring wrong package
> ----------------------------------------------------
>
> Key: DROOLS-5434
> URL: https://issues.redhat.com/browse/DROOLS-5434
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Reporter: Magnus Larsson
> Assignee: Mario Fusco
> Priority: Major
> Attachments: image-2020-09-03-09-20-10-089.png
>
>
> I am running Drools in a Spring-Boot jar and get the following warning statement _File 'BOOT-INF/classes/com/example/test/TEST.drl' is in folder 'BOOT-INF/classes/com/example/test' but declares package 'com.example.test'. It is advised to have a correspondance between package and folder names_. The package name in the drl file is correct, the problem is just that _BOOT-INF.classes._ isn't considered when evaluating if printing the warning or not.
> I have tracked it down to *KieBuilderImpl.java*, method *isFileInKieBase*. The last 2 lines in that method calls:
> {code:java}
> // packageNameForFile prints warning if package in .drl file is not same as flatted directory structure
> // Does not care about SUPPORTED_RESOURCES_ROOTS, thus prints the warning
> String pkgNameForFile = packageNameForFile( fileName, folderNameForFile, !useFolders, file );
> // Does care about SUPPORTED_RESOURCES_ROOTS, so the drl file is loaded
> return isPackageInKieBase( kieBase, pkgNameForFile );
> {code}
> As it is implemented right now, the warning might either be a false-positive (and still get loaded), or the package is wrong (and the file is not loaded).
> Voting to include the SUPPORTED_RESOURCES_ROOTS as valid prefixes when checking if the warning should be printed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (DROOLS-5434) Incorrect warning about file declaring wrong package
by Magnus Larsson (Jira)
[ https://issues.redhat.com/browse/DROOLS-5434?page=com.atlassian.jira.plug... ]
Magnus Larsson updated DROOLS-5434:
-----------------------------------
Attachment: image-2020-09-03-09-20-10-089.png
> Incorrect warning about file declaring wrong package
> ----------------------------------------------------
>
> Key: DROOLS-5434
> URL: https://issues.redhat.com/browse/DROOLS-5434
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Reporter: Magnus Larsson
> Assignee: Mario Fusco
> Priority: Major
> Attachments: image-2020-09-03-09-20-10-089.png
>
>
> I am running Drools in a Spring-Boot jar and get the following warning statement _File 'BOOT-INF/classes/com/example/test/TEST.drl' is in folder 'BOOT-INF/classes/com/example/test' but declares package 'com.example.test'. It is advised to have a correspondance between package and folder names_. The package name in the drl file is correct, the problem is just that _BOOT-INF.classes._ isn't considered when evaluating if printing the warning or not.
> I have tracked it down to *KieBuilderImpl.java*, method *isFileInKieBase*. The last 2 lines in that method calls:
> {code:java}
> // packageNameForFile prints warning if package in .drl file is not same as flatted directory structure
> // Does not care about SUPPORTED_RESOURCES_ROOTS, thus prints the warning
> String pkgNameForFile = packageNameForFile( fileName, folderNameForFile, !useFolders, file );
> // Does care about SUPPORTED_RESOURCES_ROOTS, so the drl file is loaded
> return isPackageInKieBase( kieBase, pkgNameForFile );
> {code}
> As it is implemented right now, the warning might either be a false-positive (and still get loaded), or the package is wrong (and the file is not loaded).
> Voting to include the SUPPORTED_RESOURCES_ROOTS as valid prefixes when checking if the warning should be printed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (WFWIP-346) Bootable JAR - Second bootable JAR fails to package if first uses certain layers
by Jan Kasik (Jira)
[ https://issues.redhat.com/browse/WFWIP-346?page=com.atlassian.jira.plugin... ]
Jan Kasik updated WFWIP-346:
----------------------------
Description:
See the reproducer: https://github.com/honza-kasik/layer-conflict - there are two Maven modules, each configured to run WildFly Maven JAR plugin.
If I run {{mvn clean package -Dversion.org.wildfly.jar.plugin=2.0.0.Beta3}}, bootable JAR for app-one builds but for app-two the build ends up with an error and app-two fails to package:
{noformat}
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-jar-maven-plugin:2.0.0.Beta3:package (default) on project app-two: Provisioning failed: Failed to generate standalone.xml on {
[ERROR] "operation" => "composite",
[ERROR] "address" => [],
[ERROR] "rollback-on-runtime-failure" => true,
[ERROR] "steps" => [
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("interface" => "public")],
[ERROR] "inet-address" => "${jboss.bind.address:127.0.0.1}"
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.bean-validation")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.weld")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.naming")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.ee")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.io")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.undertow")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.jaxrs")]
[ERROR] }
[ERROR] ]
[ERROR] }: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-8" => "WFLYCTL0310: Extension module org.jboss.as.jaxrs not found"}}
{noformat}
Packaging when running {{mvn clean install -Dversion.org.wildfly.jar.plugin=2.0.0.Beta3 -pl app-two}} ends with success. Same for {{app-one}} only.
If I replace layers in app-one with layer {{cloud-server}} both modules build successfully.
was:
See the reproducer: https://github.com/honza-kasik/layer-conflict - there are two Maven modules, each configured to run WildFly Maven JAR plugin.
If I run {{mvn clean package -Dversion.org.wildfly.jar.plugin=2.0.0.Beta3}}, bootable JAR for app-one builds but for app-two the build ends up with an error and app-two fails to package:
{noformat}
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-jar-maven-plugin:2.0.0.Beta3:package (default) on project app-two: Provisioning failed: Failed to generate standalone.xml on {
[ERROR] "operation" => "composite",
[ERROR] "address" => [],
[ERROR] "rollback-on-runtime-failure" => true,
[ERROR] "steps" => [
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("interface" => "public")],
[ERROR] "inet-address" => "${jboss.bind.address:127.0.0.1}"
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.bean-validation")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.weld")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.naming")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.ee")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.io")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.undertow")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.jaxrs")]
[ERROR] }
[ERROR] ]
[ERROR] }: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-8" => "WFLYCTL0310: Extension module org.jboss.as.jaxrs not found"}}
{noformat}
Packaging when running {{mvn clean install -Dversion.org.wildfly.jar.plugin=2.0.0.Beta2 -pl app-two}} ends with success. Same for {{app-one}} only.
If I replace layers in app-one with layer {{cloud-server}} both modules build successfully.
> Bootable JAR - Second bootable JAR fails to package if first uses certain layers
> --------------------------------------------------------------------------------
>
> Key: WFWIP-346
> URL: https://issues.redhat.com/browse/WFWIP-346
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Jan Kasik
> Assignee: Jean Francois Denise
> Priority: Critical
>
> See the reproducer: https://github.com/honza-kasik/layer-conflict - there are two Maven modules, each configured to run WildFly Maven JAR plugin.
> If I run {{mvn clean package -Dversion.org.wildfly.jar.plugin=2.0.0.Beta3}}, bootable JAR for app-one builds but for app-two the build ends up with an error and app-two fails to package:
> {noformat}
> [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-jar-maven-plugin:2.0.0.Beta3:package (default) on project app-two: Provisioning failed: Failed to generate standalone.xml on {
> [ERROR] "operation" => "composite",
> [ERROR] "address" => [],
> [ERROR] "rollback-on-runtime-failure" => true,
> [ERROR] "steps" => [
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("interface" => "public")],
> [ERROR] "inet-address" => "${jboss.bind.address:127.0.0.1}"
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.wildfly.extension.bean-validation")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.weld")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.naming")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.ee")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.wildfly.extension.io")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.wildfly.extension.undertow")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.jaxrs")]
> [ERROR] }
> [ERROR] ]
> [ERROR] }: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-8" => "WFLYCTL0310: Extension module org.jboss.as.jaxrs not found"}}
> {noformat}
> Packaging when running {{mvn clean install -Dversion.org.wildfly.jar.plugin=2.0.0.Beta3 -pl app-two}} ends with success. Same for {{app-one}} only.
> If I replace layers in app-one with layer {{cloud-server}} both modules build successfully.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (WFWIP-346) Bootable JAR - Second bootable JAR fails to package if first uses certain layers
by Jan Kasik (Jira)
[ https://issues.redhat.com/browse/WFWIP-346?page=com.atlassian.jira.plugin... ]
Jan Kasik updated WFWIP-346:
----------------------------
Description:
See the reproducer: https://github.com/honza-kasik/layer-conflict - there are two Maven modules, each configured to run WildFly Maven JAR plugin.
If I run {{mvn clean package -Dversion.org.wildfly.jar.plugin=2.0.0.Beta3}}, bootable JAR for app-one builds but for app-two the build ends up with an error and app-two fails to package:
{noformat}
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-jar-maven-plugin:2.0.0.Beta3:package (default) on project app-two: Provisioning failed: Failed to generate standalone.xml on {
[ERROR] "operation" => "composite",
[ERROR] "address" => [],
[ERROR] "rollback-on-runtime-failure" => true,
[ERROR] "steps" => [
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("interface" => "public")],
[ERROR] "inet-address" => "${jboss.bind.address:127.0.0.1}"
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.bean-validation")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.weld")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.naming")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.ee")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.io")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.undertow")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.jaxrs")]
[ERROR] }
[ERROR] ]
[ERROR] }: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-8" => "WFLYCTL0310: Extension module org.jboss.as.jaxrs not found"}}
{noformat}
Packaging when running {{mvn clean install -Dversion.org.wildfly.jar.plugin=2.0.0.Beta2 -pl app-two}} ends with success. Same for {{app-one}} only.
If I replace layers in app-one with layer {{cloud-server}} both modules build successfully.
was:
See the reproducer: https://github.com/honza-kasik/layer-conflict - there are two Maven modules, each configured to run WildFly Maven JAR plugin.
If I run {{mvn clean package -Dversion.org.wildfly.jar.plugin=2.0.0.Beta3}}, bootable JAR for app-one builds but for app-two the build ends up with an error and app-two fails to package:
{noformat}
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-jar-maven-plugin:2.0.0.Beta3:package (default) on project app-two: Provisioning failed: Failed to generate standalone.xml on {
[ERROR] "operation" => "composite",
[ERROR] "address" => [],
[ERROR] "rollback-on-runtime-failure" => true,
[ERROR] "steps" => [
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("interface" => "public")],
[ERROR] "inet-address" => "${jboss.bind.address:127.0.0.1}"
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.bean-validation")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.weld")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.naming")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.ee")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.io")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.undertow")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.jaxrs")]
[ERROR] }
[ERROR] ]
[ERROR] }: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-8" => "WFLYCTL0310: Extension module org.jboss.as.jaxrs not found"}}
{noformat}
Packaging when running {{mvn clean install -Dversion.org.wildfly.jar.plugin=2.0.0.Beta2 -pl app-two}} ends with success. Same for {{app-one}} only.
If I replace layers in app-one with layer {{cloud-server}} both modules builds successfully.
> Bootable JAR - Second bootable JAR fails to package if first uses certain layers
> --------------------------------------------------------------------------------
>
> Key: WFWIP-346
> URL: https://issues.redhat.com/browse/WFWIP-346
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Jan Kasik
> Assignee: Jean Francois Denise
> Priority: Critical
>
> See the reproducer: https://github.com/honza-kasik/layer-conflict - there are two Maven modules, each configured to run WildFly Maven JAR plugin.
> If I run {{mvn clean package -Dversion.org.wildfly.jar.plugin=2.0.0.Beta3}}, bootable JAR for app-one builds but for app-two the build ends up with an error and app-two fails to package:
> {noformat}
> [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-jar-maven-plugin:2.0.0.Beta3:package (default) on project app-two: Provisioning failed: Failed to generate standalone.xml on {
> [ERROR] "operation" => "composite",
> [ERROR] "address" => [],
> [ERROR] "rollback-on-runtime-failure" => true,
> [ERROR] "steps" => [
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("interface" => "public")],
> [ERROR] "inet-address" => "${jboss.bind.address:127.0.0.1}"
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.wildfly.extension.bean-validation")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.weld")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.naming")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.ee")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.wildfly.extension.io")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.wildfly.extension.undertow")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.jaxrs")]
> [ERROR] }
> [ERROR] ]
> [ERROR] }: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-8" => "WFLYCTL0310: Extension module org.jboss.as.jaxrs not found"}}
> {noformat}
> Packaging when running {{mvn clean install -Dversion.org.wildfly.jar.plugin=2.0.0.Beta2 -pl app-two}} ends with success. Same for {{app-one}} only.
> If I replace layers in app-one with layer {{cloud-server}} both modules build successfully.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (WFWIP-346) Bootable JAR - Second bootable JAR fails to package if first uses certain layers
by Fabio Burzigotti (Jira)
[ https://issues.redhat.com/browse/WFWIP-346?page=com.atlassian.jira.plugin... ]
Fabio Burzigotti updated WFWIP-346:
-----------------------------------
Summary: Bootable JAR - Second bootable JAR fails to package if first uses certain layers (was: Second bootable JAR fails to package if first uses certain layers)
> Bootable JAR - Second bootable JAR fails to package if first uses certain layers
> --------------------------------------------------------------------------------
>
> Key: WFWIP-346
> URL: https://issues.redhat.com/browse/WFWIP-346
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Jan Kasik
> Assignee: Jean Francois Denise
> Priority: Critical
>
> See the reproducer: https://github.com/honza-kasik/layer-conflict - there are two Maven modules, each configured to run WildFly Maven JAR plugin.
> If I run {{mvn clean package -Dversion.org.wildfly.jar.plugin=2.0.0.Beta3}}, bootable JAR for app-one builds but for app-two the build ends up with an error and app-two fails to package:
> {noformat}
> [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-jar-maven-plugin:2.0.0.Beta3:package (default) on project app-two: Provisioning failed: Failed to generate standalone.xml on {
> [ERROR] "operation" => "composite",
> [ERROR] "address" => [],
> [ERROR] "rollback-on-runtime-failure" => true,
> [ERROR] "steps" => [
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("interface" => "public")],
> [ERROR] "inet-address" => "${jboss.bind.address:127.0.0.1}"
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.wildfly.extension.bean-validation")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.weld")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.naming")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.ee")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.wildfly.extension.io")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.wildfly.extension.undertow")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.jaxrs")]
> [ERROR] }
> [ERROR] ]
> [ERROR] }: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-8" => "WFLYCTL0310: Extension module org.jboss.as.jaxrs not found"}}
> {noformat}
> Packaging when running {{mvn clean install -Dversion.org.wildfly.jar.plugin=2.0.0.Beta2 -pl app-two}} ends with success. Same for {{app-one}} only.
> If I replace layers in app-one with layer {{cloud-server}} both modules builds successfully.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (WFWIP-346) Second bootable JAR fails to package if first uses certain layers
by Jan Kasik (Jira)
Jan Kasik created WFWIP-346:
-------------------------------
Summary: Second bootable JAR fails to package if first uses certain layers
Key: WFWIP-346
URL: https://issues.redhat.com/browse/WFWIP-346
Project: WildFly WIP
Issue Type: Bug
Reporter: Jan Kasik
Assignee: Jean Francois Denise
See the reproducer: https://github.com/honza-kasik/layer-conflict - there are two Maven modules, each configured to run WildFly Maven JAR plugin.
If I run {{mvn clean package -Dversion.org.wildfly.jar.plugin=2.0.0.Beta3}}, bootable JAR for app-one builds but for app-two the build ends up with an error and app-two fails to package:
{noformat}
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-jar-maven-plugin:2.0.0.Beta3:package (default) on project app-two: Provisioning failed: Failed to generate standalone.xml on {
[ERROR] "operation" => "composite",
[ERROR] "address" => [],
[ERROR] "rollback-on-runtime-failure" => true,
[ERROR] "steps" => [
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("interface" => "public")],
[ERROR] "inet-address" => "${jboss.bind.address:127.0.0.1}"
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.bean-validation")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.weld")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.naming")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.ee")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.io")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.undertow")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.jaxrs")]
[ERROR] }
[ERROR] ]
[ERROR] }: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-8" => "WFLYCTL0310: Extension module org.jboss.as.jaxrs not found"}}
{noformat}
Packaging when running {{mvn clean install -Dversion.org.wildfly.jar.plugin=2.0.0.Beta2 -pl app-two}} ends with success. Same for {{app-one}} only.
If I replace layers in app-one with layer {{cloud-server}} both modules builds successfully.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month