August 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3667) LDAPSyncQueryExecution.createSearchContext() hides a root cause when an error occurs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3667?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3667. ----------------------------------- Resolution: Done Resolved by adding the underlying exception in all circumstances and not individually logging the error in LDAPSyncQueryExecution. This makes the behavior more consistent with the other translators. > LDAPSyncQueryExecution.createSearchContext() hides a root cause when an error occurs > ------------------------------------------------------------------------------------ > > Key: TEIID-3667 > URL: https://issues.jboss.org/browse/TEIID-3667 > Project: Teiid > Issue Type: Quality Risk > Components: LDAP Connector > Affects Versions: 8.7 > Environment: JDV6.1, Teiid 8.11.x > Reporter: Hisanobu Okuda > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.12 > > > When an LDAP error occurs, org.teiid.translator.ldap.LDAPSyncQueryExecution.createSearchContext() shows the following error log: > {code} > 14:23:18,723 ERROR [org.teiid.CONNECTOR] (Worker27_QueryProcessorQueue616) TEIID12002 Attempted to search context: dc=test.org > {code} > but does mention nothing about a cause. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3667) LDAPSyncQueryExecution.createSearchContext() hides a root cause when an error occurs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3667?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3667: ---------------------------------- Issue Type: Quality Risk (was: Feature Request) Fix Version/s: 8.12 Priority: Minor (was: Major) Affects Version/s: 8.7 (was: 8.7.3) (was: 8.11.2) > LDAPSyncQueryExecution.createSearchContext() hides a root cause when an error occurs > ------------------------------------------------------------------------------------ > > Key: TEIID-3667 > URL: https://issues.jboss.org/browse/TEIID-3667 > Project: Teiid > Issue Type: Quality Risk > Components: LDAP Connector > Affects Versions: 8.7 > Environment: JDV6.1, Teiid 8.11.x > Reporter: Hisanobu Okuda > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.12 > > > When an LDAP error occurs, org.teiid.translator.ldap.LDAPSyncQueryExecution.createSearchContext() shows the following error log: > {code} > 14:23:18,723 ERROR [org.teiid.CONNECTOR] (Worker27_QueryProcessorQueue616) TEIID12002 Attempted to search context: dc=test.org > {code} > but does mention nothing about a cause. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3667) LDAPSyncQueryExecution.createSearchContext() hides a root cause when an error occurs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3667?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3667: --------------------------------------- There was another of these fixed with TEIID-3411. I'll check to see if there are any others. > LDAPSyncQueryExecution.createSearchContext() hides a root cause when an error occurs > ------------------------------------------------------------------------------------ > > Key: TEIID-3667 > URL: https://issues.jboss.org/browse/TEIID-3667 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 8.7.3, 8.11.2 > Environment: JDV6.1, Teiid 8.11.x > Reporter: Hisanobu Okuda > Assignee: Steven Hawkins > > When an LDAP error occurs, org.teiid.translator.ldap.LDAPSyncQueryExecution.createSearchContext() shows the following error log: > {code} > 14:23:18,723 ERROR [org.teiid.CONNECTOR] (Worker27_QueryProcessorQueue616) TEIID12002 Attempted to search context: dc=test.org > {code} > but does mention nothing about a cause. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3664) Only JDK 1.7 can build Teiid code base success

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3664?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3664: --------------------------------------- I haven't seen indeterminate behavior with that test, but I wouldn't mind resolving this by removing the socket pooling. That's a very old feature of the socket layer that we carried forward, and it is generally of little benefit. > Only JDK 1.7 can build Teiid code base success > ---------------------------------------------- > > Key: TEIID-3664 > URL: https://issues.jboss.org/browse/TEIID-3664 > Project: Teiid > Issue Type: Quality Risk > Components: Build/Kits > Affects Versions: 8.12 > Reporter: Kylin Soong > Assignee: Steven Hawkins > Fix For: 8.12 > > > The following depiction exist in README.md > {code} > install JDK 1.7 or higher > {code} > But the build commands > {code} > $ mvn clean install -P release -s settings.xml > {code} > will execute failed if use JDK 1.8 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3667) LDAPSyncQueryExecution.createSearchContext() hides a root cause when an error occurs

by Hisanobu Okuda (JIRA)

[ https://issues.jboss.org/browse/TEIID-3667?page=com.atlassian.jira.plugin... ] Hisanobu Okuda commented on TEIID-3667: --------------------------------------- pull request: https://github.com/teiid/teiid/pull/518 > LDAPSyncQueryExecution.createSearchContext() hides a root cause when an error occurs > ------------------------------------------------------------------------------------ > > Key: TEIID-3667 > URL: https://issues.jboss.org/browse/TEIID-3667 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 8.7.3, 8.11.2 > Environment: JDV6.1, Teiid 8.11.x > Reporter: Hisanobu Okuda > Assignee: Steven Hawkins > > When an LDAP error occurs, org.teiid.translator.ldap.LDAPSyncQueryExecution.createSearchContext() shows the following error log: > {code} > 14:23:18,723 ERROR [org.teiid.CONNECTOR] (Worker27_QueryProcessorQueue616) TEIID12002 Attempted to search context: dc=test.org > {code} > but does mention nothing about a cause. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3667) LDAPSyncQueryExecution.createSearchContext() hides a root cause when an error occurs

by Hisanobu Okuda (JIRA)

Hisanobu Okuda created TEIID-3667: ------------------------------------- Summary: LDAPSyncQueryExecution.createSearchContext() hides a root cause when an error occurs Key: TEIID-3667 URL: https://issues.jboss.org/browse/TEIID-3667 Project: Teiid Issue Type: Feature Request Components: LDAP Connector Affects Versions: 8.11.2, 8.7.3 Environment: JDV6.1, Teiid 8.11.x Reporter: Hisanobu Okuda Assignee: Steven Hawkins When an LDAP error occurs, org.teiid.translator.ldap.LDAPSyncQueryExecution.createSearchContext() shows the following error log: {code} 14:23:18,723 ERROR [org.teiid.CONNECTOR] (Worker27_QueryProcessorQueue616) TEIID12002 Attempted to search context: dc=test.org {code} but does mention nothing about a cause. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3664) Only JDK 1.7 can build Teiid code base success

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3664?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-3664: ------------------------------------ {code} ------------------------------------------------------------------------------- Test set: org.teiid.transport.TestCommSockets ------------------------------------------------------------------------------- Tests run: 17, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.486 sec <<< FAILURE! - in org.teiid.transport.TestCommSockets testConnectWithPooling(org.teiid.transport.TestCommSockets) Time elapsed: 0.086 sec <<< FAILURE! java.lang.AssertionError: expected:<1> but was:<2> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:743) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:555) at org.junit.Assert.assertEquals(Assert.java:542) at org.teiid.transport.TestCommSockets.testConnectWithPooling(TestCommSockets.java:119) {code} It seems the test not related with JDK version, but if use 1.8, above error may cause build failed. I have repeat build several times with 1.8, most of time(2/3) above error throw, build failed If build with 1.7, always success. > Only JDK 1.7 can build Teiid code base success > ---------------------------------------------- > > Key: TEIID-3664 > URL: https://issues.jboss.org/browse/TEIID-3664 > Project: Teiid > Issue Type: Quality Risk > Components: Build/Kits > Affects Versions: 8.12 > Reporter: Kylin Soong > Assignee: Steven Hawkins > Fix For: 8.12 > > > The following depiction exist in README.md > {code} > install JDK 1.7 or higher > {code} > But the build commands > {code} > $ mvn clean install -P release -s settings.xml > {code} > will execute failed if use JDK 1.8 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3666) VDB can deploy before datasource is bound

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3666?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3666. ----------------------------------- Fix Version/s: 8.12 8.11.3 Resolution: Done Added the vdbstatuschecker to the model as a marker if it could still be retried. > VDB can deploy before datasource is bound > ----------------------------------------- > > Key: TEIID-3666 > URL: https://issues.jboss.org/browse/TEIID-3666 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.3 > Environment: JDBC driver for datasource is deployed in deployments/ directory of standalone instance > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.3 > > > A VDB can be deployed before the datasources it depends on are fully deployed and bound, resulting in the VDB never being marked as ACTIVE. This appears to be exclusive to environments where the JDBC driver for the datasource is deployed through use of the standalone deployments/ directory. If the driver is deployed as a module, then the risk of the issue is lowered or eliminated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3666) VDB can deploy before datasource is bound

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3666?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3666: --------------------------------------- Yes there is an issue here. If the bound events happens at the same time as the failed loads, and the thread ordering puts the bound event in between the two failures, then the second failed load will not be retried. > VDB can deploy before datasource is bound > ----------------------------------------- > > Key: TEIID-3666 > URL: https://issues.jboss.org/browse/TEIID-3666 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.3 > Environment: JDBC driver for datasource is deployed in deployments/ directory of standalone instance > Reporter: Marc Shirley > Assignee: Steven Hawkins > > A VDB can be deployed before the datasources it depends on are fully deployed and bound, resulting in the VDB never being marked as ACTIVE. This appears to be exclusive to environments where the JDBC driver for the datasource is deployed through use of the standalone deployments/ directory. If the driver is deployed as a module, then the risk of the issue is lowered or eliminated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3666) VDB can deploy before datasource is bound

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3666?page=com.atlassian.jira.plugin... ] Work on TEIID-3666 started by Steven Hawkins. --------------------------------------------- > VDB can deploy before datasource is bound > ----------------------------------------- > > Key: TEIID-3666 > URL: https://issues.jboss.org/browse/TEIID-3666 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.3 > Environment: JDBC driver for datasource is deployed in deployments/ directory of standalone instance > Reporter: Marc Shirley > Assignee: Steven Hawkins > > A VDB can be deployed before the datasources it depends on are fully deployed and bound, resulting in the VDB never being marked as ACTIVE. This appears to be exclusive to environments where the JDBC driver for the datasource is deployed through use of the standalone deployments/ directory. If the driver is deployed as a module, then the risk of the issue is lowered or eliminated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2015