[JBoss JIRA] (TEIIDDES-2908) Errors in Error Log when deploying/undeploying a fuse project into Fuse on EAP
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2908?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2908.
------------------------------------
Resolution: Done
10.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/078f98bc94432b541...
Hopefully I caught/wrapped all the lazy calls to Designer's adapterServer() to prevent logging if this error code shows up.
> Errors in Error Log when deploying/undeploying a fuse project into Fuse on EAP
> ------------------------------------------------------------------------------
>
> Key: TEIIDDES-2908
> URL: https://issues.jboss.org/browse/TEIIDDES-2908
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.1
> Environment: JBDS 9.1.0.GA + TD 10.0.1.Final-v20160713-1749-B16
> Reporter: Andrej Podhradsky
> Assignee: Barry LaFond
> Fix For: 10.0.2
>
> Attachments: errorLog.txt
>
>
> During deploying/undeploying a fuse project into Fuse on EAP 6.3.0.CR2 I saw the following error in Error Log
> {code}
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-attribute" for [
> {"socket-binding-group" => "standard-sockets"},
> {"socket-binding" => "teiid-jdbc"}
> ]. Failure was "JBAS014807: Management resource '[
> (\"socket-binding-group\" => \"standard-sockets\"),
> (\"socket-binding\" => \"teiid-jdbc\")
> ]' not found".
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:361)
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9ManagerService.execute(Wildfly9ManagerService.java:171)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.jboss.ide.eclipse.as.management.core.service.DelegatingManagerService.execute(DelegatingManagerService.java:132)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.executeRequest(JBoss7ServerUtil.java:77)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.getJdbcPort(JBoss7ServerUtil.java:237)
> at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:114)
> at org.eclipse.wst.server.core.internal.ResourceManager.fireServerEvent(ResourceManager.java:560)
> at org.eclipse.wst.server.core.internal.ResourceManager.addServer(ResourceManager.java:712)
> at org.eclipse.wst.server.core.internal.Server.saveToMetadata(Server.java:477)
> at org.eclipse.wst.server.core.internal.Base.doSave(Base.java:266)
> at org.eclipse.wst.server.core.internal.Server.doSave(Server.java:466)
> at org.eclipse.wst.server.core.internal.ServerWorkingCopy.save(ServerWorkingCopy.java:433)
> at org.eclipse.wst.server.ui.internal.wizard.WizardTaskUtil.saveServer(WizardTaskUtil.java:112)
> at org.eclipse.wst.server.ui.internal.wizard.WizardTaskUtil$2.performFinish(WizardTaskUtil.java:51)
> at org.eclipse.wst.server.ui.internal.wizard.TaskWizard.executeTask(TaskWizard.java:268)
> at org.eclipse.wst.server.ui.internal.wizard.TaskWizard$2.run(TaskWizard.java:215)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2225)
> at org.eclipse.wst.server.ui.internal.wizard.page.WorkspaceRunnableAdapter.run(WorkspaceRunnableAdapter.java:35)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> Caused by: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-attribute" for [
> {"socket-binding-group" => "standard-sockets"},
> {"socket-binding" => "teiid-jdbc"}
> ]. Failure was "JBAS014807: Management resource '[
> (\"socket-binding-group\" => \"standard-sockets\"),
> (\"socket-binding\" => \"teiid-jdbc\")
> ]' not found".
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:352)
> ... 21 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2971) Create Primary Keys when JDG materialization is created
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2971?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2971.
------------------------------------
Resolution: Out of Date
PK's were already being created on source tables if they exist on views. Marking as out of date
> Create Primary Keys when JDG materialization is created
> -------------------------------------------------------
>
> Key: TEIIDDES-2971
> URL: https://issues.jboss.org/browse/TEIIDDES-2971
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling
> Affects Versions: 10.0.2
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 10.0.2
>
>
> When a view is being materialized for JDG, the following keys need to be created:
> - as part of the cacheTypeMap property, the 3rd parameter primary key column: (cacheName:ClassName:primarykeycolumn)
> a primary key should be made containing that column on both of the newly created tables.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2930) Dynamic VDB should contain full path to the materialized table
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2930?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2930.
------------------------------------
Resolution: Done
retesting shows as fixed
> Dynamic VDB should contain full path to the materialized table
> --------------------------------------------------------------
>
> Key: TEIIDDES-2930
> URL: https://issues.jboss.org/browse/TEIIDDES-2930
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Fix For: 10.0.2
>
> Attachments: completeJDGproject.zip, customer-cache-table-info.png, customer-view-info.png, jdgCustomer.zip, screenshot1.png, screenshotProp.png
>
>
> I have a table (CustomerViewMat.Customer) and I set materialized table to another model (CustomerMatCache.Customer) (screenshot1) .I create VDB and dynamic VDB. When I want to deploy this dynamic VDB to the server, server shows me error:
> TEIID31088 The materialization table Customer defined on view CustomerViewMat.Customer, must be defined with "schema" qualifier that represents PHYSICAL model.
> I noticed that in the dynamicVDB in the CustomerViewMat model is:
> {code:java}
> OPTIONS(MATERIALIZED 'TRUE', MATERIALIZED_TABLE 'Customer', "teiid_rel: ...
> {code}
> I think that this happens because Customer table is in the CustomerViewMat and CustomerMatCache too. But in the properties (Screenshot1) is set correctly model. (CustomerMatCache)
> When I set full path, vdb was deployed sucessfully
> {code:java}
> OPTIONS(MATERIALIZED 'TRUE', MATERIALIZED_TABLE 'CustomerMatCache.Customer', "teiid_rel: ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2930) Dynamic VDB should contain full path to the materialized table
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2930?page=com.atlassian.jira.plu... ]
Matus Makovy commented on TEIIDDES-2930:
----------------------------------------
[~apodhrad] Yes, from my point of view this should be OK. [~blafond] Should I close it now or will you change the state to resolved and I will close it after?
> Dynamic VDB should contain full path to the materialized table
> --------------------------------------------------------------
>
> Key: TEIIDDES-2930
> URL: https://issues.jboss.org/browse/TEIIDDES-2930
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Fix For: 10.0.2
>
> Attachments: completeJDGproject.zip, customer-cache-table-info.png, customer-view-info.png, jdgCustomer.zip, screenshot1.png, screenshotProp.png
>
>
> I have a table (CustomerViewMat.Customer) and I set materialized table to another model (CustomerMatCache.Customer) (screenshot1) .I create VDB and dynamic VDB. When I want to deploy this dynamic VDB to the server, server shows me error:
> TEIID31088 The materialization table Customer defined on view CustomerViewMat.Customer, must be defined with "schema" qualifier that represents PHYSICAL model.
> I noticed that in the dynamicVDB in the CustomerViewMat model is:
> {code:java}
> OPTIONS(MATERIALIZED 'TRUE', MATERIALIZED_TABLE 'Customer', "teiid_rel: ...
> {code}
> I think that this happens because Customer table is in the CustomerViewMat and CustomerMatCache too. But in the properties (Screenshot1) is set correctly model. (CustomerMatCache)
> When I set full path, vdb was deployed sucessfully
> {code:java}
> OPTIONS(MATERIALIZED 'TRUE', MATERIALIZED_TABLE 'CustomerMatCache.Customer', "teiid_rel: ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2930) Dynamic VDB should contain full path to the materialized table
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2930?page=com.atlassian.jira.plu... ]
Andrej Podhradsky commented on TEIIDDES-2930:
---------------------------------------------
[~mkralik], [~mmakovy] so is this issue fixed?
> Dynamic VDB should contain full path to the materialized table
> --------------------------------------------------------------
>
> Key: TEIIDDES-2930
> URL: https://issues.jboss.org/browse/TEIIDDES-2930
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Fix For: 10.0.2
>
> Attachments: completeJDGproject.zip, customer-cache-table-info.png, customer-view-info.png, jdgCustomer.zip, screenshot1.png, screenshotProp.png
>
>
> I have a table (CustomerViewMat.Customer) and I set materialized table to another model (CustomerMatCache.Customer) (screenshot1) .I create VDB and dynamic VDB. When I want to deploy this dynamic VDB to the server, server shows me error:
> TEIID31088 The materialization table Customer defined on view CustomerViewMat.Customer, must be defined with "schema" qualifier that represents PHYSICAL model.
> I noticed that in the dynamicVDB in the CustomerViewMat model is:
> {code:java}
> OPTIONS(MATERIALIZED 'TRUE', MATERIALIZED_TABLE 'Customer', "teiid_rel: ...
> {code}
> I think that this happens because Customer table is in the CustomerViewMat and CustomerMatCache too. But in the properties (Screenshot1) is set correctly model. (CustomerMatCache)
> When I set full path, vdb was deployed sucessfully
> {code:java}
> OPTIONS(MATERIALIZED 'TRUE', MATERIALIZED_TABLE 'CustomerMatCache.Customer', "teiid_rel: ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2908) Errors in Error Log when deploying/undeploying a fuse project into Fuse on EAP
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2908?page=com.atlassian.jira.plu... ]
Andrej Podhradsky reopened TEIIDDES-2908:
-----------------------------------------
Now, I'm getting the following error when I start the server
{code}
org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-children-names" for undefined. Failure was "JBAS013493: System boot is in process; execution of remote management operations is not currently available".
at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:361)
at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9ManagerService.execute(Wildfly9ManagerService.java:171)
at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
at org.jboss.ide.eclipse.as.management.core.service.DelegatingManagerService.execute(DelegatingManagerService.java:132)
at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.executeRequest(JBoss7ServerUtil.java:77)
at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.isTeiidServer(JBoss7ServerUtil.java:203)
at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptJBoss7Server(TeiidServerAdapterFactory.java:186)
at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptServer(TeiidServerAdapterFactory.java:87)
at org.teiid.designer.runtime.TeiidParentServerListener$1.tryConnecting(TeiidParentServerListener.java:260)
at org.teiid.designer.runtime.TeiidParentServerListener$1.run(TeiidParentServerListener.java:241)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-children-names" for undefined. Failure was "JBAS013493: System boot is in process; execution of remote management operations is not currently available".
at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:352)
... 11 more
{code}
Tested with Teiid Designer 10.0.2.Final-v20161027-2114-B64 (which includes the commit mentioned above).
> Errors in Error Log when deploying/undeploying a fuse project into Fuse on EAP
> ------------------------------------------------------------------------------
>
> Key: TEIIDDES-2908
> URL: https://issues.jboss.org/browse/TEIIDDES-2908
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.1
> Environment: JBDS 9.1.0.GA + TD 10.0.1.Final-v20160713-1749-B16
> Reporter: Andrej Podhradsky
> Assignee: Barry LaFond
> Fix For: 10.0.2
>
> Attachments: errorLog.txt
>
>
> During deploying/undeploying a fuse project into Fuse on EAP 6.3.0.CR2 I saw the following error in Error Log
> {code}
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-attribute" for [
> {"socket-binding-group" => "standard-sockets"},
> {"socket-binding" => "teiid-jdbc"}
> ]. Failure was "JBAS014807: Management resource '[
> (\"socket-binding-group\" => \"standard-sockets\"),
> (\"socket-binding\" => \"teiid-jdbc\")
> ]' not found".
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:361)
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9ManagerService.execute(Wildfly9ManagerService.java:171)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.jboss.ide.eclipse.as.management.core.service.DelegatingManagerService.execute(DelegatingManagerService.java:132)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.executeRequest(JBoss7ServerUtil.java:77)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.getJdbcPort(JBoss7ServerUtil.java:237)
> at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:114)
> at org.eclipse.wst.server.core.internal.ResourceManager.fireServerEvent(ResourceManager.java:560)
> at org.eclipse.wst.server.core.internal.ResourceManager.addServer(ResourceManager.java:712)
> at org.eclipse.wst.server.core.internal.Server.saveToMetadata(Server.java:477)
> at org.eclipse.wst.server.core.internal.Base.doSave(Base.java:266)
> at org.eclipse.wst.server.core.internal.Server.doSave(Server.java:466)
> at org.eclipse.wst.server.core.internal.ServerWorkingCopy.save(ServerWorkingCopy.java:433)
> at org.eclipse.wst.server.ui.internal.wizard.WizardTaskUtil.saveServer(WizardTaskUtil.java:112)
> at org.eclipse.wst.server.ui.internal.wizard.WizardTaskUtil$2.performFinish(WizardTaskUtil.java:51)
> at org.eclipse.wst.server.ui.internal.wizard.TaskWizard.executeTask(TaskWizard.java:268)
> at org.eclipse.wst.server.ui.internal.wizard.TaskWizard$2.run(TaskWizard.java:215)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2225)
> at org.eclipse.wst.server.ui.internal.wizard.page.WorkspaceRunnableAdapter.run(WorkspaceRunnableAdapter.java:35)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> Caused by: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-attribute" for [
> {"socket-binding-group" => "standard-sockets"},
> {"socket-binding" => "teiid-jdbc"}
> ]. Failure was "JBAS014807: Management resource '[
> (\"socket-binding-group\" => \"standard-sockets\"),
> (\"socket-binding\" => \"teiid-jdbc\")
> ]' not found".
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:352)
> ... 21 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2971) Create Primary Keys when JDG materialization is created
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2971?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-2971:
---------------------------------------
With the latest test build, if the View has a PK defined, then the generated JDG source tables will have the same primary key.
> Create Primary Keys when JDG materialization is created
> -------------------------------------------------------
>
> Key: TEIIDDES-2971
> URL: https://issues.jboss.org/browse/TEIIDDES-2971
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling
> Affects Versions: 10.0.2
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 10.0.2
>
>
> When a view is being materialized for JDG, the following keys need to be created:
> - as part of the cacheTypeMap property, the 3rd parameter primary key column: (cacheName:ClassName:primarykeycolumn)
> a primary key should be made containing that column on both of the newly created tables.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2970) Set default MatView Extension Properties for JDG materialization
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2970?page=com.atlassian.jira.plu... ]
Van Halbert updated TEIIDDES-2970:
----------------------------------
Description:
When a view is being materialized for JDG, set the following extension properties:
<vhalbert> "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'execute {jdgsourcemodelname}.native(''swap cache names'');'
<vhalbert> "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'execute {jdgsourcemodelname}.native(''truncate cache'');',
teiid_rel:MATERIALIZED_STAGE_TABLE" '{jdgsourcemodelname}.{stagingTable}')
where {jdgsourcemodelname} as the new JDG Source Model that is created.
was:
When a view is being materialized for JDG, set the following extension properties:
<vhalbert> "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'execute {jdgsourcemodelname}.native(''swap cache names'');'
<vhalbert> "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'execute {jdgsourcemodelname}.native(''truncate cache'');',
where {jdgsourcemodelname} as the new JDG Source Model that is created.
> Set default MatView Extension Properties for JDG materialization
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2970
> URL: https://issues.jboss.org/browse/TEIIDDES-2970
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling
> Affects Versions: 10.0.2
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 10.0.2
>
>
> When a view is being materialized for JDG, set the following extension properties:
> <vhalbert> "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'execute {jdgsourcemodelname}.native(''swap cache names'');'
> <vhalbert> "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'execute {jdgsourcemodelname}.native(''truncate cache'');',
> teiid_rel:MATERIALIZED_STAGE_TABLE" '{jdgsourcemodelname}.{stagingTable}')
> where {jdgsourcemodelname} as the new JDG Source Model that is created.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years, 11 months