October 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-130) An error should occur if the vdb file is not found

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-130?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIIDSB-130. ------------------------------------ Resolution: Done Moved up the check for non-existent vdb file into the auto configuration. > An error should occur if the vdb file is not found > -------------------------------------------------- > > Key: TEIIDSB-130 > URL: https://issues.jboss.org/browse/TEIIDSB-130 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Steven Hawkins > Priority: Major > Fix For: 1.3.0 > > > At some point with a previous change I think I removed the exception thrown when the vdb file is not found - but that can be confusing as the implicit vdb will be used instead. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-130) An error should occur if the vdb file is not found

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-130?page=com.atlassian.jira.plugi... ] Steven Hawkins reassigned TEIIDSB-130: -------------------------------------- Assignee: Steven Hawkins > An error should occur if the vdb file is not found > -------------------------------------------------- > > Key: TEIIDSB-130 > URL: https://issues.jboss.org/browse/TEIIDSB-130 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.0 > > > At some point with a previous change I think I removed the exception thrown when the vdb file is not found - but that can be confusing as the implicit vdb will be used instead. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-130) An error should occur if the vdb file is not found

by Steven Hawkins (Jira)

Steven Hawkins created TEIIDSB-130: -------------------------------------- Summary: An error should occur if the vdb file is not found Key: TEIIDSB-130 URL: https://issues.jboss.org/browse/TEIIDSB-130 Project: Teiid Spring Boot Issue Type: Quality Risk Components: core Reporter: Steven Hawkins Fix For: 1.3.0 At some point with a previous change I think I removed the exception thrown when the vdb file is not found - but that can be confusing as the implicit vdb will be used instead. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[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 commented on TEIIDSB-127: ---------------------------------------- The attached project reproduces his issue. The old pr that tried to use the ApplicationContext will reproduce the other issue (getting a DataSource bean before Spring Data initializes it). > "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: Ramesh Reddy > Priority: Major > Attachments: TEIIDSB-127.zip > > > 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

1
0
0 / 0

[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 updated TEIIDSB-127: ----------------------------------- Attachment: TEIIDSB-127.zip > "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: Ramesh Reddy > Priority: Major > Attachments: TEIIDSB-127.zip > > > 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

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-127) "No registered data sources found" if used "management.server.port=8081"

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-127?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIIDSB-127: -------------------------------------- Sorry, I haven't had time to contribute to this yet, yes, that is fine. Please give me any test case you may have for my testing. > "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: Ramesh Reddy > 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

1
0
0 / 0

[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 commented on TEIIDSB-127: ---------------------------------------- I'm kicking this over to you [~rareddy]. My best guess is using explicit depends on as nothing else seems to work. > "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: Ramesh Reddy > 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

1
0
0 / 0

[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 reassigned TEIIDSB-127: -------------------------------------- Assignee: Ramesh Reddy (was: 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: Ramesh Reddy > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-5818) separate the wildfly build/repo

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5818?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5818. ----------------------------------- Resolution: Done Marking this as initially resolved. Everything wildfly is now separated into a single profile and module. I don't see a need yet to separate to an additional repository. > separate the wildfly build/repo > ------------------------------- > > Key: TEIID-5818 > URL: https://issues.jboss.org/browse/TEIID-5818 > Project: Teiid > Issue Type: Task > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > The wildfly build should be further decoupled from the Teiid build. Initially this could be as simple as removing the module references from the parent pom. We also need to update the wildfly logic poms to start referencing teiid artifacts via a distinct version (rather than project.version). > From there we can decide how to promote it into its own repository. As it doesn't seem likely that we'll invest in a mechanism to update teiid-wildly using some kind of teiid core overlay, we'll likely just do a teiid-wildfly release with every teiid release. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-129) allow connection to mongodb cluster on atlas (cloud.mongodb.com)

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-129?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-129: --------------------------------- Sprint: SDI Sprint 54 > allow connection to mongodb cluster on atlas (cloud.mongodb.com) > ---------------------------------------------------------------- > > Key: TEIIDSB-129 > URL: https://issues.jboss.org/browse/TEIIDSB-129 > Project: Teiid Spring Boot > Issue Type: Bug > Components: datasource > Reporter: Marco Ardito > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.0 > > > 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

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2019