July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22658) Infinite or very long hang in CDI builder with Payara embedded maven dep

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22658?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22658: ----------------------------------- Fix Version/s: 4.4.1.AM1 (was: 4.4.x) > Infinite or very long hang in CDI builder with Payara embedded maven dep > ------------------------------------------------------------------------ > > Key: JBIDE-22658 > URL: https://issues.jboss.org/browse/JBIDE-22658 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Reporter: arjan tijms > Assignee: Viacheslav Kabanovich > Fix For: 4.4.1.AM1 > > > In the latest JBoss Tools for Eclipse Mars .2 (would be great if it was easy to see the main version easily, but I guess it's 4.3.1), the CDI builder either infinitely hangs or takes an enormous amount of time (an hour at least on a core M laptop) when payara embedded is present as (test) dependency in a maven project. > During this hang I took a stack trace, which looks as follows: > {noformat} > "Worker-20" #96 prio=5 os_prio=31 tid=0x0000000101512000 nid=0x14803 runnable [0x0000700003fde000] > java.lang.Thread.State: RUNNABLE > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.<init>(ZipFile.java:219) > at java.util.zip.ZipFile.<init>(ZipFile.java:149) > at java.util.zip.ZipFile.<init>(ZipFile.java:163) > at org.eclipse.jdt.internal.core.JavaModelManager.getZipFile(JavaModelManager.java:2678) > at org.eclipse.jdt.internal.core.JavaModelManager.getZipFile(JavaModelManager.java:2644) > at org.eclipse.jdt.internal.core.JarPackageFragmentRoot.getJar(JarPackageFragmentRoot.java:156) > at org.eclipse.jdt.internal.core.ClassFile.getJarBinaryTypeInfo(ClassFile.java:355) > at org.eclipse.jdt.internal.core.ClassFile.getBinaryTypeInfo(ClassFile.java:290) > at org.eclipse.jdt.internal.core.ClassFile.getBinaryTypeInfo(ClassFile.java:284) > at org.eclipse.jdt.internal.core.ClassFile.buildStructure(ClassFile.java:93) > at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:259) > at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107) > at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579) > at org.eclipse.jdt.internal.core.BinaryType.getElementInfo(BinaryType.java:287) > at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302) > at org.eclipse.jdt.internal.core.JavaElement.exists(JavaElement.java:220) > at org.jboss.tools.cdi.internal.core.scanner.ImplementationCollector.process(ImplementationCollector.java:41) > at org.jboss.tools.cdi.internal.core.scanner.ImplementationCollector.<init>(ImplementationCollector.java:32) > at org.jboss.tools.cdi.internal.core.impl.CDIProject.rebuildBeans(CDIProject.java:1309) > at org.jboss.tools.cdi.internal.core.impl.CDIProject.update(CDIProject.java:1216) > - locked <0x000000078ecd93d8> (a org.jboss.tools.cdi.internal.core.impl.CDICache) > at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.applyWorkingCopy(DefinitionContext.java:442) > at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:267) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > I debugged Eclipse with a second Eclipse, and it appeared that the code is repeatedly opening {{.m2/repository/fish/payara/extras/payara-embedded-all/4.1.1.162/payara-embedded-all-4.1.1.162.jar}} from {{CDIProject#rebuildBeans}}. > The specific line of code is: > {code:java} > ImplementationCollector ic = new ImplementationCollector(typeDefinitions); > {code} > The number of type definitions it seems to go through in {{ImplementationCollector#process}} is *33009* and the loop looks to be making progress, so it's more likely just incredibly slow and not an infinite hang. > The dependency in pom.xml looks as follows: > {code:xml} > <dependency> > <groupId>fish.payara.extras</groupId> > <artifactId>payara-embedded-all</artifactId> > <version>4.1.1.162</version> > <scope>test</scope> > </dependency> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2044: ----------------------------- Target Release: (was: ) > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Labels: discuss > Fix For: 10.0.1.AM2 > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3946) Detected components with invalid version count towards the "components that meet the requirements"

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3946?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3946: ----------------------------- Target Release: (was: ) > Detected components with invalid version count towards the "components that meet the requirements" > -------------------------------------------------------------------------------------------------- > > Key: JBDS-3946 > URL: https://issues.jboss.org/browse/JBDS-3946 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.0.1.AM2 > > > On confirmation page there is an info message that says how many components were detected that meet the requirements. Currently even components with invalid versions count towards the total even though they really don't meet the requirements. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3946) Detected components with invalid version count towards the "components that meet the requirements"

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3946?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3946: -------------------------------- > Detected components with invalid version count towards the "components that meet the requirements" > -------------------------------------------------------------------------------------------------- > > Key: JBDS-3946 > URL: https://issues.jboss.org/browse/JBDS-3946 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.0.1.AM2 > > > On confirmation page there is an info message that says how many components were detected that meet the requirements. Currently even components with invalid versions count towards the total even though they really don't meet the requirements. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3948) Use CDK nightly builds metadata to include nightly CDK build into DevSuite Bundl Installer

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3948?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3948: ----------------------------- Target Release: (was: ) > Use CDK nightly builds metadata to include nightly CDK build into DevSuite Bundl Installer > ------------------------------------------------------------------------------------------ > > Key: JBDS-3948 > URL: https://issues.jboss.org/browse/JBDS-3948 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.0.1.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.0.1.AM2 > > > Nightly CDK builds have sha256 checksums and metadata.txt. DevSuite build should use that to check if new download for CDK resources is required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3914) Build zip distribution for Mac OS X and Linux

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3914?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3914: ----------------------------- Target Release: (was: ) > Build zip distribution for Mac OS X and Linux > --------------------------------------------- > > Key: JBDS-3914 > URL: https://issues.jboss.org/browse/JBDS-3914 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.0.1.AM2 > > Attachments: zip in exe fails.png > > > We need to check if self extracting 7zip understands zip format and instead of creating .7z archive use zip archve for bundled installer. that would let us release the same zip as Linux and Mac OS X distribution. The only change is creating readme.md in the archive root with link to installation guide (see trelo card for details). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3652) Installer - Replace use of JBDS installer with JBDS product archive - to save time

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3652?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3652: -------------------------------- Fix Version/s: 10.0.1.AM2 (was: 10.0.1.AM1) > Installer - Replace use of JBDS installer with JBDS product archive - to save time > ---------------------------------------------------------------------------------- > > Key: JBDS-3652 > URL: https://issues.jboss.org/browse/JBDS-3652 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Minor > Labels: havoc, performance > Fix For: 10.0.1.AM2 > > > The current installer runs for several minutes when it invokes the JBDS installer - can we replace this a JBDS product archive and some follow-on tasks (such as setting the JDK location)? Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3922) Internal error occurs during installation when symbol "?" is used in installation path

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3922?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3922: -------------------------------- Fix Version/s: 10.0.1.AM2 (was: 10.0.1.AM1) > Internal error occurs during installation when symbol "?" is used in installation path > -------------------------------------------------------------------------------------- > > Key: JBDS-3922 > URL: https://issues.jboss.org/browse/JBDS-3922 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.0.0.GA > Environment: Fedora 23, x64 > Reporter: Ondrej Dockal > Assignee: Denis Golovin > Fix For: 10.0.1.AM2 > > > When choosing an installation path during devstudio installation and the character of "?" is used, installation process ends up with an internal error message. I would expect that error message would more descriptive or adding such character into installation path while choosing the path would cause some kind of warning/error before installation process starts. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3956) Installer should let to update detected oracle vurtualbox and vagrant

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3956?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3956: ----------------------------- Target Release: (was: ) > Installer should let to update detected oracle vurtualbox and vagrant > --------------------------------------------------------------------- > > Key: JBDS-3956 > URL: https://issues.jboss.org/browse/JBDS-3956 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.1.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.0.1.AM2 > > > It should also work for OpenJDK installed from .msi file. Detection should read installation information from registry using vbs scripts (see https://msdn.microsoft.com/en-us/library/aa369767(v=vs.85).aspx for details). > Reading install information form registry would work better than detection based on environment variables. It would let rerun detection on installer windows activation and detect changes in configuration without restarting installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3956) Installer should let to update detected oracle vurtualbox and vagrant

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3956?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3956: -------------------------------- Fix Version/s: 10.0.1.AM2 > Installer should let to update detected oracle vurtualbox and vagrant > --------------------------------------------------------------------- > > Key: JBDS-3956 > URL: https://issues.jboss.org/browse/JBDS-3956 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.1.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.0.1.AM2 > > > It should also work for OpenJDK installed from .msi file. Detection should read installation information from registry using vbs scripts (see https://msdn.microsoft.com/en-us/library/aa369767(v=vs.85).aspx for details). > Reading install information form registry would work better than detection based on environment variables. It would let rerun detection on installer windows activation and detect changes in configuration without restarting installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2016