[JBoss JIRA] (WFCORE-1715) HostProcessReloadHandler does not reset the HostRunningModeControl's restartMode
by Yeray Santana Borges (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1715?page=com.atlassian.jira.plugi... ]
Yeray Santana Borges edited comment on WFCORE-1715 at 8/28/16 8:59 AM:
-----------------------------------------------------------------------
I have arrived to these conclusions after taking a look to the code around this issue:
# It seems that the RestartMode has already a default value, created in the constructor of HostRunningModeControl. It's initialized to RestartMode.SERVERS in a single point: HostControllerEnvironment L298. Its setter is only invoked in HostProcessReloadHandler#reloadInitiated L145 so it seems that currently the default value used is RestartMode.SERVERS.
# The possible "problem" could be if the user executes a reload(restartServers=false), this operation will let the HostRunningModeControl.RestartMode equals to RestartMode.HC_ONLY because it's never reverted to its default RestartMode.SERVERS after reloading the HC. The consequence I have been able to see is a minor different order when shutdown operation is executed after HC reload:
Case 1:
/host=master:reload(restart-servers=false)
/host=master:shutdown(restart=true)
Case 2:
/host=master:reload(restart-servers=true)
/host=master:shutdown(restart=true)
Shutdown op on case 1, servers are unregistered from the HC, the HC is stopped and at the end the servers are stopped.
Shutdown op on case 2, servers are unregistered from HC, servers are stopped and at the end the HC is stopped.
Whit the change in this issue, reverting RestartMode to its default after a HC reload, the sequence of actions of shutdown operation after a reload (with restart-servers true or false) will be the same and will be the sequences on case 2.
[~brian.stansberry] About the default timeout, yes, I can confirm that it will be by default is 0 (code about timeout is in WFCORE-1427)
was (Author: yersan):
I have arrived to these conclusions after taking a look to the code around this issue:
# It seems that the RestartMode has already a default value, created in the constructor of HostRunningModeControl. It's initialized to RestartMode.SERVERS in a single point: HostControllerEnvironment L298. Its setter is only invoked in HostProcessReloadHandler#reloadInitiated L145 so it seems that currently the default value used is RestartMode.SERVERS.
# The possible "problem" could be if the user executes a reload(restartServers=false), this operation will let the HostRunningModeControl.RestartMode equals to RestartMode.HC_ONLY because it's never reverted to its default RestartMode.SERVERS after reloading the HC. The consequence I has been able to see is a minor different order when shutdown operation is executed after HC reload:
Case 1:
/host=master:reload(restart-servers=false)
/host=master:shutdown(restart=true)
Case 2:
/host=master:reload(restart-servers=true)
/host=master:shutdown(restart=true)
Shutdown op on case 1, servers are unregistered from the HC, the HC is stopped and at the end the server are stopped.
Shutdown op on case 2, servers are unregistered from HC, servers are stopped and at the end the HC is stopped.
Whit the change in this issue, reverting RestartMode to its default after a HC reload, the sequence of actions of shutdown operation after a reload (with restart-servers true or false) will be the same and will be the sequences on case 2.
[~brian.stansberry] About the default timeout, yes, I can confirm that it will be by default is 0 (code about timeout is in WFCORE-1427)
> HostProcessReloadHandler does not reset the HostRunningModeControl's restartMode
> --------------------------------------------------------------------------------
>
> Key: WFCORE-1715
> URL: https://issues.jboss.org/browse/WFCORE-1715
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.2.0.Final, 3.0.0.Alpha5
> Reporter: Yeray Santana Borges
> Assignee: Yeray Santana Borges
> Fix For: 3.0.0.Alpha6
>
>
> The ReloadContext created by HostProcessReloadHandler sets the HostRunningModeControl's restartMode but then it never gets restored to the default value. The doReload() method of the ReloadContext should restore it. This ensures the ServerInventoryService.stop() only uses the value set by HostProcessReloadHandler once, for that one reload.
> A concern here is that ServerInventoryService only goes into its "shutdownServers" logic if the restartMode == RestartMode.SERVERS. Which, due to this bug, it will be following any HC reload. But if we restore the default value of restartMode, that is null, and null != RestartMode.SERVERS. So the ""shutdownServers" logic will no longer kick in. But should it? Should the default value of restartMode be "null"? Or should it be RestartMode.SERVERS? If we change the default from null, then the behavior when no reload has happened will change.
> Basically we need to decide whether the "shutdownServers" logic should happen by default.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (DROOLS-1221) Add fail-safe and scalability functionality to the Drools (CEP) rules engine
by Youcef HILEM (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1221?page=com.atlassian.jira.plugi... ]
Youcef HILEM commented on DROOLS-1221:
--------------------------------------
See also : A scalable, highly available, CEP architecture (https://github.com/redhat-italy/hacep)
> Add fail-safe and scalability functionality to the Drools (CEP) rules engine
> ----------------------------------------------------------------------------
>
> Key: DROOLS-1221
> URL: https://issues.jboss.org/browse/DROOLS-1221
> Project: Drools
> Issue Type: Feature Request
> Components: core engine
> Affects Versions: 6.4.0.Final
> Environment: Drools (CEP) Rule engine 6.4.0.Final
> Reporter: Tom Pijl
> Assignee: Mario Fusco
>
> The Drools Rule engine is currently not fail-safe and scalable which is a requirement for Cloud deployment.
> Add a possibility to persist the state of the working memory after each state change (perhaps linked to the fireAllRules()?) and related to that the possibility to restore the state in case of a crash (fail-safe requirement).
> This persistent state store can also be used to synchronize multiple engine instances (scalability requirement).
> Of course this has major impact on the performance of the engine, but it is the only way to make the engine useful in a multi-tenant Cloud environment
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFLY-7018) Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
by Mark S (JIRA)
[ https://issues.jboss.org/browse/WFLY-7018?page=com.atlassian.jira.plugin.... ]
Mark S updated WFLY-7018:
-------------------------
Steps to Reproduce:
h3. The following Wildfly 10.0.0.Final Datasource configuration via CLI...
{code}
# Via CLI
# cd C:\dev\tools\wildfly-10.1.0.Final\
# bin\jboss-cli.bat
module add \
--name=org.postgres \
--resources=C:\Users\user\Downloads\postgresql-9.4.1209.jar \
--dependencies=javax.api,javax.transaction.api
/subsystem=datasources/jdbc-driver=postgres:add( \
driver-name="postgres", \
driver-module-name="org.postgres", \
driver-class-name=org.postgresql.Driver, \
driver-datasource-class-name=org.postgresql.ds.PGSimpleDataSource, \
driver-xa-datasource-class-name=org.postgresql.xa.PGXADataSource )
data-source add \
--name=Postgres_MY_APP_DS \
--driver-name=postgres \
--jndi-name=java:/MY_APP_DS \
--valid-connection-checker-class-name=org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker \
--exception-sorter-class-name=org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter \
--connection-url=jdbc:postgresql://localhost:5432/myapp \
--user-name=myapp \
--password=myapp
{code}
*... will produce the following exception in Wildfly 10.1.0.Final:*
{code}
{"WFLYCTL0080: Failed services" => {"org.wildfly.data-source.Postgres_MY_APP_DS" => "org.jboss.msc.service.StartException in service org.wildfly.data-source.Postgres_MY_APP_DS: WFLYJCA0033: Error during the deployment of Postgres_MY_APP_DS
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"},"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.data-source.Postgres_MY_APP_DS"],"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}
{code}
h3. The following Wildfly 10.0.0.Final Datasource configuration via XML (standalone-full.xml)...
{code:xml}
<subsystem xmlns="urn:jboss:domain:datasources:4.0">
<datasources>
<datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS">
<connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
<driver>postgres</driver>
<security>
<user-name>myapp</user-name>
<password>myapp</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
</validation>
</datasource>
<drivers>
<driver name="postgres" module="org.postgres">
<driver-class>org.postgresql.Driver</driver-class>
<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
<datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
</driver>
</drivers>
</datasources>
</subsystem>
{code}
*... will produce the following Stacktrace on Wildfly 10.1.0.Final Application Server Startup:*
{code}
14:16:16,583 ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-5) Error during the deployment of java:/MY_APP_DS: javax.resource.ResourceException: IJ031103: At least one connection property must be defined for datasource-class: org.postgresql.ds.PGSimpleDataSource
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createConnectionFactory(LocalManagedConnectionFactory.java:108)
at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:772)
at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:312)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:371)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:149)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
14:16:16,588 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service org.wildfly.data-source.Postgres_MY_APP_DS: org.jboss.msc.service.StartException in service org.wildfly.data-source.Postgres_MY_APP_DS: WFLYJCA0033: Error during the deployment of Postgres_MY_APP_DS
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:163)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:151)
... 5 more
.....
14:16:17,470 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "Postgres_MY_APP_DS")
]) - failure description: {
"WFLYCTL0080: Failed services" => {"org.wildfly.data-source.Postgres_MY_APP_DS" => "org.jboss.msc.service.StartException in service org.wildfly.data-source.Postgres_MY_APP_DS: WFLYJCA0033: Error during the deployment of Postgres_MY_APP_DS
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"},
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.data-source.Postgres_MY_APP_DS"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
}
14:16:17,473 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "Postgres_MY_APP_DS")
]) - failure description: {
"WFLYCTL0080: Failed services" => {"org.wildfly.data-source.Postgres_MY_APP_DS" => "org.jboss.msc.service.StartException in service org.wildfly.data-source.Postgres_MY_APP_DS: WFLYJCA0033: Error during the deployment of Postgres_MY_APP_DS
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"},
"WFLYCTL0412: Required services that are not installed:" => [
"org.wildfly.data-source.Postgres_MY_APP_DS",
"org.wildfly.data-source.Postgres_MY_APP_DS"
],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
}
{code}
h3. Other examples
The following configuration is similar and would also fail:
* http://www.nailedtothex.org/roller/kyle/entry/registering-postgresql-jdbc...
was:
h3. The following Wildfly 10.0.0.Final Datasource configuration via CLI...
{code}
# Via CLI
# cd C:\dev\tools\wildfly-10.1.0.Final\
# bin\jboss-cli.bat
module add \
--name=org.postgres \
--resources=C:\Users\user\Downloads\postgresql-9.4.1209.jar \
--dependencies=javax.api,javax.transaction.api
/subsystem=datasources/jdbc-driver=postgres:add( \
driver-name="postgres", \
driver-module-name="org.postgres", \
driver-class-name=org.postgresql.Driver, \
driver-datasource-class-name=org.postgresql.ds.PGSimpleDataSource, \
driver-xa-datasource-class-name=org.postgresql.xa.PGXADataSource )
data-source add \
--name=Postgres_MY_APP_DS \
--driver-name=postgres \
--jndi-name=java:/MY_APP_DS \
--valid-connection-checker-class-name=org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker \
--exception-sorter-class-name=org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter \
--connection-url=jdbc:postgresql://localhost:5432/myapp \
--user-name=myapp \
--password=myapp
{code}
*... will produce the following exception in Wildfly 10.1.0.Final:*
{code}
{"WFLYCTL0080: Failed services" => {"org.wildfly.data-source.Postgres_MY_APP_DS" => "org.jboss.msc.service.StartException in service org.wildfly.data-source.Postgres_MY_APP_DS: WFLYJCA0033: Error during the deployment of Postgres_MY_APP_DS
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"},"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.data-source.Postgres_MY_APP_DS"],"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}
{code}
h3. The following Wildfly 10.0.0.Final Datasource configuration via XML (standalone-full.xml)...
{code:xml}
<subsystem xmlns="urn:jboss:domain:datasources:4.0">
<datasources>
<datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS">
<connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
<driver>postgres</driver>
<security>
<user-name>myapp</user-name>
<password>myapp</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
</validation>
</datasource>
<drivers>
<driver name="postgres" module="org.postgres">
<driver-class>org.postgresql.Driver</driver-class>
<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
<datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
</driver>
</drivers>
</datasources>
</subsystem>
{code}
*... will produce the following Stacktrace on Wildfly 10.1.0.Final Application Server Startup:*
{code}
14:16:16,583 ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-5) Error during the deployment of java:/MY_APP_DS: javax.resource.ResourceException: IJ031103: At least one connection property must be defined for datasource-class: org.postgresql.ds.PGSimpleDataSource
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createConnectionFactory(LocalManagedConnectionFactory.java:108)
at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:772)
at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:312)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:371)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:149)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
14:16:16,588 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service org.wildfly.data-source.Postgres_MY_APP_DS: org.jboss.msc.service.StartException in service org.wildfly.data-source.Postgres_MY_APP_DS: WFLYJCA0033: Error during the deployment of Postgres_MY_APP_DS
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:163)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:151)
... 5 more
.....
14:16:17,470 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "Postgres_MY_APP_DS")
]) - failure description: {
"WFLYCTL0080: Failed services" => {"org.wildfly.data-source.Postgres_MY_APP_DS" => "org.jboss.msc.service.StartException in service org.wildfly.data-source.Postgres_MY_APP_DS: WFLYJCA0033: Error during the deployment of Postgres_MY_APP_DS
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"},
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.data-source.Postgres_MY_APP_DS"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
}
14:16:17,473 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "Postgres_MY_APP_DS")
]) - failure description: {
"WFLYCTL0080: Failed services" => {"org.wildfly.data-source.Postgres_MY_APP_DS" => "org.jboss.msc.service.StartException in service org.wildfly.data-source.Postgres_MY_APP_DS: WFLYJCA0033: Error during the deployment of Postgres_MY_APP_DS
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"},
"WFLYCTL0412: Required services that are not installed:" => [
"org.wildfly.data-source.Postgres_MY_APP_DS",
"org.wildfly.data-source.Postgres_MY_APP_DS"
],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
}
{code}
h3. Other examples
The following configuration is similar and would also fail:
* http://www.nailedtothex.org/roller/kyle/entry/registering-postgresql-jdbc...
* http://www.ironjacamar.org/doc/userguide/1.2/en-US/html/apc.html#ex_datas...
> Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
> -------------------------------------------------------------------
>
> Key: WFLY-7018
> URL: https://issues.jboss.org/browse/WFLY-7018
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.1.0.Final
> Reporter: Mark S
> Assignee: Jesper Pedersen
>
> My current Wildfly 10.0.0.Final (Non-XA) Datasource configuration will not work for Wildfly 10.1.0.Final. See the "Steps to Reproduce" section.
> The stacktrace points to here:
> * https://source.jboss.org/browse/IronJacamar/adapters/src/main/java/org/jb...
> * https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.3.4.Final/a...
> h3. The work-around
> h3. Wildfly 10.1.0.Final Datasource configuration via CLI
> {code}
> # No parameter to set a connection property value.
> {code}
> h3. Wildfly 10.1.0.Final Datasource configuration via XML (standalone-full.xml)
> Note the addition of {{<connection-property name="databaseName">myapp</connection-property>}}
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:datasources:4.0">
> <datasources>
> <datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS">
> <connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
> <connection-property name="databaseName">myapp</connection-property>
> <driver>postgres</driver>
> <security>
> <user-name>myapp</user-name>
> <password>myapp</password>
> </security>
> <validation>
> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
> </validation>
> </datasource>
> <drivers>
> <driver name="postgres" module="org.postgres">
> <driver-class>org.postgresql.Driver</driver-class>
> <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
> <datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
> </driver>
> </drivers>
> </datasources>
> </subsystem>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFLY-7018) Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
by Mark S (JIRA)
[ https://issues.jboss.org/browse/WFLY-7018?page=com.atlassian.jira.plugin.... ]
Mark S updated WFLY-7018:
-------------------------
Steps to Reproduce:
h3. The following Wildfly 10.0.0.Final Datasource configuration via CLI...
{code}
# Via CLI
# cd C:\dev\tools\wildfly-10.1.0.Final\
# bin\jboss-cli.bat
module add \
--name=org.postgres \
--resources=C:\Users\user\Downloads\postgresql-9.4.1209.jar \
--dependencies=javax.api,javax.transaction.api
/subsystem=datasources/jdbc-driver=postgres:add( \
driver-name="postgres", \
driver-module-name="org.postgres", \
driver-class-name=org.postgresql.Driver, \
driver-datasource-class-name=org.postgresql.ds.PGSimpleDataSource, \
driver-xa-datasource-class-name=org.postgresql.xa.PGXADataSource )
data-source add \
--name=Postgres_MY_APP_DS \
--driver-name=postgres \
--jndi-name=java:/MY_APP_DS \
--valid-connection-checker-class-name=org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker \
--exception-sorter-class-name=org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter \
--connection-url=jdbc:postgresql://localhost:5432/myapp \
--user-name=myapp \
--password=myapp
{code}
*... will produce the following exception in Wildfly 10.1.0.Final:*
{code}
{"WFLYCTL0080: Failed services" => {"org.wildfly.data-source.Postgres_MY_APP_DS" => "org.jboss.msc.service.StartException in service org.wildfly.data-source.Postgres_MY_APP_DS: WFLYJCA0033: Error during the deployment of Postgres_MY_APP_DS
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"},"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.data-source.Postgres_MY_APP_DS"],"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}
{code}
h3. The following Wildfly 10.0.0.Final Datasource configuration via XML (standalone-full.xml)...
{code:xml}
<subsystem xmlns="urn:jboss:domain:datasources:4.0">
<datasources>
<datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS">
<connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
<driver>postgres</driver>
<security>
<user-name>myapp</user-name>
<password>myapp</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
</validation>
</datasource>
<drivers>
<driver name="postgres" module="org.postgres">
<driver-class>org.postgresql.Driver</driver-class>
<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
<datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
</driver>
</drivers>
</datasources>
</subsystem>
{code}
*... will produce the following Stacktrace on Wildfly 10.1.0.Final Application Server Startup:*
{code}
14:16:16,583 ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-5) Error during the deployment of java:/MY_APP_DS: javax.resource.ResourceException: IJ031103: At least one connection property must be defined for datasource-class: org.postgresql.ds.PGSimpleDataSource
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createConnectionFactory(LocalManagedConnectionFactory.java:108)
at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:772)
at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:312)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:371)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:149)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
14:16:16,588 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service org.wildfly.data-source.Postgres_MY_APP_DS: org.jboss.msc.service.StartException in service org.wildfly.data-source.Postgres_MY_APP_DS: WFLYJCA0033: Error during the deployment of Postgres_MY_APP_DS
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:163)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:151)
... 5 more
.....
14:16:17,470 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "Postgres_MY_APP_DS")
]) - failure description: {
"WFLYCTL0080: Failed services" => {"org.wildfly.data-source.Postgres_MY_APP_DS" => "org.jboss.msc.service.StartException in service org.wildfly.data-source.Postgres_MY_APP_DS: WFLYJCA0033: Error during the deployment of Postgres_MY_APP_DS
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"},
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.data-source.Postgres_MY_APP_DS"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
}
14:16:17,473 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "Postgres_MY_APP_DS")
]) - failure description: {
"WFLYCTL0080: Failed services" => {"org.wildfly.data-source.Postgres_MY_APP_DS" => "org.jboss.msc.service.StartException in service org.wildfly.data-source.Postgres_MY_APP_DS: WFLYJCA0033: Error during the deployment of Postgres_MY_APP_DS
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"},
"WFLYCTL0412: Required services that are not installed:" => [
"org.wildfly.data-source.Postgres_MY_APP_DS",
"org.wildfly.data-source.Postgres_MY_APP_DS"
],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
}
{code}
h3. Other examples
The following configuration is similar and would also fail:
* http://www.nailedtothex.org/roller/kyle/entry/registering-postgresql-jdbc...
* http://www.ironjacamar.org/doc/userguide/1.2/en-US/html/apc.html#ex_datas...
was:
h3. The following Wildfly 10.0.0.Final Datasource configuration via CLI...
{code}
# Via CLI
# cd C:\dev\tools\wildfly-10.1.0.Final\
# bin\jboss-cli.bat
module add \
--name=org.postgres \
--resources=C:\Users\user\Downloads\postgresql-9.4.1209.jar \
--dependencies=javax.api,javax.transaction.api
/subsystem=datasources/jdbc-driver=postgres:add( \
driver-name="postgres", \
driver-module-name="org.postgres", \
driver-class-name=org.postgresql.Driver, \
driver-datasource-class-name=org.postgresql.ds.PGSimpleDataSource, \
driver-xa-datasource-class-name=org.postgresql.xa.PGXADataSource )
data-source add \
--name=Postgres_MY_APP_DS \
--driver-name=postgres \
--jndi-name=java:/MY_APP_DS \
--valid-connection-checker-class-name=org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker \
--exception-sorter-class-name=org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter \
--connection-url=jdbc:postgresql://localhost:5432/myapp \
--user-name=myapp \
--password=myapp
{code}
*... will produce the following exception in Wildfly 10.1.0.Final:*
{code}
{"WFLYCTL0080: Failed services" => {"org.wildfly.data-source.Postgres_MY_APP_DS" => "org.jboss.msc.service.StartException in service org.wildfly.data-source.Postgres_MY_APP_DS: WFLYJCA0033: Error during the deployment of Postgres_MY_APP_DS
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"},"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.data-source.Postgres_MY_APP_DS"],"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}
{code}
h3. The following Wildfly 10.0.0.Final Datasource configuration via XML (standalone-full.xml)...
{code:xml}
<subsystem xmlns="urn:jboss:domain:datasources:4.0">
<datasources>
<datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS">
<connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
<driver>postgres</driver>
<security>
<user-name>myapp</user-name>
<password>myapp</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
</validation>
</datasource>
<drivers>
<driver name="postgres" module="org.postgres">
<driver-class>org.postgresql.Driver</driver-class>
<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
<datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
</driver>
</drivers>
</datasources>
</subsystem>
{code}
*... will produce the following Stacktrace on Wildfly 10.1.0.Final Application Server Startup:*
{code}
14:16:16,583 ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-5) Error during the deployment of java:/MY_APP_DS: javax.resource.ResourceException: IJ031103: At least one connection property must be defined for datasource-class: org.postgresql.ds.PGSimpleDataSource
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createConnectionFactory(LocalManagedConnectionFactory.java:108)
at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:772)
at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:312)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:371)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:149)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
14:16:16,588 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service org.wildfly.data-source.Postgres_MY_APP_DS: org.jboss.msc.service.StartException in service org.wildfly.data-source.Postgres_MY_APP_DS: WFLYJCA0033: Error during the deployment of Postgres_MY_APP_DS
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:163)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:151)
... 5 more
.....
14:16:17,470 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "Postgres_MY_APP_DS")
]) - failure description: {
"WFLYCTL0080: Failed services" => {"org.wildfly.data-source.Postgres_MY_APP_DS" => "org.jboss.msc.service.StartException in service org.wildfly.data-source.Postgres_MY_APP_DS: WFLYJCA0033: Error during the deployment of Postgres_MY_APP_DS
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"},
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.data-source.Postgres_MY_APP_DS"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
}
14:16:17,473 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "Postgres_MY_APP_DS")
]) - failure description: {
"WFLYCTL0080: Failed services" => {"org.wildfly.data-source.Postgres_MY_APP_DS" => "org.jboss.msc.service.StartException in service org.wildfly.data-source.Postgres_MY_APP_DS: WFLYJCA0033: Error during the deployment of Postgres_MY_APP_DS
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"},
"WFLYCTL0412: Required services that are not installed:" => [
"org.wildfly.data-source.Postgres_MY_APP_DS",
"org.wildfly.data-source.Postgres_MY_APP_DS"
],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
}
{code}
h3. Other examples
The following configuration is similar and would also fail:
* http://www.nailedtothex.org/roller/kyle/entry/registering-postgresql-jdbc...
> Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
> -------------------------------------------------------------------
>
> Key: WFLY-7018
> URL: https://issues.jboss.org/browse/WFLY-7018
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.1.0.Final
> Reporter: Mark S
> Assignee: Jesper Pedersen
>
> My current Wildfly 10.0.0.Final (Non-XA) Datasource configuration will not work for Wildfly 10.1.0.Final. See the "Steps to Reproduce" section.
> The stacktrace points to here:
> * https://source.jboss.org/browse/IronJacamar/adapters/src/main/java/org/jb...
> * https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.3.4.Final/a...
> h3. The work-around
> h3. Wildfly 10.1.0.Final Datasource configuration via CLI
> {code}
> # No parameter to set a connection property value.
> {code}
> h3. Wildfly 10.1.0.Final Datasource configuration via XML (standalone-full.xml)
> Note the addition of {{<connection-property name="databaseName">myapp</connection-property>}}
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:datasources:4.0">
> <datasources>
> <datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS">
> <connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
> <connection-property name="databaseName">myapp</connection-property>
> <driver>postgres</driver>
> <security>
> <user-name>myapp</user-name>
> <password>myapp</password>
> </security>
> <validation>
> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
> </validation>
> </datasource>
> <drivers>
> <driver name="postgres" module="org.postgres">
> <driver-class>org.postgresql.Driver</driver-class>
> <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
> <datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
> </driver>
> </drivers>
> </datasources>
> </subsystem>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFLY-7018) Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
by Mark S (JIRA)
[ https://issues.jboss.org/browse/WFLY-7018?page=com.atlassian.jira.plugin.... ]
Mark S updated WFLY-7018:
-------------------------
Description:
My current Wildfly 10.0.0.Final (Non-XA) Datasource configuration will not work for Wildfly 10.1.0.Final. See the "Steps to Reproduce" section.
The stacktrace points to here:
* https://source.jboss.org/browse/IronJacamar/adapters/src/main/java/org/jb...
* https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.3.4.Final/a...
h3. The work-around
h3. Wildfly 10.1.0.Final Datasource configuration via CLI
{code}
# No parameter to set a connection property value.
{code}
h3. Wildfly 10.1.0.Final Datasource configuration via XML (standalone-full.xml)
Note the addition of {{<connection-property name="databaseName">myapp</connection-property>}}
{code:xml}
<subsystem xmlns="urn:jboss:domain:datasources:4.0">
<datasources>
<datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS">
<connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
<connection-property name="databaseName">myapp</connection-property>
<driver>postgres</driver>
<security>
<user-name>myapp</user-name>
<password>myapp</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
</validation>
</datasource>
<drivers>
<driver name="postgres" module="org.postgres">
<driver-class>org.postgresql.Driver</driver-class>
<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
<datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
</driver>
</drivers>
</datasources>
</subsystem>
{code}
was:
My current Wildfly 10.0.0.Final (Non-XA) Datasource configuration will not work for Wildfly 10.1.0.Final. See the "Steps to Reproduce" section.
The stacktrace points to here:
https://source.jboss.org/browse/IronJacamar/adapters/src/main/java/org/jb...
h3. The work-around
h3. Wildfly 10.1.0.Final Datasource configuration via CLI
{code}
# No parameter to set a connection property value.
{code}
h3. Wildfly 10.1.0.Final Datasource configuration via XML (standalone-full.xml)
Note the addition of {{<connection-property name="databaseName">myapp</connection-property>}}
{code:xml}
<subsystem xmlns="urn:jboss:domain:datasources:4.0">
<datasources>
<datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS">
<connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
<connection-property name="databaseName">myapp</connection-property>
<driver>postgres</driver>
<security>
<user-name>myapp</user-name>
<password>myapp</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
</validation>
</datasource>
<drivers>
<driver name="postgres" module="org.postgres">
<driver-class>org.postgresql.Driver</driver-class>
<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
<datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
</driver>
</drivers>
</datasources>
</subsystem>
{code}
> Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
> -------------------------------------------------------------------
>
> Key: WFLY-7018
> URL: https://issues.jboss.org/browse/WFLY-7018
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.1.0.Final
> Reporter: Mark S
> Assignee: Jesper Pedersen
>
> My current Wildfly 10.0.0.Final (Non-XA) Datasource configuration will not work for Wildfly 10.1.0.Final. See the "Steps to Reproduce" section.
> The stacktrace points to here:
> * https://source.jboss.org/browse/IronJacamar/adapters/src/main/java/org/jb...
> * https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.3.4.Final/a...
> h3. The work-around
> h3. Wildfly 10.1.0.Final Datasource configuration via CLI
> {code}
> # No parameter to set a connection property value.
> {code}
> h3. Wildfly 10.1.0.Final Datasource configuration via XML (standalone-full.xml)
> Note the addition of {{<connection-property name="databaseName">myapp</connection-property>}}
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:datasources:4.0">
> <datasources>
> <datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS">
> <connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
> <connection-property name="databaseName">myapp</connection-property>
> <driver>postgres</driver>
> <security>
> <user-name>myapp</user-name>
> <password>myapp</password>
> </security>
> <validation>
> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
> </validation>
> </datasource>
> <drivers>
> <driver name="postgres" module="org.postgres">
> <driver-class>org.postgresql.Driver</driver-class>
> <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
> <datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
> </driver>
> </drivers>
> </datasources>
> </subsystem>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFLY-7018) Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
by Mark S (JIRA)
[ https://issues.jboss.org/browse/WFLY-7018?page=com.atlassian.jira.plugin.... ]
Mark S updated WFLY-7018:
-------------------------
Description:
My current Wildfly 10.0.0.Final (Non-XA) Datasource configuration will not work for Wildfly 10.1.0.Final. See the "Steps to Reproduce" section.
The stacktrace points to here:
https://source.jboss.org/browse/IronJacamar/adapters/src/main/java/org/jb...
h3. The work-around
h3. Wildfly 10.1.0.Final Datasource configuration via CLI
{code}
# No parameter to set a connection property value.
{code}
h3. Wildfly 10.1.0.Final Datasource configuration via XML (standalone-full.xml)
Note the addition of {{<connection-property name="databaseName">myapp</connection-property>}}
{code:xml}
<subsystem xmlns="urn:jboss:domain:datasources:4.0">
<datasources>
<datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS">
<connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
<connection-property name="databaseName">myapp</connection-property>
<driver>postgres</driver>
<security>
<user-name>myapp</user-name>
<password>myapp</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
</validation>
</datasource>
<drivers>
<driver name="postgres" module="org.postgres">
<driver-class>org.postgresql.Driver</driver-class>
<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
<datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
</driver>
</drivers>
</datasources>
</subsystem>
{code}
was:
My current Wildfly 10.0.0.Final (Non-XA) Datasource configuration will not work for Wildfly 10.1.0.Final. See Steps
The stacktrace points to here:
https://source.jboss.org/browse/IronJacamar/adapters/src/main/java/org/jb...
h3. The work-around
h3. Wildfly 10.1.0.Final Datasource configuration via CLI
{code}
# No parameter to set a connection property value.
{code}
h3. Wildfly 10.1.0.Final Datasource configuration via XML (standalone-full.xml)
Note the addition of {{<connection-property name="databaseName">myapp</connection-property>}}
{code:xml}
<subsystem xmlns="urn:jboss:domain:datasources:4.0">
<datasources>
<datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS">
<connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
<connection-property name="databaseName">myapp</connection-property>
<driver>postgres</driver>
<security>
<user-name>myapp</user-name>
<password>myapp</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
</validation>
</datasource>
<drivers>
<driver name="postgres" module="org.postgres">
<driver-class>org.postgresql.Driver</driver-class>
<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
<datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
</driver>
</drivers>
</datasources>
</subsystem>
{code}
> Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
> -------------------------------------------------------------------
>
> Key: WFLY-7018
> URL: https://issues.jboss.org/browse/WFLY-7018
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.1.0.Final
> Reporter: Mark S
> Assignee: Jesper Pedersen
>
> My current Wildfly 10.0.0.Final (Non-XA) Datasource configuration will not work for Wildfly 10.1.0.Final. See the "Steps to Reproduce" section.
> The stacktrace points to here:
> https://source.jboss.org/browse/IronJacamar/adapters/src/main/java/org/jb...
> h3. The work-around
> h3. Wildfly 10.1.0.Final Datasource configuration via CLI
> {code}
> # No parameter to set a connection property value.
> {code}
> h3. Wildfly 10.1.0.Final Datasource configuration via XML (standalone-full.xml)
> Note the addition of {{<connection-property name="databaseName">myapp</connection-property>}}
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:datasources:4.0">
> <datasources>
> <datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS">
> <connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
> <connection-property name="databaseName">myapp</connection-property>
> <driver>postgres</driver>
> <security>
> <user-name>myapp</user-name>
> <password>myapp</password>
> </security>
> <validation>
> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
> </validation>
> </datasource>
> <drivers>
> <driver name="postgres" module="org.postgres">
> <driver-class>org.postgresql.Driver</driver-class>
> <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
> <datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
> </driver>
> </drivers>
> </datasources>
> </subsystem>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFLY-7018) Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
by Mark S (JIRA)
[ https://issues.jboss.org/browse/WFLY-7018?page=com.atlassian.jira.plugin.... ]
Mark S updated WFLY-7018:
-------------------------
Description:
My current Wildfly 10.0.0.Final (Non-XA) Datasource configuration will not work for Wildfly 10.1.0.Final. See Steps
The stacktrace points to here:
https://source.jboss.org/browse/IronJacamar/adapters/src/main/java/org/jb...
h3. The work-around
h3. Wildfly 10.1.0.Final Datasource configuration via CLI
{code}
# No parameter to set a connection property value.
{code}
h3. Wildfly 10.1.0.Final Datasource configuration via XML (standalone-full.xml)
Note the addition of {{<connection-property name="databaseName">myapp</connection-property>}}
{code:xml}
<subsystem xmlns="urn:jboss:domain:datasources:4.0">
<datasources>
<datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS">
<connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
<connection-property name="databaseName">myapp</connection-property>
<driver>postgres</driver>
<security>
<user-name>myapp</user-name>
<password>myapp</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
</validation>
</datasource>
<drivers>
<driver name="postgres" module="org.postgres">
<driver-class>org.postgresql.Driver</driver-class>
<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
<datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
</driver>
</drivers>
</datasources>
</subsystem>
{code}
was:
My current Wildfly 10.0.0.Final (Non-XA) Datasource configuration will not work for Wildfly 10.1.0.Final.
h3. The work-around
h3. Wildfly 10.1.0.Final Datasource configuration via CLI
{code}
# No parameter to set a connection property value.
{code}
h3. Wildfly 10.1.0.Final Datasource configuration via XML (standalone-full.xml)
Note the addition of {{<connection-property name="databaseName">myapp</connection-property>}}
{code:xml}
<subsystem xmlns="urn:jboss:domain:datasources:4.0">
<datasources>
<datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS">
<connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
<connection-property name="databaseName">myapp</connection-property>
<driver>postgres</driver>
<security>
<user-name>myapp</user-name>
<password>myapp</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
</validation>
</datasource>
<drivers>
<driver name="postgres" module="org.postgres">
<driver-class>org.postgresql.Driver</driver-class>
<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
<datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
</driver>
</drivers>
</datasources>
</subsystem>
{code}
> Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
> -------------------------------------------------------------------
>
> Key: WFLY-7018
> URL: https://issues.jboss.org/browse/WFLY-7018
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.1.0.Final
> Reporter: Mark S
> Assignee: Jesper Pedersen
>
> My current Wildfly 10.0.0.Final (Non-XA) Datasource configuration will not work for Wildfly 10.1.0.Final. See Steps
> The stacktrace points to here:
> https://source.jboss.org/browse/IronJacamar/adapters/src/main/java/org/jb...
> h3. The work-around
> h3. Wildfly 10.1.0.Final Datasource configuration via CLI
> {code}
> # No parameter to set a connection property value.
> {code}
> h3. Wildfly 10.1.0.Final Datasource configuration via XML (standalone-full.xml)
> Note the addition of {{<connection-property name="databaseName">myapp</connection-property>}}
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:datasources:4.0">
> <datasources>
> <datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS">
> <connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
> <connection-property name="databaseName">myapp</connection-property>
> <driver>postgres</driver>
> <security>
> <user-name>myapp</user-name>
> <password>myapp</password>
> </security>
> <validation>
> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
> </validation>
> </datasource>
> <drivers>
> <driver name="postgres" module="org.postgres">
> <driver-class>org.postgresql.Driver</driver-class>
> <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
> <datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
> </driver>
> </drivers>
> </datasources>
> </subsystem>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFLY-7018) Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
by Mark S (JIRA)
Mark S created WFLY-7018:
----------------------------
Summary: Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final
Key: WFLY-7018
URL: https://issues.jboss.org/browse/WFLY-7018
Project: WildFly
Issue Type: Bug
Components: JCA
Affects Versions: 10.1.0.Final
Reporter: Mark S
Assignee: Jesper Pedersen
My current Wildfly 10.0.0.Final (Non-XA) Datasource configuration will not work for Wildfly 10.1.0.Final.
h3. The work-around
h3. Wildfly 10.1.0.Final Datasource configuration via CLI
{code}
# No parameter to set a connection property value.
{code}
h3. Wildfly 10.1.0.Final Datasource configuration via XML (standalone-full.xml)
Note the addition of {{<connection-property name="databaseName">myapp</connection-property>}}
{code:xml}
<subsystem xmlns="urn:jboss:domain:datasources:4.0">
<datasources>
<datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS">
<connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url>
<connection-property name="databaseName">myapp</connection-property>
<driver>postgres</driver>
<security>
<user-name>myapp</user-name>
<password>myapp</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
</validation>
</datasource>
<drivers>
<driver name="postgres" module="org.postgres">
<driver-class>org.postgresql.Driver</driver-class>
<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
<datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
</driver>
</drivers>
</datasources>
</subsystem>
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFCORE-1743) Unable to force CLI to execute a low level command
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1743?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-1743:
------------------------------------------
Another reason it's important that users can configure the CLI to be lenient about sending low level ops is it's very helpful to us server developers in analyzing server behavior. If we can't do this we'd have to write custom clients to experiment, which is impractical. I hit this issue while trying to investigate solutions to WFCORE-1737.
> Unable to force CLI to execute a low level command
> --------------------------------------------------
>
> Key: WFCORE-1743
> URL: https://issues.jboss.org/browse/WFCORE-1743
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 3.0.0.Alpha5
> Reporter: Brian Stansberry
> Assignee: Alexey Loubyansky
> Fix For: 3.0.0.CR1
>
>
> I cannot get this operation to execute, even if I set validate-operation-requests to false in jboss-cli.xml:
> {code}
> [standalone@embedded /] /subsystem=datasources/bogus=*:read-resource-description
> Failed to get the list of the operation properties: "WFLYCTL0030: No resource definition is registered for address [
> ("subsystem" => "datasources"),
> ("bogus" => "*")
> ]"
> {code}
> It is important that the CLI allows users to send whatever low level ops they wish to the server if they turn off verification. The server validates requests itself, and in some cases can be coded to be lenient about things (e.g. to let previous 'wrong' things work.) We don't want the CLI to get in the way of that by doing client side validation that cannot be turned off.
> Problem seems to be this in the Util class:
> {code}
> public static ModelNode toOperationRequest(CommandContext ctx,
> ParsedCommandLine parsedLine, Attachments attachments)
> throws CommandFormatException {
> return toOperationRequest(ctx, parsedLine, attachments, true);
> }
> {code}
> That 'true' param results in the CLI trying to do a background read-operation-description and failing the op if unsuccessful.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months