[
https://issues.jboss.org/browse/WFLY-6157?page=com.atlassian.jira.plugin....
]
Christian Beikov commented on WFLY-6157:
----------------------------------------
What exactly do you need? Here is the datasource and driver definition that I use.
{code:xml}
<datasource jta="true" jndi-name="java:jboss/datasources/MyDS"
pool-name="MyDS" enabled="true" use-ccm="true">
<connection-url>jdbc:postgresql://localhost:5432/mydb</connection-url>
<driver>org.postgresql</driver>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
<pool>
<min-pool-size>4</min-pool-size>
<max-pool-size>8</max-pool-size>
<prefill>true</prefill>
</pool>
<security>
<user-name>dbadmin</user-name>
<password>dbadmin</password>
</security>
<validation>
<validate-on-match>true</validate-on-match>
<background-validation>true</background-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>
<statement>
<share-prepared-statements>false</share-prepared-statements>
</statement>
</datasource>
<driver name="org.postgresql" module="org.postgresql">
<driver-class>org.postgresql.Driver</driver-class>
<datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
</driver>
{code}
Connection URL ignored for SQL Server datasource
------------------------------------------------
Key: WFLY-6157
URL:
https://issues.jboss.org/browse/WFLY-6157
Project: WildFly
Issue Type: Bug
Affects Versions: 10.0.0.Final
Reporter: Rich DiCroce
Assignee: Jason Greene
The connection-url for a datasource is being ignored (or more likely, getting lost
somewhere) when using WildFly with the Microsoft SQL Server JDBC driver. No matter what I
specify as the connection-url (even something obviously invalid like "foobar"),
the driver always ends up using the defaults that are baked into it.
The same driver worked fine on WildFly 10 CR2 (and many earlier versions), so some change
between then and 10 Final has caused a regression.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)