[JBoss JIRA] (TEIIDDES-3123) Deploy XML VDB takes a long time.
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3123?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-3123:
---------------------------------------
The native only required for when the translator is infinispan-hotrod. This doesn't need to be used otherwise.
I tried the latest Teiid Designer beta2 build and this doesn't appear to be occurring.
> Deploy XML VDB takes a long time.
> ---------------------------------
>
> Key: TEIIDDES-3123
> URL: https://issues.jboss.org/browse/TEIIDDES-3123
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 11.1
> Reporter: Matej Kralik
> Priority: Critical
> Attachments: SourceColumnsProject.zip, screenshot.png
>
>
> When I generate XML VDB from VDB, the designer adds "<metadata type="NATIVE"/>" property to XML VDB. It causes performance issue because deploy XML VDB takes a long time.
> The time between deploy VDB (added to the repository) and set VDB to active:
> With "metadata native" property: 3 minutes.
> Without "metadata native" property: <1 seconds.
> For this example, I use XML VDB (in the project from attachments) which connects to MS SQL Server database.
> When I use another connection with a lot of tables and schemas, it takes very long (more than 30minutes).
> I think that it is not necessary to add this property by default to all XML VDBs only if it is necessary for specific VDB. For users who want to use this property will be good to add a new checkbox to the 'options' tab in the 'Save as VDB XML file' wizard. (screenshot)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (TEIIDDES-3117) Dynamic VDB is not generated properly for UDF function
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3117?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-3117.
------------------------------------
Resolution: Won't Do
Designer VDB editor currently allows adding User Properties, so as a work-around, I added this one via the "Add New Property" button/dialog which provides the desired functionality for this use-case.
{code:xml}
<property name="lib" value="deployment.TestUDF.jar, deployment.otherUDF.jar"/>
{code}
> Dynamic VDB is not generated properly for UDF function
> ------------------------------------------------------
>
> Key: TEIIDDES-3117
> URL: https://issues.jboss.org/browse/TEIIDDES-3117
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1
> Environment: Fedora 26
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 11.1.1
>
>
> I have a project with UDF function. I mark jar as deployable and it is on the server. Static VDB works fine, but when I generate dynamic VDB and want it to deploy on the server, the server shows me an error:
> {code:java}
> 15:50:26,282 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "myUdfVdb-vdb.xml"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:184) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2064) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1987) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_121]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_121]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: TEIID50088 Failed to load module MyTestUdf-1.0-SNAPSHOT for UDF in VDB myUdfVdb.1:org.jboss.modules.ModuleNotFoundException: MyTestUdf-1.0-SNAPSHOT:main
> at org.teiid.jboss.VDBDependencyDeployer.deploy(VDBDependencyDeployer.java:85)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:177) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
> ... 5 more
> {code}
> According to EAP [documentation|https://access.redhat.com/documentation/en-US/JBoss_Enterpr...], a module is automatically created after jar file is deployed. Name of the module is *deployment.<runtime jar name>* however designer generated lib properties *only* with <jarFileName>.
> The name is wrong too because when designer deploying jar file, the runtime name is set with suffix (.jar f.e. runtime-name: "MyTestUdf-1.0-SNAPSHOT.jar")
> *Actual property*
> {code:java}
> <property name="lib" value="MyTestUdf-1.0-SNAPSHOT"/>
> {code}
> *Valid property*
> {code:java}
> <property name="lib" value="deployment.MyTestUdf-1.0-SNAPSHOT.jar"/>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (TEIIDDES-3117) Dynamic VDB is not generated properly for UDF function
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3117?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-3117:
----------------------------------------
[~blafond] I do not think Teiid looks at "<entry>" elements, if the "lib" directory is found in the VDB then contents of it are loaded into an implicit module, and that module is available for the UDF execution.
The alternative is, one can provide a "lib" property in vdb.xml, which needs to be a reference to a "module" name.
Given these two cases, UI needs to handle properly.
> Dynamic VDB is not generated properly for UDF function
> ------------------------------------------------------
>
> Key: TEIIDDES-3117
> URL: https://issues.jboss.org/browse/TEIIDDES-3117
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1
> Environment: Fedora 26
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 11.1.1
>
>
> I have a project with UDF function. I mark jar as deployable and it is on the server. Static VDB works fine, but when I generate dynamic VDB and want it to deploy on the server, the server shows me an error:
> {code:java}
> 15:50:26,282 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "myUdfVdb-vdb.xml"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:184) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2064) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1987) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_121]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_121]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: TEIID50088 Failed to load module MyTestUdf-1.0-SNAPSHOT for UDF in VDB myUdfVdb.1:org.jboss.modules.ModuleNotFoundException: MyTestUdf-1.0-SNAPSHOT:main
> at org.teiid.jboss.VDBDependencyDeployer.deploy(VDBDependencyDeployer.java:85)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:177) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
> ... 5 more
> {code}
> According to EAP [documentation|https://access.redhat.com/documentation/en-US/JBoss_Enterpr...], a module is automatically created after jar file is deployed. Name of the module is *deployment.<runtime jar name>* however designer generated lib properties *only* with <jarFileName>.
> The name is wrong too because when designer deploying jar file, the runtime name is set with suffix (.jar f.e. runtime-name: "MyTestUdf-1.0-SNAPSHOT.jar")
> *Actual property*
> {code:java}
> <property name="lib" value="MyTestUdf-1.0-SNAPSHOT"/>
> {code}
> *Valid property*
> {code:java}
> <property name="lib" value="deployment.MyTestUdf-1.0-SNAPSHOT.jar"/>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (TEIIDDES-3103) Execute VDB in the Guides doesn't work
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3103?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-3103:
----------------------------------------
[~mkralik] Can you set up a time where you can demo this issue to me? and verify your installed configuration/versions?
> Execute VDB in the Guides doesn't work
> --------------------------------------
>
> Key: TEIIDDES-3103
> URL: https://issues.jboss.org/browse/TEIIDDES-3103
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1
> Environment: Fedora 26
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 11.1.1
>
> Attachments: guides.mkv, screenshot.png
>
>
> Last step (execute VDB) in the first guide (Model JDBC Source) doesn't work. After click on the "Execute VDB" shows wizard for choosing VDB (screenshot1). After click OK, VDB is not deployed.
> I noticed that it doesn't work in the other guides as well.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (TEIIDDES-3117) Dynamic VDB is not generated properly for UDF function
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3117?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-3117:
----------------------------------------
[~rareddy] Currently our UDF's are added via simple <entry> in VDB
{code:xml}
<entry path="/lib/TestUDF.jar">
<property name="checksum" value="2064868142"/>
</entry>
{code}
So to clarify:
* if a VDB contains UDF jars, they are discovered from the <entry> elements (above) and modules are created through Teiid Runtime (i.e. no <property name="lib" ...... is needed)
* if UDF jars are already deployed as *modules* then there needs to be a reference to those jars in a separate property?
** <property name="lib" value="deployment.MyTestUdf-1.0-SNAPSHOT.jar"/>
> Dynamic VDB is not generated properly for UDF function
> ------------------------------------------------------
>
> Key: TEIIDDES-3117
> URL: https://issues.jboss.org/browse/TEIIDDES-3117
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1
> Environment: Fedora 26
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 11.1.1
>
>
> I have a project with UDF function. I mark jar as deployable and it is on the server. Static VDB works fine, but when I generate dynamic VDB and want it to deploy on the server, the server shows me an error:
> {code:java}
> 15:50:26,282 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "myUdfVdb-vdb.xml"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:184) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2064) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1987) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_121]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_121]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: TEIID50088 Failed to load module MyTestUdf-1.0-SNAPSHOT for UDF in VDB myUdfVdb.1:org.jboss.modules.ModuleNotFoundException: MyTestUdf-1.0-SNAPSHOT:main
> at org.teiid.jboss.VDBDependencyDeployer.deploy(VDBDependencyDeployer.java:85)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:177) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
> ... 5 more
> {code}
> According to EAP [documentation|https://access.redhat.com/documentation/en-US/JBoss_Enterpr...], a module is automatically created after jar file is deployed. Name of the module is *deployment.<runtime jar name>* however designer generated lib properties *only* with <jarFileName>.
> The name is wrong too because when designer deploying jar file, the runtime name is set with suffix (.jar f.e. runtime-name: "MyTestUdf-1.0-SNAPSHOT.jar")
> *Actual property*
> {code:java}
> <property name="lib" value="MyTestUdf-1.0-SNAPSHOT"/>
> {code}
> *Valid property*
> {code:java}
> <property name="lib" value="deployment.MyTestUdf-1.0-SNAPSHOT.jar"/>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (TEIIDDES-3117) Dynamic VDB is not generated properly for UDF function
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3117?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-3117:
----------------------------------------
[~blafond] When JAR is already deployed into the WildFly as is, i.e. no module is created then "deployment" prefix is needed. When you are including the JAR file inside the "lib" directory then you don't need any property at all.
So, as per Designer adding the "lib" property with "deployment" prefix, it should depend on UI says. If it a module and has post fix of ".jar" yes that should be added otherwise no.
> Dynamic VDB is not generated properly for UDF function
> ------------------------------------------------------
>
> Key: TEIIDDES-3117
> URL: https://issues.jboss.org/browse/TEIIDDES-3117
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1
> Environment: Fedora 26
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 11.1.1
>
>
> I have a project with UDF function. I mark jar as deployable and it is on the server. Static VDB works fine, but when I generate dynamic VDB and want it to deploy on the server, the server shows me an error:
> {code:java}
> 15:50:26,282 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "myUdfVdb-vdb.xml"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:184) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2064) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1987) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_121]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_121]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: TEIID50088 Failed to load module MyTestUdf-1.0-SNAPSHOT for UDF in VDB myUdfVdb.1:org.jboss.modules.ModuleNotFoundException: MyTestUdf-1.0-SNAPSHOT:main
> at org.teiid.jboss.VDBDependencyDeployer.deploy(VDBDependencyDeployer.java:85)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:177) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
> ... 5 more
> {code}
> According to EAP [documentation|https://access.redhat.com/documentation/en-US/JBoss_Enterpr...], a module is automatically created after jar file is deployed. Name of the module is *deployment.<runtime jar name>* however designer generated lib properties *only* with <jarFileName>.
> The name is wrong too because when designer deploying jar file, the runtime name is set with suffix (.jar f.e. runtime-name: "MyTestUdf-1.0-SNAPSHOT.jar")
> *Actual property*
> {code:java}
> <property name="lib" value="MyTestUdf-1.0-SNAPSHOT"/>
> {code}
> *Valid property*
> {code:java}
> <property name="lib" value="deployment.MyTestUdf-1.0-SNAPSHOT.jar"/>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (TEIIDDES-3123) Deploy XML VDB takes a long time.
by Matej Kralik (JIRA)
Matej Kralik created TEIIDDES-3123:
--------------------------------------
Summary: Deploy XML VDB takes a long time.
Key: TEIIDDES-3123
URL: https://issues.jboss.org/browse/TEIIDDES-3123
Project: Teiid Designer
Issue Type: Bug
Components: Dynamic VDBs
Affects Versions: 11.1
Reporter: Matej Kralik
Priority: Critical
Attachments: SourceColumnsProject.zip, screenshot.png
When I generate XML VDB from VDB, the designer adds "<metadata type="NATIVE"/>" property to XML VDB. It causes performance issue because deploy XML VDB takes a long time.
The time between deploy VDB (added to the repository) and set VDB to active:
With "metadata native" property: 3 minutes.
Without "metadata native" property: <1 seconds.
For this example, I use XML VDB (in the project from attachments) which connects to MS SQL Server database.
When I use another connection with a lot of tables and schemas, it takes very long (more than 30minutes).
I think that it is not necessary to add this property by default to all XML VDBs only if it is necessary for specific VDB. For users who want to use this property will be good to add a new checkbox to the 'options' tab in the 'Save as VDB XML file' wizard. (screenshot)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (TEIIDDES-3122) Designer is not able to generate XML VDB (dynamicVDB)
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3122?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-3122.
----------------------------------
Resolution: Duplicate Issue
I noticed that it is already reported -> TEIIDDES-3118
> Designer is not able to generate XML VDB (dynamicVDB)
> -----------------------------------------------------
>
> Key: TEIIDDES-3122
> URL: https://issues.jboss.org/browse/TEIIDDES-3122
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 11.1
> Reporter: Matej Kralik
> Priority: Blocker
> Attachments: PartSupplierProject.zip, screenshot.png
>
>
> When I click on (Generate XML VDB), the wizard doesn't contain any XML contents and an error is displayed in the background (screenshot).
> Problem Occurred windows contains this information:
> {code:java}
> An exception occurred while performing an operation
> * null
> * cvc-complex-type.4: Attribute 'translator-name' must appear on element 'source'.
> {code}
> In the error log:
> {code:java}
> javax.xml.bind.MarshalException
> - with linked exception:
> [org.xml.sax.SAXParseException; lineNumber: 0; columnNumber: 0; cvc-complex-type.4: Attribute 'translator-name' must appear on element 'source'.]
> at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:311)
> at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:236)
> at javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:130)
> at org.teiid.designer.vdb.dynamic.DynamicVdb.write(DynamicVdb.java:392)
> at org.teiid.designer.runtime.ui.wizards.vdbs.AbstractGenerateVdbManager.getDynamicVdbXml(AbstractGenerateVdbManager.java:332)
> at org.teiid.designer.runtime.ui.wizards.vdbs.GenerateDynamicVdbManager.getDynamicVdbXml(GenerateDynamicVdbManager.java:201)
> at org.teiid.designer.runtime.ui.wizards.vdbs.GenerateDynamicVdbDialog.refreshXml(GenerateDynamicVdbDialog.java:326)
> at org.teiid.designer.runtime.ui.wizards.vdbs.GenerateDynamicVdbDialog.resetDynamicVdb(GenerateDynamicVdbDialog.java:317)
> at org.teiid.designer.runtime.ui.wizards.vdbs.GenerateDynamicVdbDialog.createContents(GenerateDynamicVdbDialog.java:672)
> at org.eclipse.jface.window.Window.create(Window.java:426)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.eclipse.jface.window.Window.open(Window.java:783)
> at org.teiid.designer.runtime.ui.actions.GenerateDynamicVdbAction.run(GenerateDynamicVdbAction.java:67)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5268)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4522)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4107)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> Caused by: org.xml.sax.SAXParseException; lineNumber: 0; columnNumber: 0; cvc-complex-type.4: Attribute 'translator-name' must appear on element 'source'.
> at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
> at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:134)
> at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:396)
> at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327)
> at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:284)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:452)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3230)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.addDefaultAttributes(XMLSchemaValidator.java:2936)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:2054)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:740)
> at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorHandlerImpl.startElement(ValidatorHandlerImpl.java:570)
> at org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:551)
> at com.sun.xml.internal.bind.v2.runtime.output.SAXOutput.endStartTag(SAXOutput.java:113)
> at com.sun.xml.internal.bind.v2.runtime.output.ForkXmlOutput.endStartTag(ForkXmlOutput.java:91)
> at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.endAttributes(XMLSerializer.java:292)
> at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:680)
> at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementNodeProperty.serializeItem(ArrayElementNodeProperty.java:54)
> at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementProperty.serializeListBody(ArrayElementProperty.java:157)
> at com.sun.xml.internal.bind.v2.runtime.property.ArrayERProperty.serializeBody(ArrayERProperty.java:144)
> at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:345)
> at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:681)
> at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementNodeProperty.serializeItem(ArrayElementNodeProperty.java:54)
> at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementProperty.serializeListBody(ArrayElementProperty.java:157)
> at com.sun.xml.internal.bind.v2.runtime.property.ArrayERProperty.serializeBody(ArrayERProperty.java:144)
> at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:345)
> at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsSoleContent(XMLSerializer.java:578)
> at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.serializeRoot(ClassBeanInfoImpl.java:326)
> at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:479)
> at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:308)
> ... 42 more
> {code}
> I noticed that when VDB contains only source model, the designer is able to generate XML VDB. (In the project from attachments: Delete viewPartSupplier from VDB and try to generate XML again)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (TEIIDDES-3122) Designer is not able to generate XML VDB (dynamicVDB)
by Matej Kralik (JIRA)
Matej Kralik created TEIIDDES-3122:
--------------------------------------
Summary: Designer is not able to generate XML VDB (dynamicVDB)
Key: TEIIDDES-3122
URL: https://issues.jboss.org/browse/TEIIDDES-3122
Project: Teiid Designer
Issue Type: Bug
Components: Dynamic VDBs
Affects Versions: 11.1
Reporter: Matej Kralik
Priority: Blocker
Attachments: PartSupplierProject.zip, screenshot.png
When I click on (Generate XML VDB), the wizard doesn't contain any XML contents and an error is displayed in the background (screenshot).
Problem Occurred windows contains this information:
{code:java}
An exception occurred while performing an operation
* null
* cvc-complex-type.4: Attribute 'translator-name' must appear on element 'source'.
{code}
In the error log:
{code:java}
javax.xml.bind.MarshalException
- with linked exception:
[org.xml.sax.SAXParseException; lineNumber: 0; columnNumber: 0; cvc-complex-type.4: Attribute 'translator-name' must appear on element 'source'.]
at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:311)
at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:236)
at javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:130)
at org.teiid.designer.vdb.dynamic.DynamicVdb.write(DynamicVdb.java:392)
at org.teiid.designer.runtime.ui.wizards.vdbs.AbstractGenerateVdbManager.getDynamicVdbXml(AbstractGenerateVdbManager.java:332)
at org.teiid.designer.runtime.ui.wizards.vdbs.GenerateDynamicVdbManager.getDynamicVdbXml(GenerateDynamicVdbManager.java:201)
at org.teiid.designer.runtime.ui.wizards.vdbs.GenerateDynamicVdbDialog.refreshXml(GenerateDynamicVdbDialog.java:326)
at org.teiid.designer.runtime.ui.wizards.vdbs.GenerateDynamicVdbDialog.resetDynamicVdb(GenerateDynamicVdbDialog.java:317)
at org.teiid.designer.runtime.ui.wizards.vdbs.GenerateDynamicVdbDialog.createContents(GenerateDynamicVdbDialog.java:672)
at org.eclipse.jface.window.Window.create(Window.java:426)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
at org.eclipse.jface.window.Window.open(Window.java:783)
at org.teiid.designer.runtime.ui.actions.GenerateDynamicVdbAction.run(GenerateDynamicVdbAction.java:67)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5268)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4522)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4107)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
Caused by: org.xml.sax.SAXParseException; lineNumber: 0; columnNumber: 0; cvc-complex-type.4: Attribute 'translator-name' must appear on element 'source'.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:134)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:396)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:284)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:452)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3230)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.addDefaultAttributes(XMLSchemaValidator.java:2936)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:2054)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:740)
at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorHandlerImpl.startElement(ValidatorHandlerImpl.java:570)
at org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:551)
at com.sun.xml.internal.bind.v2.runtime.output.SAXOutput.endStartTag(SAXOutput.java:113)
at com.sun.xml.internal.bind.v2.runtime.output.ForkXmlOutput.endStartTag(ForkXmlOutput.java:91)
at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.endAttributes(XMLSerializer.java:292)
at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:680)
at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementNodeProperty.serializeItem(ArrayElementNodeProperty.java:54)
at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementProperty.serializeListBody(ArrayElementProperty.java:157)
at com.sun.xml.internal.bind.v2.runtime.property.ArrayERProperty.serializeBody(ArrayERProperty.java:144)
at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:345)
at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:681)
at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementNodeProperty.serializeItem(ArrayElementNodeProperty.java:54)
at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementProperty.serializeListBody(ArrayElementProperty.java:157)
at com.sun.xml.internal.bind.v2.runtime.property.ArrayERProperty.serializeBody(ArrayERProperty.java:144)
at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:345)
at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsSoleContent(XMLSerializer.java:578)
at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.serializeRoot(ClassBeanInfoImpl.java:326)
at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:479)
at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:308)
... 42 more
{code}
I noticed that when VDB contains only source model, the designer is able to generate XML VDB. (In the project from attachments: Delete viewPartSupplier from VDB and try to generate XML again)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (TEIIDDES-3117) Dynamic VDB is not generated properly for UDF function
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3117?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-3117:
----------------------------------------
[~rareddy] Can you verify that the "lib" property for UDF jars in the VDB manifest require the *deployment.* prefix? thx
> Dynamic VDB is not generated properly for UDF function
> ------------------------------------------------------
>
> Key: TEIIDDES-3117
> URL: https://issues.jboss.org/browse/TEIIDDES-3117
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1
> Environment: Fedora 26
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 11.1.1
>
>
> I have a project with UDF function. I mark jar as deployable and it is on the server. Static VDB works fine, but when I generate dynamic VDB and want it to deploy on the server, the server shows me an error:
> {code:java}
> 15:50:26,282 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."myUdfVdb-vdb.xml".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "myUdfVdb-vdb.xml"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:184) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2064) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1987) [jboss-msc-1.1.7.SP1-redhat-1.jar:1.1.7.SP1-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_121]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_121]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: TEIID50088 Failed to load module MyTestUdf-1.0-SNAPSHOT for UDF in VDB myUdfVdb.1:org.jboss.modules.ModuleNotFoundException: MyTestUdf-1.0-SNAPSHOT:main
> at org.teiid.jboss.VDBDependencyDeployer.deploy(VDBDependencyDeployer.java:85)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:177) [jboss-as-server-7.5.16.Final-redhat-1.jar:7.5.16.Final-redhat-1]
> ... 5 more
> {code}
> According to EAP [documentation|https://access.redhat.com/documentation/en-US/JBoss_Enterpr...], a module is automatically created after jar file is deployed. Name of the module is *deployment.<runtime jar name>* however designer generated lib properties *only* with <jarFileName>.
> The name is wrong too because when designer deploying jar file, the runtime name is set with suffix (.jar f.e. runtime-name: "MyTestUdf-1.0-SNAPSHOT.jar")
> *Actual property*
> {code:java}
> <property name="lib" value="MyTestUdf-1.0-SNAPSHOT"/>
> {code}
> *Valid property*
> {code:java}
> <property name="lib" value="deployment.MyTestUdf-1.0-SNAPSHOT.jar"/>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months