[JBoss JIRA] (TEIID-5827) XA datasource properties are undefined
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5827?page=com.atlassian.jira.plugin... ]
Steven Hawkins reopened TEIID-5827:
-----------------------------------
> XA datasource properties are undefined
> --------------------------------------
>
> Key: TEIID-5827
> URL: https://issues.jboss.org/browse/TEIID-5827
> Project: Teiid
> Issue Type: Bug
> Components: AdminApi
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.0, 12.2.2, 12.3.1
>
>
> The method getTemplatePropertyDefinitions, in the class AdminFactory.java.
> The datasource name should be "xa-data-source" instead of "data-source" when the datasource is XA. See the code snapshot below:
>
> {code:java}
> // get JDBC properties
> if (isXA(templateName)) {
> cliCall("read-resource-description", new String[] {"subsystem", "datasources", "data-source",
> stripXA(templateName)}, null, builder);
> addXAProperties(props);
> } else {
> cliCall("read-resource-description", new String[] {"subsystem", "datasources", "data-source",
> templateName}, null, builder);
> addDriverproperties(props);
> }
> {code}
> Another issue, when reading using the method getDataSource in the class AdminFactory.java, it is not getting the properties recursively. and the connection properties are returned as undefined like below:
>
> {code:java}
> "xa-datasource-properties" => {
> "DatabaseName" => undefined,
> "PortNumber" => undefined,
> "ServerName" => undefined
> }
> {code}
> more details in the following forum discussion link: [https://developer.jboss.org/thread/280411?start=15&tstart=0]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (TEIID-5827) XA datasource properties are undefined
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5827?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5827:
---------------------------------------
[~mtawk] with the existing logic it looks like that would need to be set via the connection-properties property as URL=jdbc:oracle:thin:@oraclehost:1521/ORCL - I think this needs some tweaking as the code has special handling only for a handful of xa properties: ServerName, PortNumber, and DatabaseName
> XA datasource properties are undefined
> --------------------------------------
>
> Key: TEIID-5827
> URL: https://issues.jboss.org/browse/TEIID-5827
> Project: Teiid
> Issue Type: Bug
> Components: AdminApi
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.0, 12.2.2, 12.3.1
>
>
> The method getTemplatePropertyDefinitions, in the class AdminFactory.java.
> The datasource name should be "xa-data-source" instead of "data-source" when the datasource is XA. See the code snapshot below:
>
> {code:java}
> // get JDBC properties
> if (isXA(templateName)) {
> cliCall("read-resource-description", new String[] {"subsystem", "datasources", "data-source",
> stripXA(templateName)}, null, builder);
> addXAProperties(props);
> } else {
> cliCall("read-resource-description", new String[] {"subsystem", "datasources", "data-source",
> templateName}, null, builder);
> addDriverproperties(props);
> }
> {code}
> Another issue, when reading using the method getDataSource in the class AdminFactory.java, it is not getting the properties recursively. and the connection properties are returned as undefined like below:
>
> {code:java}
> "xa-datasource-properties" => {
> "DatabaseName" => undefined,
> "PortNumber" => undefined,
> "ServerName" => undefined
> }
> {code}
> more details in the following forum discussion link: [https://developer.jboss.org/thread/280411?start=15&tstart=0]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (TEIID-5825) allow connection to mongodb cluster on atlas (cloud.mongodb.com)
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5825?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5825:
---------------------------------------
Yes, I was planning to.
> allow connection to mongodb cluster on atlas (cloud.mongodb.com)
> ----------------------------------------------------------------
>
> Key: TEIID-5825
> URL: https://issues.jboss.org/browse/TEIID-5825
> Project: Teiid
> Issue Type: Bug
> Components: Connector API
> Affects Versions: 12.2
> Reporter: Marco Ardito
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.0, 12.3.1
>
>
> The issue is that teiid mongodb connector expects connection parameters based on the " Standard Connection String Format" instead of the "DNS Seedlist Connection Format", as defined in [https://docs.mongodb.com/manual/reference/connection-string|https://docs....]
> _
> "In addition to the standard connection format, MongoDB supports a DNS-constructed seed list. Using DNS to construct the available servers list allows more flexibility of deployment and the ability to change the servers in rotation without reconfiguring clients."_
> The following is a typical connection string for a DNS seedlist connection string:
> mongodb+srv://server.example.com/
> and:
> * a port number is not needed
> * a different prefix is used, instead of mongodb:// => mongodb+srv://
> I have a "free tier" cluster instance on cloud.mongodb,com (aka Atlas), which is limited in size and resources but should be functionally identical to a full sized paid cluster on the same platform, and it does not expire. A free tier can be activated here
> [https://www.mongodb.com/cloud/atlas#atlas-form-container|https://www.mong...]
> I tried with both the mongodb command line client and with the GUI tool Compass (https://www.mongodb.com/products/compass) which has a community edition
> and this different syntax works perfectly, while it is not supported by the current teiid connector, it seems
> there is a way to use the "old" syntax, prefixed by "mongodb:// " with server and port, to those Atlas clusters, but it is cumbersome, as it needs the user to specify more parameters, as "replicaSet" and "readPreference", at least. See https://docs.mongodb.com/manual/reference/connection-string
> With those additional settings I was able to connect with the Compass GUI tool, but not with the latest command line client (4.2), and anyway the teiid connector seems to not support those additional parameters,, I tried to add them as DS properties but always failed
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (TEIIDSB-127) "No registered data sources found" if used "management.server.port=8081"
by Renat Eskenin (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-127?page=com.atlassian.jira.plugi... ]
Renat Eskenin reopened TEIIDSB-127:
-----------------------------------
I sended additionnal information for reproduce
> "No registered data sources found" if used "management.server.port=8081"
> ------------------------------------------------------------------------
>
> Key: TEIIDSB-127
> URL: https://issues.jboss.org/browse/TEIIDSB-127
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: datasource
> Affects Versions: 1.2.0
> Environment: teiid-spring-boot
> Reporter: Renat Eskenin
> Assignee: Steven Hawkins
> Priority: Major
>
> When we used management.server.port=8081 and server.port=8080 in spring boot properties we get exception
> [2019-10-10 12:12:53,806 MSK] ERROR [test] org.teiid.PROCESSOR [restartedMain]: TEIID30019 Unexpected exception for request 8fPp+5AbzHhy.0
> java.lang.IllegalArgumentException: No registered data sources found
> How can we change management port for spring actuator and do not broken Teiid?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (TEIIDSB-127) "No registered data sources found" if used "management.server.port=8081"
by Renat Eskenin (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-127?page=com.atlassian.jira.plugi... ]
Renat Eskenin commented on TEIIDSB-127:
---------------------------------------
Ok. Spring properties:
{code:java}
spring.profiles.active=local,dev
spring.application.name=odata-facade
springfox.documentation.swagger.v2.path=/api-docs
spring.jackson.serialization.WRITE_DATES_AS_TIMESTAMPS=false
management.endpoint.metrics.enabled=true
management.endpoints.web.exposure.include=*
management.endpoint.prometheus.enabled=true
management.metrics.export.prometheus.enabled=true
server.port=8080
server.error.whitelabel.enabled=true
spring.devtools.restart.log-condition-evaluation-delta=false
spring.datasource.vertica.jdbc-url=jdbc:vertica://cis.local:5433/dwh?SearchPath=bi
spring.datasource.vertica.username=user
spring.datasource.vertica.password=password
spring.datasource.vertica.driver-class-name=com.vertica.jdbc.Driver
spring.datasource.vertica.platform=vertica
spring.datasource.vertica.translator-name=custom-vertica
spring.datasource.vertica.importer.SchemaName=bi
spring.datasource.vertica.importer.DatabaseTimeZone=UTC
spring.datasource.vertica.importer.UseFullSchemaName=false
spring.teiid.model.package=com.model
spring.jpa.hibernate.ddl-auto=none
logging.level.org.teiid=INFO
spring.main.allow-bean-definition-overriding=true
management.server.port=8911
springfox.documentation.swagger.v2.path=/swagger.json
{code}
Datasource
{code:java}
package com.config;
import javax.sql.DataSource;
import org.springframework.boot.context.properties.ConfigurationProperties;
import org.springframework.boot.jdbc.DataSourceBuilder;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.teiid.spring.autoconfigure.MultiDataSourceTransactionManagement;
@Configuration
public class DataSources extends MultiDataSourceTransactionManagement {
@ConfigurationProperties(prefix = "spring.datasource.vertica")
@Bean
public DataSource vertica() {
return DataSourceBuilder.create().build();
}
}
{code}
Its all project :)
> "No registered data sources found" if used "management.server.port=8081"
> ------------------------------------------------------------------------
>
> Key: TEIIDSB-127
> URL: https://issues.jboss.org/browse/TEIIDSB-127
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: datasource
> Affects Versions: 1.2.0
> Environment: teiid-spring-boot
> Reporter: Renat Eskenin
> Assignee: Steven Hawkins
> Priority: Major
>
> When we used management.server.port=8081 and server.port=8080 in spring boot properties we get exception
> [2019-10-10 12:12:53,806 MSK] ERROR [test] org.teiid.PROCESSOR [restartedMain]: TEIID30019 Unexpected exception for request 8fPp+5AbzHhy.0
> java.lang.IllegalArgumentException: No registered data sources found
> How can we change management port for spring actuator and do not broken Teiid?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (TEIID-5827) XA datasource properties are undefined
by Mark Tawk (Jira)
[ https://issues.jboss.org/browse/TEIID-5827?page=com.atlassian.jira.plugin... ]
Mark Tawk commented on TEIID-5827:
----------------------------------
Thank you Steven for the fix.
We encountered an issue with xa-datasource using Oracle. We are not able to set the xa-datasource-property "URL" for the oracle connection.
{code:java}
<xa-datasource-property name="URL">
jdbc:oracle:thin:@oraclehost:1521/ORCL
</xa-datasource-property>
{code}
> XA datasource properties are undefined
> --------------------------------------
>
> Key: TEIID-5827
> URL: https://issues.jboss.org/browse/TEIID-5827
> Project: Teiid
> Issue Type: Bug
> Components: AdminApi
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.0, 12.2.2, 12.3.1
>
>
> The method getTemplatePropertyDefinitions, in the class AdminFactory.java.
> The datasource name should be "xa-data-source" instead of "data-source" when the datasource is XA. See the code snapshot below:
>
> {code:java}
> // get JDBC properties
> if (isXA(templateName)) {
> cliCall("read-resource-description", new String[] {"subsystem", "datasources", "data-source",
> stripXA(templateName)}, null, builder);
> addXAProperties(props);
> } else {
> cliCall("read-resource-description", new String[] {"subsystem", "datasources", "data-source",
> templateName}, null, builder);
> addDriverproperties(props);
> }
> {code}
> Another issue, when reading using the method getDataSource in the class AdminFactory.java, it is not getting the properties recursively. and the connection properties are returned as undefined like below:
>
> {code:java}
> "xa-datasource-properties" => {
> "DatabaseName" => undefined,
> "PortNumber" => undefined,
> "ServerName" => undefined
> }
> {code}
> more details in the following forum discussion link: [https://developer.jboss.org/thread/280411?start=15&tstart=0]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (TEIID-5825) allow connection to mongodb cluster on atlas (cloud.mongodb.com)
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIID-5825?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5825:
-------------------------------------
Can you pls also make same change in spring boot version too?
> allow connection to mongodb cluster on atlas (cloud.mongodb.com)
> ----------------------------------------------------------------
>
> Key: TEIID-5825
> URL: https://issues.jboss.org/browse/TEIID-5825
> Project: Teiid
> Issue Type: Bug
> Components: Connector API
> Affects Versions: 12.2
> Reporter: Marco Ardito
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.0, 12.3.1
>
>
> The issue is that teiid mongodb connector expects connection parameters based on the " Standard Connection String Format" instead of the "DNS Seedlist Connection Format", as defined in [https://docs.mongodb.com/manual/reference/connection-string|https://docs....]
> _
> "In addition to the standard connection format, MongoDB supports a DNS-constructed seed list. Using DNS to construct the available servers list allows more flexibility of deployment and the ability to change the servers in rotation without reconfiguring clients."_
> The following is a typical connection string for a DNS seedlist connection string:
> mongodb+srv://server.example.com/
> and:
> * a port number is not needed
> * a different prefix is used, instead of mongodb:// => mongodb+srv://
> I have a "free tier" cluster instance on cloud.mongodb,com (aka Atlas), which is limited in size and resources but should be functionally identical to a full sized paid cluster on the same platform, and it does not expire. A free tier can be activated here
> [https://www.mongodb.com/cloud/atlas#atlas-form-container|https://www.mong...]
> I tried with both the mongodb command line client and with the GUI tool Compass (https://www.mongodb.com/products/compass) which has a community edition
> and this different syntax works perfectly, while it is not supported by the current teiid connector, it seems
> there is a way to use the "old" syntax, prefixed by "mongodb:// " with server and port, to those Atlas clusters, but it is cumbersome, as it needs the user to specify more parameters, as "replicaSet" and "readPreference", at least. See https://docs.mongodb.com/manual/reference/connection-string
> With those additional settings I was able to connect with the Compass GUI tool, but not with the latest command line client (4.2), and anyway the teiid connector seems to not support those additional parameters,, I tried to add them as DS properties but always failed
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (TEIID-5825) allow connection to mongodb cluster on atlas (cloud.mongodb.com)
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5825?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5825.
-----------------------------------
Fix Version/s: 13.0
12.3.1
Resolution: Done
Relaxed the logic for making a connection and added a check for the seedlist format. Updated the docs around the remoteServerList to explicitly state that it can contain the full prefixed url.
> allow connection to mongodb cluster on atlas (cloud.mongodb.com)
> ----------------------------------------------------------------
>
> Key: TEIID-5825
> URL: https://issues.jboss.org/browse/TEIID-5825
> Project: Teiid
> Issue Type: Bug
> Components: Connector API
> Affects Versions: 12.2
> Reporter: Marco Ardito
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.0, 12.3.1
>
>
> The issue is that teiid mongodb connector expects connection parameters based on the " Standard Connection String Format" instead of the "DNS Seedlist Connection Format", as defined in [https://docs.mongodb.com/manual/reference/connection-string|https://docs....]
> _
> "In addition to the standard connection format, MongoDB supports a DNS-constructed seed list. Using DNS to construct the available servers list allows more flexibility of deployment and the ability to change the servers in rotation without reconfiguring clients."_
> The following is a typical connection string for a DNS seedlist connection string:
> mongodb+srv://server.example.com/
> and:
> * a port number is not needed
> * a different prefix is used, instead of mongodb:// => mongodb+srv://
> I have a "free tier" cluster instance on cloud.mongodb,com (aka Atlas), which is limited in size and resources but should be functionally identical to a full sized paid cluster on the same platform, and it does not expire. A free tier can be activated here
> [https://www.mongodb.com/cloud/atlas#atlas-form-container|https://www.mong...]
> I tried with both the mongodb command line client and with the GUI tool Compass (https://www.mongodb.com/products/compass) which has a community edition
> and this different syntax works perfectly, while it is not supported by the current teiid connector, it seems
> there is a way to use the "old" syntax, prefixed by "mongodb:// " with server and port, to those Atlas clusters, but it is cumbersome, as it needs the user to specify more parameters, as "replicaSet" and "readPreference", at least. See https://docs.mongodb.com/manual/reference/connection-string
> With those additional settings I was able to connect with the Compass GUI tool, but not with the latest command line client (4.2), and anyway the teiid connector seems to not support those additional parameters,, I tried to add them as DS properties but always failed
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (TEIID-5823) CVE's in jboss-fuse/teiid
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5823?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5823:
---------------------------------------
The lucene change is from 5.5.4 to 7.1.0. This is used by hibernate-search-engine under infinispan. Even the latest version of that dependency uses 5.5.5. Upstream I'm going to update our infinispan dependency, but otherwise remove the lucene change. The expectation is that infinispan and/or hibernate will address this.
> CVE's in jboss-fuse/teiid
> -------------------------
>
> Key: TEIID-5823
> URL: https://issues.jboss.org/browse/TEIID-5823
> Project: Teiid
> Issue Type: Quality Risk
> Components: Build/Kits
> Affects Versions: 13.x, 12.3.1
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Blocker
> Fix For: 13.0, 7.5-12.3.1
>
>
> *Branch/Tag*: 12.3.1.fuse-750011-redhat-00001
> * *Severity*: {color:#f9423a}High{color}
> 1. apache commons collections
> * Vulnerability ID: CVE-2015-6420
> 2. org.apache.lucene:lucene-queryparser - Remote Code Execution (RCE)
> * Vulnerability ID: CVE-2017-12629
> 3. org.slf4j:slf4j-ext - Access Restriction Bypass
> * Vulnerability ID: CVE-2018-8088
> These changes will be committed to the teiid/teiid product branch 7.5-12.3.x and to master.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (TEIID-5823) CVE's in jboss-fuse/teiid
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5823?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5823:
---------------------------------------
Actually this is also breaking things on master, I just didn't see it because the wildfly build was pulled off of travis. I'll see what can be done.
> CVE's in jboss-fuse/teiid
> -------------------------
>
> Key: TEIID-5823
> URL: https://issues.jboss.org/browse/TEIID-5823
> Project: Teiid
> Issue Type: Quality Risk
> Components: Build/Kits
> Affects Versions: 13.x, 12.3.1
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Blocker
> Fix For: 13.0, 7.5-12.3.1
>
>
> *Branch/Tag*: 12.3.1.fuse-750011-redhat-00001
> * *Severity*: {color:#f9423a}High{color}
> 1. apache commons collections
> * Vulnerability ID: CVE-2015-6420
> 2. org.apache.lucene:lucene-queryparser - Remote Code Execution (RCE)
> * Vulnerability ID: CVE-2017-12629
> 3. org.slf4j:slf4j-ext - Access Restriction Bypass
> * Vulnerability ID: CVE-2018-8088
> These changes will be committed to the teiid/teiid product branch 7.5-12.3.x and to master.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months