May 2016 - jboss-jira - Jboss List Archives

[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)

8 years, 7 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)

8 years, 7 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)

8 years, 7 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)

8 years, 7 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)

8 years, 7 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)

8 years, 7 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)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3742) DeliveryActive not documented

by ANGELA ROBERTSON (JIRA)

[ https://issues.jboss.org/browse/WFLY-3742?page=com.atlassian.jira.plugin.... ] ANGELA ROBERTSON reassigned WFLY-3742: -------------------------------------- Assignee: Brian Stansberry (was: Nidhi Chaudhary) > DeliveryActive not documented > ----------------------------- > > Key: WFLY-3742 > URL: https://issues.jboss.org/browse/WFLY-3742 > Project: WildFly > Issue Type: Bug > Components: Documentation > Environment: JBoss EAP 6.2 > Reporter: Tom Ross > Assignee: Brian Stansberry > > Please document fix for WFLY-878. It is an important feature. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1427) Add a timeout param to reload op and use it for "graceful reload"

by Yeray Santana Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1427?page=com.atlassian.jira.plugi... ] Yeray Santana Borges reassigned WFCORE-1427: -------------------------------------------- Assignee: Yeray Santana Borges > Add a timeout param to reload op and use it for "graceful reload" > ----------------------------------------------------------------- > > Key: WFCORE-1427 > URL: https://issues.jboss.org/browse/WFCORE-1427 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI, Domain Management > Reporter: Brian Stansberry > Assignee: Yeray Santana Borges > > So instead of > {code} > :suspend(20) > :reload > {code} > It's just > {code} > :reload(20) > {code} > The high level 'reload' command in the CLI should take a --timeout param as well. > If doing the graceful suspend as part of server side ":reload" handling proves problematic (I haven't looked into it at all before filing this) then a simpler alternative is to only go with the --timeout param on the CLI reload command, and have the CLI implement the graceful behavior internally by first calling :suspend and then :reload. Web console could do the same thing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6527) Cannot lookup RemoteConnectionFactory using https-remoting

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-6527?page=com.atlassian.jira.plugin.... ] jaikiran pai commented on WFLY-6527: ------------------------------------ If possible, please attach a simple application which reproduces this. Or please open a forum discussion https://developer.jboss.org/en/wildfly/ where this can be looked into in detail along with code and exception stacktraces. > Cannot lookup RemoteConnectionFactory using https-remoting > ---------------------------------------------------------- > > Key: WFLY-6527 > URL: https://issues.jboss.org/browse/WFLY-6527 > Project: WildFly > Issue Type: Bug > Components: Remoting > Affects Versions: 10.0.0.Final > Environment: RedHat Linux, Java 1.8 > Reporter: George Turner > Assignee: David Lloyd > > I have successfully configured the system for two way ssl. I can connect to a topic from a standalone client, but I cannot connect with the same code from an EJB client using the following: > Properties props = new Properties(); > props.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); > ctx = new InitialContext(props); > ConnectionFactory cf = (ConnectionFactory) ctx.lookup("jms/RemoteConnectionFactory"); > It seems to "attach" the stateless bean to the first remote instance and then the second remote instance lookup fails. I have tried using the EJBClientContext properties (as used for EJB lookups) but no help. There is VERY little documentation about using https-remoting. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2016