[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 resolved TEIID-5827.
-----------------------------------
Resolution: Done
Updated the name and the logic in getDataSource to look at the xa-datasource-properties as well.
> 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... ]
Work on TEIID-5825 started by Steven Hawkins.
---------------------------------------------
> 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
>
> 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-5827) XA datasource properties are undefined
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5827?page=com.atlassian.jira.plugin... ]
Work on TEIID-5827 started by Steven Hawkins.
---------------------------------------------
> XA datasource properties are undefined
> --------------------------------------
>
> Key: TEIID-5827
> URL: https://issues.jboss.org/browse/TEIID-5827
> Project: Teiid
> Issue Type: Bug
> 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 updated TEIID-5827:
----------------------------------
Fix Version/s: 13.0
12.2.2
12.3.1
> 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 updated TEIID-5827:
----------------------------------
Component/s: AdminApi
> 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-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 resolved TEIID-5823.
-----------------------------------
Fix Version/s: 7.5-12.3.1
13.0
Resolution: Done
Merged the pull requests and added a product fix version.
> 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: 7.5-12.3.1, 13.0
>
>
> *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] (TEIIDSB-127) "No registered data sources found" if used "management.server.port=8081"
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-127?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIIDSB-127.
------------------------------------
Resolution: Cannot Reproduce
This is not reproducible for me. Updated the port configuration and started successfully:
2019-10-14 09:28:38.040 INFO 22557 --- [ main] o.s.b.w.e.u.UndertowServletWebServer : Undertow started on port(s) 8080 (http) with context path '/foo'
2019-10-14 09:28:38.146 INFO 22557 --- [ main] io.undertow.servlet : Initializing Spring embedded WebApplicationContext
2019-10-14 09:28:38.146 INFO 22557 --- [ main] o.s.web.context.ContextLoader : Root WebApplicationContext: initialization completed in 101 ms
2019-10-14 09:28:38.180 INFO 22557 --- [ main] o.s.b.a.e.web.EndpointLinksResolver : Exposing 2 endpoint(s) beneath base path '/actuator'
2019-10-14 09:28:38.242 INFO 22557 --- [ main] org.teiid.RUNTIME.VDBLifeCycleListener : TEIID40120 VDB customer.1 will be removed from the repository
2019-10-14 09:28:38.242 INFO 22557 --- [ main] org.teiid.RUNTIME.VDBLifeCycleListener : TEIID40119 VDB customer.1 removed from the repository
2019-10-14 09:28:38.243 INFO 22557 --- [ main] org.teiid.RUNTIME.VDBLifeCycleListener : TEIID40118 VDB customer.1 added to the repository
2019-10-14 09:28:38.243 INFO 22557 --- [ main] org.teiid.RUNTIME : TEIID50029 VDB customer.1 model "virt" metadata is currently being loaded. Start Time: 10/14/19 9:28 AM
2019-10-14 09:28:38.244 INFO 22557 --- [ main] org.teiid.RUNTIME : TEIID50030 VDB customer.1 model "virt" metadata loaded. End Time: 10/14/19 9:28 AM
2019-10-14 09:28:38.244 INFO 22557 --- [ main] org.teiid.RUNTIME : TEIID50029 VDB customer.1 model "accounts" metadata is currently being loaded. Start Time: 10/14/19 9:28 AM
2019-10-14 09:28:38.244 INFO 22557 --- [ main] org.teiid.RUNTIME : TEIID50030 VDB customer.1 model "accounts" metadata loaded. End Time: 10/14/19 9:28 AM
2019-10-14 09:28:38.280 INFO 22557 --- [ main] org.teiid.RUNTIME.VDBLifeCycleListener : TEIID40003 VDB customer.1 is set to ACTIVE
2019-10-14 09:28:38.289 INFO 22557 --- [ main] o.s.b.w.e.u.UndertowServletWebServer : Undertow started on port(s) 8081 (http) with context path ''
2019-10-14 09:28:38.293 INFO 22557 --- [ main] org.teiid.spring.example.Application : Started Application in 7.577 seconds (JVM running for 8.036)
Issued a query that utilized a database connection without a problem.
If there is more context you can provide from your configuration or other details we may be able to determine what is going on in your case.
> "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 Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-127?page=com.atlassian.jira.plugi... ]
Work on TEIIDSB-127 started by Steven Hawkins.
----------------------------------------------
> "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 updated TEIID-5827:
-----------------------------
Description:
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]
was:
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:
// 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);
}
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:
"xa-datasource-properties" => {
"DatabaseName" => undefined,
"PortNumber" => undefined,
"ServerName" => undefined
}
more details in the following forum discussion link: [https://developer.jboss.org/thread/280411?start=15&tstart=0]
> XA datasource properties are undefined
> --------------------------------------
>
> Key: TEIID-5827
> URL: https://issues.jboss.org/browse/TEIID-5827
> Project: Teiid
> Issue Type: Bug
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
> Priority: Major
>
> 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