August 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4389) Local connection waits for active VDB 1, 000, 000 times longer than specified in waitForLoad property

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-4389?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-4389: ------------------------------------- Sorry! I forgot to set it. > Local connection waits for active VDB 1,000,000 times longer than specified in waitForLoad property > --------------------------------------------------------------------------------------------------- > > Key: TEIID-4389 > URL: https://issues.jboss.org/browse/TEIID-4389 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.5 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If user specifies waitForLoad connection property in URL, Teiid waits for longer time than specified in the property. > I believe it is because you call Object.wait(long) method with wrong parameter \[1\]. In combination with TEIID-4388, from users point of view, local connection waits for active VDB for ever. > \[1\] See this [commit|https://github.com/teiid/teiid/commit/d7e161ff04c77f8f2da85b2debb1...]. You call method like _vdb.wait(timeOutNanos);_, but from javadoc: *timeout - the maximum time to wait in milliseconds.* It means that Teiid waits 1,000,000 times longer than specified in parameter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4388) If model fails to load native metadata, VDB has still status LOADING

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-4388?page=com.atlassian.jira.plugin... ] Juraj Duráni updated TEIID-4388: -------------------------------- Affects Version/s: 8.12.5 > If model fails to load native metadata, VDB has still status LOADING > -------------------------------------------------------------------- > > Key: TEIID-4388 > URL: https://issues.jboss.org/browse/TEIID-4388 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.5 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If one model fails to load native metadata, VDB's status is still LOADING. > {code:plain|title=CLI status} > [standalone@localhost:9999 /] /subsystem=teiid:get-vdb(vdb-name=test,vdb-version=1) > { > "outcome" => "success", > "result" => { > "vdb-name" => "test", > "status" => "LOADING", > "vdb-version" => 1, > ... > "models" => [ > { > "model-name" => "Source1", > ... > "metadata-status" => "LOADED" > }, > { > "model-name" => "Source2", > ... > "validity-errors" => [ > { > "severity" => "INFO", > "message" => "TEIID50029 VDB test.1 model \"Source2\" metadata is currently being loaded. Start Time: 8/17/16 7:41 AM" > }, > { > "severity" => "ERROR", > "message" => "TEIID31178 Could not obtain connection for schema Source2, but one is required for metadata load. " > } > ], > ... > "metadata-status" => "FAILED" > }, > { > "model-name" => "Source3", > ... > "metadata-status" => "LOADED" > } > ] > } > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4389) Local connection waits for active VDB 1, 000, 000 times longer than specified in waitForLoad property

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-4389?page=com.atlassian.jira.plugin... ] Juraj Duráni updated TEIID-4389: -------------------------------- Fix Version/s: (was: 8.12.x) > Local connection waits for active VDB 1,000,000 times longer than specified in waitForLoad property > --------------------------------------------------------------------------------------------------- > > Key: TEIID-4389 > URL: https://issues.jboss.org/browse/TEIID-4389 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.5 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If user specifies waitForLoad connection property in URL, Teiid waits for longer time than specified in the property. > I believe it is because you call Object.wait(long) method with wrong parameter \[1\]. In combination with TEIID-4388, from users point of view, local connection waits for active VDB for ever. > \[1\] See this [commit|https://github.com/teiid/teiid/commit/d7e161ff04c77f8f2da85b2debb1...]. You call method like _vdb.wait(timeOutNanos);_, but from javadoc: *timeout - the maximum time to wait in milliseconds.* It means that Teiid waits 1,000,000 times longer than specified in parameter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4389) Local connection waits for active VDB 1, 000, 000 times longer than specified in waitForLoad property

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-4389?page=com.atlassian.jira.plugin... ] Juraj Duráni updated TEIID-4389: -------------------------------- Affects Version/s: 8.12.5 > Local connection waits for active VDB 1,000,000 times longer than specified in waitForLoad property > --------------------------------------------------------------------------------------------------- > > Key: TEIID-4389 > URL: https://issues.jboss.org/browse/TEIID-4389 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.5 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If user specifies waitForLoad connection property in URL, Teiid waits for longer time than specified in the property. > I believe it is because you call Object.wait(long) method with wrong parameter \[1\]. In combination with TEIID-4388, from users point of view, local connection waits for active VDB for ever. > \[1\] See this [commit|https://github.com/teiid/teiid/commit/d7e161ff04c77f8f2da85b2debb1...]. You call method like _vdb.wait(timeOutNanos);_, but from javadoc: *timeout - the maximum time to wait in milliseconds.* It means that Teiid waits 1,000,000 times longer than specified in parameter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4389) Local connection waits for active VDB 1, 000, 000 times longer than specified in waitForLoad property

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-4389?page=com.atlassian.jira.plugin... ] Juraj Duráni updated TEIID-4389: -------------------------------- Fix Version/s: 8.12.x > Local connection waits for active VDB 1,000,000 times longer than specified in waitForLoad property > --------------------------------------------------------------------------------------------------- > > Key: TEIID-4389 > URL: https://issues.jboss.org/browse/TEIID-4389 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.5 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If user specifies waitForLoad connection property in URL, Teiid waits for longer time than specified in the property. > I believe it is because you call Object.wait(long) method with wrong parameter \[1\]. In combination with TEIID-4388, from users point of view, local connection waits for active VDB for ever. > \[1\] See this [commit|https://github.com/teiid/teiid/commit/d7e161ff04c77f8f2da85b2debb1...]. You call method like _vdb.wait(timeOutNanos);_, but from javadoc: *timeout - the maximum time to wait in milliseconds.* It means that Teiid waits 1,000,000 times longer than specified in parameter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4389) Local connection waits for active VDB 1, 000, 000 times longer than specified in waitForLoad property

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4389?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4389: ------------------------------------- Can set version, the master looks different. > Local connection waits for active VDB 1,000,000 times longer than specified in waitForLoad property > --------------------------------------------------------------------------------------------------- > > Key: TEIID-4389 > URL: https://issues.jboss.org/browse/TEIID-4389 > Project: Teiid > Issue Type: Bug > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If user specifies waitForLoad connection property in URL, Teiid waits for longer time than specified in the property. > I believe it is because you call Object.wait(long) method with wrong parameter \[1\]. In combination with TEIID-4388, from users point of view, local connection waits for active VDB for ever. > \[1\] See this [commit|https://github.com/teiid/teiid/commit/d7e161ff04c77f8f2da85b2debb1...]. You call method like _vdb.wait(timeOutNanos);_, but from javadoc: *timeout - the maximum time to wait in milliseconds.* It means that Teiid waits 1,000,000 times longer than specified in parameter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4388) If model fails to load native metadata, VDB has still status LOADING

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-4388?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-4388: ------------------------------------- So, what about changing this to feature request? Will it be hard to implement such timeout? > If model fails to load native metadata, VDB has still status LOADING > -------------------------------------------------------------------- > > Key: TEIID-4388 > URL: https://issues.jboss.org/browse/TEIID-4388 > Project: Teiid > Issue Type: Bug > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If one model fails to load native metadata, VDB's status is still LOADING. > {code:plain|title=CLI status} > [standalone@localhost:9999 /] /subsystem=teiid:get-vdb(vdb-name=test,vdb-version=1) > { > "outcome" => "success", > "result" => { > "vdb-name" => "test", > "status" => "LOADING", > "vdb-version" => 1, > ... > "models" => [ > { > "model-name" => "Source1", > ... > "metadata-status" => "LOADED" > }, > { > "model-name" => "Source2", > ... > "validity-errors" => [ > { > "severity" => "INFO", > "message" => "TEIID50029 VDB test.1 model \"Source2\" metadata is currently being loaded. Start Time: 8/17/16 7:41 AM" > }, > { > "severity" => "ERROR", > "message" => "TEIID31178 Could not obtain connection for schema Source2, but one is required for metadata load. " > } > ], > ... > "metadata-status" => "FAILED" > }, > { > "model-name" => "Source3", > ... > "metadata-status" => "LOADED" > } > ] > } > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4388) If model fails to load native metadata, VDB has still status LOADING

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4388?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4388: ------------------------------------- I do not there is a timeout, but I see that could be good enhancement. > If model fails to load native metadata, VDB has still status LOADING > -------------------------------------------------------------------- > > Key: TEIID-4388 > URL: https://issues.jboss.org/browse/TEIID-4388 > Project: Teiid > Issue Type: Bug > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If one model fails to load native metadata, VDB's status is still LOADING. > {code:plain|title=CLI status} > [standalone@localhost:9999 /] /subsystem=teiid:get-vdb(vdb-name=test,vdb-version=1) > { > "outcome" => "success", > "result" => { > "vdb-name" => "test", > "status" => "LOADING", > "vdb-version" => 1, > ... > "models" => [ > { > "model-name" => "Source1", > ... > "metadata-status" => "LOADED" > }, > { > "model-name" => "Source2", > ... > "validity-errors" => [ > { > "severity" => "INFO", > "message" => "TEIID50029 VDB test.1 model \"Source2\" metadata is currently being loaded. Start Time: 8/17/16 7:41 AM" > }, > { > "severity" => "ERROR", > "message" => "TEIID31178 Could not obtain connection for schema Source2, but one is required for metadata load. " > } > ], > ... > "metadata-status" => "FAILED" > }, > { > "model-name" => "Source3", > ... > "metadata-status" => "LOADED" > } > ] > } > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4388) If model fails to load native metadata, VDB has still status LOADING

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-4388?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-4388: ------------------------------------- Is there any default time out in case data source is down for longer period of time? > If model fails to load native metadata, VDB has still status LOADING > -------------------------------------------------------------------- > > Key: TEIID-4388 > URL: https://issues.jboss.org/browse/TEIID-4388 > Project: Teiid > Issue Type: Bug > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If one model fails to load native metadata, VDB's status is still LOADING. > {code:plain|title=CLI status} > [standalone@localhost:9999 /] /subsystem=teiid:get-vdb(vdb-name=test,vdb-version=1) > { > "outcome" => "success", > "result" => { > "vdb-name" => "test", > "status" => "LOADING", > "vdb-version" => 1, > ... > "models" => [ > { > "model-name" => "Source1", > ... > "metadata-status" => "LOADED" > }, > { > "model-name" => "Source2", > ... > "validity-errors" => [ > { > "severity" => "INFO", > "message" => "TEIID50029 VDB test.1 model \"Source2\" metadata is currently being loaded. Start Time: 8/17/16 7:41 AM" > }, > { > "severity" => "ERROR", > "message" => "TEIID31178 Could not obtain connection for schema Source2, but one is required for metadata load. " > } > ], > ... > "metadata-status" => "FAILED" > }, > { > "model-name" => "Source3", > ... > "metadata-status" => "LOADED" > } > ] > } > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4388) If model fails to load native metadata, VDB has still status LOADING

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4388?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4388: ------------------------------------- Because once the connection is available, it will retry. Where as if there is validation error then it will move to the FAILED state, which means you need to make modifications before you can re-deploy. Where as LOADING just intermediate state, where data source could be down temporarily or issues can be solved without re-deploy > If model fails to load native metadata, VDB has still status LOADING > -------------------------------------------------------------------- > > Key: TEIID-4388 > URL: https://issues.jboss.org/browse/TEIID-4388 > Project: Teiid > Issue Type: Bug > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If one model fails to load native metadata, VDB's status is still LOADING. > {code:plain|title=CLI status} > [standalone@localhost:9999 /] /subsystem=teiid:get-vdb(vdb-name=test,vdb-version=1) > { > "outcome" => "success", > "result" => { > "vdb-name" => "test", > "status" => "LOADING", > "vdb-version" => 1, > ... > "models" => [ > { > "model-name" => "Source1", > ... > "metadata-status" => "LOADED" > }, > { > "model-name" => "Source2", > ... > "validity-errors" => [ > { > "severity" => "INFO", > "message" => "TEIID50029 VDB test.1 model \"Source2\" metadata is currently being loaded. Start Time: 8/17/16 7:41 AM" > }, > { > "severity" => "ERROR", > "message" => "TEIID31178 Could not obtain connection for schema Source2, but one is required for metadata load. " > } > ], > ... > "metadata-status" => "FAILED" > }, > { > "model-name" => "Source3", > ... > "metadata-status" => "LOADED" > } > ] > } > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2016