[JBoss JIRA] (JBDS-1985) Synchronizing a VDB takes too long in 7.4.2
by Barry LaFond (Commented) (JIRA)
[ https://issues.jboss.org/browse/JBDS-1985?page=com.atlassian.jira.plugin.... ]
Barry LaFond commented on JBDS-1985:
------------------------------------
I renamed 7.4.2 branch this morning to 7.4.x (ooops forgot to update Hudson job
> Synchronizing a VDB takes too long in 7.4.2
> -------------------------------------------
>
> Key: JBDS-1985
> URL: https://issues.jboss.org/browse/JBDS-1985
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Support Patch
> Security Level: Public(Everyone can see)
> Components: teiid
> Affects Versions: 4.1.1.GA
> Reporter: Johnathon Lee
> Assignee: Barry LaFond
> Fix For: 4.1.1.GA
>
> Attachments: JBDS1985.upversion.patch.txt, org.teiid.designer.core.patch, org.teiid.designer.dqp.patch, org.teiid.designer.vdb.patch, org.teiid.designer.vdb.test.patch, org.teiid.designer.vdb.ui.patch, TEIIDDES-1200-7.4.2-Patch-A.zip, TEIIDDES_1200.zip, UdfManager.java.patch, UdfUiPlugin.java.patch, VdbUtil.java.patch
>
>
> Synchronizing a big VDB in version 7.4.2 (JBDS 4.1.1) takes 30 minutes versus 2 minutes in 7.1.1 (JBDS 4.1.0)
> Investigating/debug noted 2 areas.
> 1) New UdfManager is not caching a FunctionLibrary and each SQL validation is creating a new instance. (needs a fix)
> 2) Synchronizing a VDB is hammering the ChecksumUtil.computeChecksum() during the VDB's resource build processing
> 3) PreviewManager is using a new Vdb() object to determine if "preview = true" and version #. However, it's heavy weight and currently the Vdb() is registering for events, but is not being Unregistered.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (JBDS-1985) Synchronizing a VDB takes too long in 7.4.2
by Nick Boldt (Commented) (JIRA)
[ https://issues.jboss.org/browse/JBDS-1985?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-1985:
----------------------------------
New build finished last night.
https://hudson.qa.jboss.com/hudson/view/DevStudio_Stable_Branch/job/jboss...
http://download.jboss.org/jbosstools/builds/staging/jbosstools-teiid-desi...
http://download.jboss.org/jbosstools/builds/staging/jbosstools-teiid-desi...
... but I don't see the plugin/features being versioned 7.4.3 as per my patch yet. Were you going to apply that, or should I?
> Synchronizing a VDB takes too long in 7.4.2
> -------------------------------------------
>
> Key: JBDS-1985
> URL: https://issues.jboss.org/browse/JBDS-1985
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Support Patch
> Security Level: Public(Everyone can see)
> Components: teiid
> Affects Versions: 4.1.1.GA
> Reporter: Johnathon Lee
> Assignee: Barry LaFond
> Fix For: 4.1.1.GA
>
> Attachments: JBDS1985.upversion.patch.txt, org.teiid.designer.core.patch, org.teiid.designer.dqp.patch, org.teiid.designer.vdb.patch, org.teiid.designer.vdb.test.patch, org.teiid.designer.vdb.ui.patch, TEIIDDES-1200-7.4.2-Patch-A.zip, TEIIDDES_1200.zip, UdfManager.java.patch, UdfUiPlugin.java.patch, VdbUtil.java.patch
>
>
> Synchronizing a big VDB in version 7.4.2 (JBDS 4.1.1) takes 30 minutes versus 2 minutes in 7.1.1 (JBDS 4.1.0)
> Investigating/debug noted 2 areas.
> 1) New UdfManager is not caching a FunctionLibrary and each SQL validation is creating a new instance. (needs a fix)
> 2) Synchronizing a VDB is hammering the ChecksumUtil.computeChecksum() during the VDB's resource build processing
> 3) PreviewManager is using a new Vdb() object to determine if "preview = true" and version #. However, it's heavy weight and currently the Vdb() is registering for events, but is not being Unregistered.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBDS-1718) One installer for all supported platforms
by Denis Golovin (JIRA)
One installer for all supported platforms
-----------------------------------------
Key: JBDS-1718
URL: https://issues.jboss.org/browse/JBDS-1718
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: installer
Affects Versions: 5.0.0.Beta1
Reporter: Denis Golovin
Assignee: Denis Golovin
Fix For: 5.0.0.Beta1
Installer should utilize p2director and JBDS p2 repository created bt product build. That let us to have one installer for all platforms instead of five.
Size of installer is going to be more because of multi-platform bits inside p2repo and p2Director application included.
Installer based on IzPack has to extract p2repo first and then materialize JBDS using p2 director application.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (JBDS-1985) Synchronizing a VDB takes too long in 7.4.2
by Nick Boldt (Updated) (JIRA)
[ https://issues.jboss.org/browse/JBDS-1985?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-1985:
-----------------------------
Attachment: JBDS1985.upversion.patch.txt
Patch to fix plugin and containing feature versions -- everything affected by this issue should be at 7.4.3, not 7.4.2.
Also begs the question if the branch name (http://anonsvn.jboss.org/repos/tdesigner/branches/7.4.2) should be changed to reflect new version too.
> Synchronizing a VDB takes too long in 7.4.2
> -------------------------------------------
>
> Key: JBDS-1985
> URL: https://issues.jboss.org/browse/JBDS-1985
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Support Patch
> Security Level: Public(Everyone can see)
> Components: teiid
> Affects Versions: 4.1.1.GA
> Reporter: Johnathon Lee
> Assignee: Barry LaFond
> Fix For: 4.1.1.GA
>
> Attachments: JBDS1985.upversion.patch.txt, org.teiid.designer.core.patch, org.teiid.designer.dqp.patch, org.teiid.designer.vdb.patch, org.teiid.designer.vdb.test.patch, org.teiid.designer.vdb.ui.patch, TEIIDDES-1200-7.4.2-Patch-A.zip, TEIIDDES_1200.zip, UdfManager.java.patch, UdfUiPlugin.java.patch, VdbUtil.java.patch
>
>
> Synchronizing a big VDB in version 7.4.2 (JBDS 4.1.1) takes 30 minutes versus 2 minutes in 7.1.1 (JBDS 4.1.0)
> Investigating/debug noted 2 areas.
> 1) New UdfManager is not caching a FunctionLibrary and each SQL validation is creating a new instance. (needs a fix)
> 2) Synchronizing a VDB is hammering the ChecksumUtil.computeChecksum() during the VDB's resource build processing
> 3) PreviewManager is using a new Vdb() object to determine if "preview = true" and version #. However, it's heavy weight and currently the Vdb() is registering for events, but is not being Unregistered.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (JBIDE-10102) Application not added to available application list in OpenShift Tooling
by Martin Malina (Created) (JIRA)
Application not added to available application list in OpenShift Tooling
------------------------------------------------------------------------
Key: JBIDE-10102
URL: https://issues.jboss.org/browse/JBIDE-10102
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.M4
Environment: jbdevstudio-product-eap-macosx-cocoa-5.0.0.v201110271830R-H42-M4.jar
Mac OS X Lion
Reporter: Martin Malina
Assignee: Andre Dietisheim
Fix For: 3.3.0.Beta1
When you add a new app for the first time when creating an open shift project in JBoss Tools, the app you've just added is not added to the list of apps. If you try to add it again with the same time it says it's already there. Going back to the previous page and the forth again helps.
adietisheim: "the prob is an internal caching prob in my code" ;)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months