[JBoss JIRA] (WFLY-11251) Dependency version
by Leo Russ (Jira)
Leo Russ created WFLY-11251:
-------------------------------
Summary: Dependency version
Key: WFLY-11251
URL: https://issues.jboss.org/browse/WFLY-11251
Project: WildFly
Issue Type: Feature Request
Components: EE
Affects Versions: 14.0.0.Final
Reporter: Leo Russ
org.eclipse:yasson version in current distribution is 1.0.1, the latest is 1.0.2
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (SWSQE-469) Jenkins Slave for Complex Meshes
by Guilherme Baufaker Rêgo (Jira)
Guilherme Baufaker Rêgo created SWSQE-469:
---------------------------------------------
Summary: Jenkins Slave for Complex Meshes
Key: SWSQE-469
URL: https://issues.jboss.org/browse/SWSQE-469
Project: Kiali QE
Issue Type: Task
Reporter: Guilherme Baufaker Rêgo
Assignee: Guilherme Baufaker Rêgo
Complex Mesh would need to have it is own Jenkins Slave
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11248) EJB Timer is not properly set when the database is different than the defaults
by Filippe Spolti (Jira)
[ https://issues.jboss.org/browse/WFLY-11248?page=com.atlassian.jira.plugin... ]
Filippe Spolti updated WFLY-11248:
----------------------------------
Description:
When using EJB timers the tables will be created during startup based on the database type.
If we set the *database* different than the default names, i.e. mariadb, mysql, it will fail:
timer-store example:
{code:xml}
<timer-service thread-pool-name="default" default-data-store="ejb_timer-EJB_TIMER_ds">
<data-stores>
<file-data-store name="default-file-store" path="timer-service-data" relative-to="jboss.server.data.dir"/>
<database-data-store name="ejb_timer-EJB_TIMER_ds" datasource-jndi-name="java:jboss/datasources/jbpmDS_EJBTimer" database="mysql57" partition="ejb_timer-EJB_TIMER_part" refresh-interval="30000"/>
</data-stores>
</timer-service>
{code}
Issue:
{code:java}
2018-10-25 13:06:57,541 DEBUG [org.jboss.as.ejb3.timer] (MSC service thread 1-5) Database dialect 'mysql57' read from configuration
...
2018-10-25 13:06:58,056 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBossWS 5.2.3.Final (Apache CXF 3.2.5.jbossorg-1)
2018-10-25 13:06:58,222 ERROR [org.jboss.as.ejb3.timer] (MSC service thread 1-5) WFLYEJB0163: Cannot create table for timer persistence: java.sql.SQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'PRIMARY KEY NOT NULL, TIMED_OBJECT_ID VARCHAR NOT NULL, INITIAL_DATE TIMESTAMP, ' at line 1
at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:120)
at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
at com.mysql.cj.jdbc.StatementImpl.executeUpdateInternal(StatementImpl.java:1354)
at com.mysql.cj.jdbc.StatementImpl.executeLargeUpdate(StatementImpl.java:2127)
at com.mysql.cj.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1264)
at com.mysql.cj.jdbc.StatementWrapper.executeUpdate(StatementWrapper.java:628)
at org.jboss.jca.adapters.jdbc.WrappedStatement.executeUpdate(WrappedStatement.java:430)
at org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence.checkDatabase(DatabaseTimerPersistence.java:292)
at org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence.start(DatabaseTimerPersistence.java:166)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:748)
{code}
This issue was spotted on OpenShift environment, the behavior there is to use as the database type on the datastore the same value than the datasource driver name, in this specific case, we we're trying a custom mysql jdbc driver version and named it to mysql57.
was:
When using EJB timers the tables will be created during startup based on the database type.
If we set the *database* different than the default names, i.e. mariadb, mysql, it will fail:
time-store example:
{code:xml}
<timer-service thread-pool-name="default" default-data-store="ejb_timer-EJB_TIMER_ds">
<data-stores>
<file-data-store name="default-file-store" path="timer-service-data" relative-to="jboss.server.data.dir"/>
<database-data-store name="ejb_timer-EJB_TIMER_ds" datasource-jndi-name="java:jboss/datasources/jbpmDS_EJBTimer" database="mysql57" partition="ejb_timer-EJB_TIMER_part" refresh-interval="30000"/>
</data-stores>
</timer-service>
{code}
Issue:
{code:java}
2018-10-25 13:06:57,541 DEBUG [org.jboss.as.ejb3.timer] (MSC service thread 1-5) Database dialect 'mysql57' read from configuration
...
2018-10-25 13:06:58,056 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBossWS 5.2.3.Final (Apache CXF 3.2.5.jbossorg-1)
2018-10-25 13:06:58,222 ERROR [org.jboss.as.ejb3.timer] (MSC service thread 1-5) WFLYEJB0163: Cannot create table for timer persistence: java.sql.SQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'PRIMARY KEY NOT NULL, TIMED_OBJECT_ID VARCHAR NOT NULL, INITIAL_DATE TIMESTAMP, ' at line 1
at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:120)
at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
at com.mysql.cj.jdbc.StatementImpl.executeUpdateInternal(StatementImpl.java:1354)
at com.mysql.cj.jdbc.StatementImpl.executeLargeUpdate(StatementImpl.java:2127)
at com.mysql.cj.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1264)
at com.mysql.cj.jdbc.StatementWrapper.executeUpdate(StatementWrapper.java:628)
at org.jboss.jca.adapters.jdbc.WrappedStatement.executeUpdate(WrappedStatement.java:430)
at org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence.checkDatabase(DatabaseTimerPersistence.java:292)
at org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence.start(DatabaseTimerPersistence.java:166)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:748)
{code}
This issue was spotted on OpenShift environment, the behavior there is to use as the database type on the datastore the same value than the datasource driver name, in this specific case, we we're trying a custom mysql jdbc driver version and named it to mysql57.
> EJB Timer is not properly set when the database is different than the defaults
> ------------------------------------------------------------------------------
>
> Key: WFLY-11248
> URL: https://issues.jboss.org/browse/WFLY-11248
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 14.0.0.Final
> Reporter: Filippe Spolti
> Assignee: Filippe Spolti
> Priority: Major
>
> When using EJB timers the tables will be created during startup based on the database type.
> If we set the *database* different than the default names, i.e. mariadb, mysql, it will fail:
> timer-store example:
> {code:xml}
> <timer-service thread-pool-name="default" default-data-store="ejb_timer-EJB_TIMER_ds">
> <data-stores>
> <file-data-store name="default-file-store" path="timer-service-data" relative-to="jboss.server.data.dir"/>
> <database-data-store name="ejb_timer-EJB_TIMER_ds" datasource-jndi-name="java:jboss/datasources/jbpmDS_EJBTimer" database="mysql57" partition="ejb_timer-EJB_TIMER_part" refresh-interval="30000"/>
> </data-stores>
> </timer-service>
> {code}
> Issue:
> {code:java}
> 2018-10-25 13:06:57,541 DEBUG [org.jboss.as.ejb3.timer] (MSC service thread 1-5) Database dialect 'mysql57' read from configuration
> ...
> 2018-10-25 13:06:58,056 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBossWS 5.2.3.Final (Apache CXF 3.2.5.jbossorg-1)
> 2018-10-25 13:06:58,222 ERROR [org.jboss.as.ejb3.timer] (MSC service thread 1-5) WFLYEJB0163: Cannot create table for timer persistence: java.sql.SQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'PRIMARY KEY NOT NULL, TIMED_OBJECT_ID VARCHAR NOT NULL, INITIAL_DATE TIMESTAMP, ' at line 1
> at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:120)
> at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
> at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
> at com.mysql.cj.jdbc.StatementImpl.executeUpdateInternal(StatementImpl.java:1354)
> at com.mysql.cj.jdbc.StatementImpl.executeLargeUpdate(StatementImpl.java:2127)
> at com.mysql.cj.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1264)
> at com.mysql.cj.jdbc.StatementWrapper.executeUpdate(StatementWrapper.java:628)
> at org.jboss.jca.adapters.jdbc.WrappedStatement.executeUpdate(WrappedStatement.java:430)
> at org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence.checkDatabase(DatabaseTimerPersistence.java:292)
> at org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence.start(DatabaseTimerPersistence.java:166)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> This issue was spotted on OpenShift environment, the behavior there is to use as the database type on the datastore the same value than the datasource driver name, in this specific case, we we're trying a custom mysql jdbc driver version and named it to mysql57.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11226) Maven Wildfly plugin should be working with Java 9+
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11226?page=com.atlassian.jira.plugin... ]
James Perkins commented on WFLY-11226:
--------------------------------------
Note that there is no effect on deployment goals. The {{run}}, {{start}} and {{execute-commands}} goals should be the only ones that have this issue. As a workaround you can add the following to a pom.
{code}
<profile>
<id>java9-plus</id>
<activation>
<jdk>[9,)</jdk>
</activation>
<plugins>
<plugin>
<groupId>org.wildfly.plugins</groupId>
<artifactId>wildfly-maven-plugin</artifactId>
<version>1.3.0.Alpha1-SNAPSHOT</version>
<configuration>
<java-opts>
<java-opt>--add-modules=java.se</java-opt>
</java-opts>
</configuration>
</plugin>
</plugins>
</profile>
{code}
> Maven Wildfly plugin should be working with Java 9+
> ---------------------------------------------------
>
> Key: WFLY-11226
> URL: https://issues.jboss.org/browse/WFLY-11226
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 14.0.1.Final
> Reporter: Michal Jurc
> Assignee: James Perkins
> Priority: Blocker
> Labels: java11
>
> Without the workaround, the following error is thrown by JVM upon starting WildFly/JBoss CLI utilising the plugin:
> {code}21:35:19 [INFO] STANDALONE server is starting up.
> 21:35:20 org.jboss.modules.ModuleNotFoundException: java.se
> 21:35:20 at org.jboss.modules.Module.addPaths(Module.java:1266)
> 21:35:20 at org.jboss.modules.Module.link(Module.java:1622)
> 21:35:20 at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
> 21:35:20 at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
> 21:35:20 at org.jboss.modules.Main.main(Main.java:437){code}
> This is pretty cumbersome and a blocker to migrating application without change of configuration.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11250) Add support for registering a single JVM / Server wide default SSLContext
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFLY-11250?page=com.atlassian.jira.plugin... ]
Darran Lofthouse moved WFCORE-4181 to WFLY-11250:
-------------------------------------------------
Project: WildFly (was: WildFly Core)
Key: WFLY-11250 (was: WFCORE-4181)
Component/s: Documentation
Security
(was: Security)
Fix Version/s: 15.0.0.Alpha1
(was: 7.0.0.Alpha5)
> Add support for registering a single JVM / Server wide default SSLContext
> -------------------------------------------------------------------------
>
> Key: WFLY-11250
> URL: https://issues.jboss.org/browse/WFLY-11250
> Project: WildFly
> Issue Type: Feature Request
> Components: Documentation, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 15.0.0.Alpha1
>
>
> By registering a global SSLContext libraries used within the application server can make use of a managed SSLContext instead of relying on one automatically being created through the standard system properties.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months