May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6626) Add log message indicating disabled <distributable/> flag from web-fragments

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/WFLY-6626?page=com.atlassian.jira.plugin.... ] Panagiotis Sotiropoulos commented on WFLY-6626: ----------------------------------------------- PR : https://github.com/wildfly/wildfly/pull/8939 > Add log message indicating disabled <distributable/> flag from web-fragments > ---------------------------------------------------------------------------- > > Key: WFLY-6626 > URL: https://issues.jboss.org/browse/WFLY-6626 > Project: WildFly > Issue Type: Enhancement > Components: Web (Undertow) > Affects Versions: 10.0.0.Final > Reporter: Aaron Ogburn > Assignee: Stuart Douglas > Attachments: undistributable.war > > > If a web-fragment doesn't have distributable set, then replication is not enabled. This happens silently so it may be confusing to some users that are expecting replication to be enabled when they have set <distributable/> in their WEB-INF/web.xml. > Other third party libraries they included may have web-fragments without distributable set so it'd be nice to log a notification when this happens so that users are easily informed why replication was not enabled as they may have expected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6538) https-listener does not support proxy-address-forwarding

by Emond Papegaaij (JIRA)

[ https://issues.jboss.org/browse/WFLY-6538?page=com.atlassian.jira.plugin.... ] Emond Papegaaij commented on WFLY-6538: --------------------------------------- Any news on this issue? The pull request was sent 6 weeks ago, but is still not merged. It would be really nice if this could be fixed before 10.1. > https-listener does not support proxy-address-forwarding > -------------------------------------------------------- > > Key: WFLY-6538 > URL: https://issues.jboss.org/browse/WFLY-6538 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 9.0.2.Final, 10.0.0.Final > Reporter: Emond Papegaaij > Assignee: Tomaz Cerar > > HttpsListenerService explicitly passes false to its superclass for proxyAddressForwarding and certificateForwarding, making it impossible to enable these features. For a security-sensitive application, we need a secure connection from our proxy to WildFly and we need WildFly to respect the headers sent by our proxy. It seems easy to support these options by reading them in HttpsListenerAdd and passing them to HttpsListenerService, which can simply pass them to the super constructor. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1320) Unable to create JDBC local datasource without properties on JBoss EAP 7

by ted won (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1320?page=com.atlassian.jira.plugin... ] ted won updated JBJCA-1320: --------------------------- Issue Type: Bug (was: Enhancement) > Unable to create JDBC local datasource without properties on JBoss EAP 7 > ------------------------------------------------------------------------ > > Key: JBJCA-1320 > URL: https://issues.jboss.org/browse/JBJCA-1320 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.3.Final > Reporter: ted won > Assignee: ted won > Priority: Minor > Attachments: com.msql.tar.gz > > > It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 or creating non-XA datasource, using local transactions in JBoss EAP 7. > It should display warning message than throwing error like [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. > In case of MySQL datasource classes it's possible to use datasource-class and create non-XA datasource in JBoss EAP 6 and WildFly 10 but EAP 7. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1320) Unable to create JDBC local datasource without properties on JBoss EAP 7

by ted won (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1320?page=com.atlassian.jira.plugin... ] ted won updated JBJCA-1320: --------------------------- Description: It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 or creating non-XA datasource, using local transactions in JBoss EAP 7. It should display warning message than throwing error like [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. In case of MySQL datasource classes it's possible to use datasource-class and create non-XA datasource in JBoss EAP 6 and WildFly 10 but EAP 7. was: It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 or creating non-XA datasource, using local transactions in JBoss EAP 7. It should display warning message than throwing error like [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. In case of MySQL datasource classes it's possible to use datasource-class for non-XA datasource in JBoss EAP 6 and WildFly 10 but EAP 7. > Unable to create JDBC local datasource without properties on JBoss EAP 7 > ------------------------------------------------------------------------ > > Key: JBJCA-1320 > URL: https://issues.jboss.org/browse/JBJCA-1320 > Project: IronJacamar > Issue Type: Enhancement > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.3.Final > Reporter: ted won > Assignee: ted won > Priority: Minor > Attachments: com.msql.tar.gz > > > It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 or creating non-XA datasource, using local transactions in JBoss EAP 7. > It should display warning message than throwing error like [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. > In case of MySQL datasource classes it's possible to use datasource-class and create > non-XA datasource in JBoss EAP 6 and WildFly 10 but EAP 7. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1320) Unable to create JDBC local datasource without properties on JBoss EAP 7

by ted won (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1320?page=com.atlassian.jira.plugin... ] ted won updated JBJCA-1320: --------------------------- Description: It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 or creating non-XA datasource, using local transactions in JBoss EAP 7. It should display warning message than throwing error like [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. In case of MySQL datasource classes it's possible to use datasource-class and create non-XA datasource in JBoss EAP 6 and WildFly 10 but EAP 7. was: It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 or creating non-XA datasource, using local transactions in JBoss EAP 7. It should display warning message than throwing error like [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. In case of MySQL datasource classes it's possible to use datasource-class and create non-XA datasource in JBoss EAP 6 and WildFly 10 but EAP 7. > Unable to create JDBC local datasource without properties on JBoss EAP 7 > ------------------------------------------------------------------------ > > Key: JBJCA-1320 > URL: https://issues.jboss.org/browse/JBJCA-1320 > Project: IronJacamar > Issue Type: Enhancement > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.3.Final > Reporter: ted won > Assignee: ted won > Priority: Minor > Attachments: com.msql.tar.gz > > > It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 or creating non-XA datasource, using local transactions in JBoss EAP 7. > It should display warning message than throwing error like [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. > In case of MySQL datasource classes it's possible to use datasource-class and create non-XA datasource in JBoss EAP 6 and WildFly 10 but EAP 7. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1320) Unable to create JDBC local datasource without properties on JBoss EAP 7

by ted won (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1320?page=com.atlassian.jira.plugin... ] ted won updated JBJCA-1320: --------------------------- Issue Type: Enhancement (was: Bug) > Unable to create JDBC local datasource without properties on JBoss EAP 7 > ------------------------------------------------------------------------ > > Key: JBJCA-1320 > URL: https://issues.jboss.org/browse/JBJCA-1320 > Project: IronJacamar > Issue Type: Enhancement > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.3.Final > Reporter: ted won > Assignee: ted won > Priority: Minor > Attachments: com.msql.tar.gz > > > It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 or creating non-XA datasource, using local transactions in JBoss EAP 7. > It should display warning message than throwing error like [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. > In case of MySQL datasource classes it's possible to use datasource-class for non-XA datasource in JBoss EAP 6 and WildFly 10 but EAP 7. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1320) Unable to create JDBC local datasource without properties on JBoss EAP 7

by ted won (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1320?page=com.atlassian.jira.plugin... ] ted won updated JBJCA-1320: --------------------------- Description: It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 or creating non-XA datasource, using local transactions in JBoss EAP 7. It should display warning message than throwing error like [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. In case of MySQL datasource classes it's possible to use datasource-class for non-XA datasource in JBoss EAP 6 and WildFly 10 but EAP 7. was: It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 or creating non-XA datasource, using local transactions in JBoss EAP 7. It should display warning message than error. In case of MySQL datasource classes it's possible to use datasource-class for non-XA datasource in JBoss EAP 6 and WildFly 10 but EAP 7. > Unable to create JDBC local datasource without properties on JBoss EAP 7 > ------------------------------------------------------------------------ > > Key: JBJCA-1320 > URL: https://issues.jboss.org/browse/JBJCA-1320 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.3.Final > Reporter: ted won > Assignee: ted won > Priority: Minor > Attachments: com.msql.tar.gz > > > It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 or creating non-XA datasource, using local transactions in JBoss EAP 7. > It should display warning message than throwing error like [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. > In case of MySQL datasource classes it's possible to use datasource-class for non-XA datasource in JBoss EAP 6 and WildFly 10 but EAP 7. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1320) Unable to create JDBC local datasource without properties on JBoss EAP 7

by ted won (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1320?page=com.atlassian.jira.plugin... ] ted won updated JBJCA-1320: --------------------------- Description: It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 or creating non-XA datasource, using local transactions in JBoss EAP 7. It should display warning message than error. In case of MySQL datasource classes it's possible to use datasource-class for non-XA datasource in JBoss EAP 6 and WildFly 10 but EAP 7. Steps to Reproduce: 1. Prepare JBoss EAP 7.0.0 2. Edit standalone.xml and MySQL datasource like below: {code:xml} ... <subsystem xmlns="urn:jboss:domain:datasources:4.0"> <datasources> <datasource jndi-name="java:jboss/datasources/MySqlDS" pool-name="MySqlDS"> <connection-url>jdbc:mysql://localhost:3306/mydb</connection-url> <driver>com.mysql</driver> <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation> <pool> <min-pool-size>10</min-pool-size> <max-pool-size>100</max-pool-size> <prefill>true</prefill> </pool> <security> <user-name>root</user-name> <password></password> </security> <statement> <prepared-statement-cache-size>32</prepared-statement-cache-size> <share-prepared-statements/> </statement> </datasource> <drivers> <driver name="com.mysql" module="com.mysql"> <datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource</datasource-class> </driver> </drivers> </datasources> </subsystem> ... {code} 3. Run JBoss EAP 7.0.0 bin/standalone.sh 4. Failed to start service org.wildfly.data-source.MySqlDS javax.resource.ResourceException: IJ031103: At least one connection property must be defined for datasource-class: com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource {code} 15:55:35,314 ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-3) Error during the deployment of java:jboss/datasources/MySqlDS: javax.resource.ResourceException: IJ031103: At least one connection property must be defined for datasource-class: com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource 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:364) at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:145) 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) 15:55:35,315 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service org.wildfly.data-source.MySqlDS: org.jboss.msc.service.StartException in service org.wildfly.data-source.MySqlDS: WFLYJCA0033: Error during the deployment of MySqlDS at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:159) 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:147) ... 5 more {code} 5. Actual expected: Go to JBoss EAP 7.0.0 Management Console Go to http://localhost:9990/console/App.html#profile/datasources;name=MySqlDS Run 'Test Connection' and return 'Successfully connected to database MySqlDS.' Attachment: com.msql.tar.gz Workaround Description: It's working after changing <datasource> with <xa-datasource> element in the datasources subsystem. Workaround: Workaround Exists > Unable to create JDBC local datasource without properties on JBoss EAP 7 > ------------------------------------------------------------------------ > > Key: JBJCA-1320 > URL: https://issues.jboss.org/browse/JBJCA-1320 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.3.Final > Reporter: ted won > Assignee: ted won > Priority: Minor > Attachments: com.msql.tar.gz > > > It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 or creating non-XA datasource, using local transactions in JBoss EAP 7. > It should display warning message than error. > In case of MySQL datasource classes it's possible to use datasource-class for non-XA datasource in JBoss EAP 6 and WildFly 10 but EAP 7. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1320) Unable to create JDBC local datasource without properties on JBoss EAP 7

by ted won (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1320?page=com.atlassian.jira.plugin... ] ted won updated JBJCA-1320: --------------------------- Summary: Unable to create JDBC local datasource without properties on JBoss EAP 7 (was: Failure to create JDBC datasource without properties on JBoss EAP 7) > Unable to create JDBC local datasource without properties on JBoss EAP 7 > ------------------------------------------------------------------------ > > Key: JBJCA-1320 > URL: https://issues.jboss.org/browse/JBJCA-1320 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.3.Final > Reporter: ted won > Assignee: ted won > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1320) Failure to create JDBC datasource without properties on JBoss EAP 7

by ted won (JIRA)

ted won created JBJCA-1320: ------------------------------ Summary: Failure to create JDBC datasource without properties on JBoss EAP 7 Key: JBJCA-1320 URL: https://issues.jboss.org/browse/JBJCA-1320 Project: IronJacamar Issue Type: Bug Components: JDBC Affects Versions: WildFly/IronJacamar 1.3.3.Final Reporter: ted won Assignee: ted won Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2016