[JBoss JIRA] (JBIDE-16308) Cannot start JBT 4.2.0.Alpha1 on Fedora 19
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16308?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-16308:
----------------------------------------
GC overhead may be another error, but the core dump is definitely a dup of JBIDE-16820.
> Cannot start JBT 4.2.0.Alpha1 on Fedora 19
> ------------------------------------------
>
> Key: JBIDE-16308
> URL: https://issues.jboss.org/browse/JBIDE-16308
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Environment: JBT 4.2.Alpha1, L64, Fedora 19, 64-bit, Open JDK 1.7
> Reporter: Jiri Peterka
> Priority: Blocker
> Fix For: 4.2.0.Alpha1
>
> Attachments: hs_err_pid17371.log, hs_err_pid18745.log
>
>
> Installing JBT on Eclipse -4.4.M4- 4.4.M3 JEE package (linux_64), after JBT installation update site and restart I have:
> {code}
> !ENTRY org.eclipse.osgi 4 0 2013-12-16 15:35:03.535
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> at java.util.ArrayList.iterator(ArrayList.java:814)
> at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:962)
> at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:454)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:412)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:402)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1510)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1481)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1424)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> {code}
> Even if I raise a memory for JVM, Eclipse doesn't start but not error message is written
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16308) Cannot start JBT 4.2.0.Alpha1 on Fedora 19
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16308?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-16308:
----------------------------------------
> Could it be related to http://www.youtube.com/watch?v=IAZenG98E38 ?
Damn, wrong link!
My link was JBIDE-16820.
> Cannot start JBT 4.2.0.Alpha1 on Fedora 19
> ------------------------------------------
>
> Key: JBIDE-16308
> URL: https://issues.jboss.org/browse/JBIDE-16308
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Environment: JBT 4.2.Alpha1, L64, Fedora 19, 64-bit, Open JDK 1.7
> Reporter: Jiri Peterka
> Priority: Blocker
> Fix For: 4.2.0.Alpha1
>
> Attachments: hs_err_pid17371.log, hs_err_pid18745.log
>
>
> Installing JBT on Eclipse -4.4.M4- 4.4.M3 JEE package (linux_64), after JBT installation update site and restart I have:
> {code}
> !ENTRY org.eclipse.osgi 4 0 2013-12-16 15:35:03.535
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> at java.util.ArrayList.iterator(ArrayList.java:814)
> at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:962)
> at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:454)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:412)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:402)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1510)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1481)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1424)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> {code}
> Even if I raise a memory for JVM, Eclipse doesn't start but not error message is written
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16308) Cannot start JBT 4.2.0.Alpha1 on Fedora 19
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16308?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-16308:
------------------------------------
Installing from http://download.jboss.org/jbosstools/updates/nightly/core/4.2.luna/ into Eclipse Standard 4.4.M3 and selecting only *org.jboss.tools.community.central.feature* results in the same crash...
{code}
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fb157572255, pid=21996, tid=140400201221888
#
# JRE version: 7.0_17-b02
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libxul.so+0xc81255] JSD_DebuggerOnForUser+0x978a2
{code}
Here's the debug output showing the eclipse.ini / commandline settings:
{code}
-debug
-vm /opt/sun-java2-7.0/bin/java
-vmargs
-Dosgi.requiredJavaVersion=1.6
-XX:MaxPermSize=256m
-Xms40m
-Xmx512m
{code}
but based on a smaller set of installed features:
{code}
$➔ find . -maxdepth 1 -name "*jboss*" -o -name "*hibernate*" | sort
./org.hibernate.eclipse.feature_3.8.0.Alpha1-v20131207-1621-B2
./org.jboss.ide.eclipse.archives.feature_3.5.0.Alpha1-v20131209-0714-B4
./org.jboss.ide.eclipse.as.archives.integration.feature_2.5.0.Alpha1-v20131209-0714-B4
./org.jboss.ide.eclipse.as.feature_2.5.0.Alpha1-v20131209-0714-B4
./org.jboss.ide.eclipse.as.jmx.integration.feature_2.5.0.Alpha1-v20131209-0714-B4
./org.jboss.ide.eclipse.as.serverAdapter.wtp.feature_2.5.0.Alpha1-v20131209-0714-B4
./org.jboss.ide.eclipse.as.server.rse.integration.feature_2.5.0.Alpha1-v20131209-0714-B4
./org.jboss.tools.archives.scanner.feature_3.5.0.Alpha1-v20131209-0714-B4
./org.jboss.tools.central.feature_1.3.0.Alpha1-v20131209-0943-B6
./org.jboss.tools.common.feature_3.6.0.Alpha1-v20131206-2157-B1
./org.jboss.tools.community.central.feature_1.3.0.Alpha1-v20131209-0943-B6
./org.jboss.tools.community.project.examples.feature_1.6.0.Alpha1-v20131209-0943-B6
./org.jboss.tools.jmx.feature_1.5.0.Alpha1-v20131209-0714-B4
./org.jboss.tools.jsf.feature_3.6.0.Alpha1-v20131209-0801-B5
./org.jboss.tools.jst.feature_3.6.0.Alpha1-v20131207-1423-B2
./org.jboss.tools.maven.project.examples.feature_1.6.0.Alpha1-v20131209-0943-B6
./org.jboss.tools.project.examples.feature_1.6.0.Alpha1-v20131209-0943-B6
./org.jboss.tools.runtime.core.feature_3.0.0.Alpha1-v20131206-2157-B1
./org.jboss.tools.runtime.seam.detector.feature_3.5.0.Alpha1-v20131209-0801-B5
./org.jboss.tools.seam.feature_3.5.0.Alpha1-v20131209-0801-B5
./org.jboss.tools.stacks.core.feature_1.1.0.Alpha1-v20131206-2157-B1
./org.jboss.tools.vpe.feature_3.5.100.Alpha1-v20131210-2123-B4
{code}
> Cannot start JBT 4.2.0.Alpha1 on Fedora 19
> ------------------------------------------
>
> Key: JBIDE-16308
> URL: https://issues.jboss.org/browse/JBIDE-16308
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Environment: JBT 4.2.Alpha1, L64, Fedora 19, 64-bit, Open JDK 1.7
> Reporter: Jiri Peterka
> Priority: Blocker
> Fix For: 4.2.0.Alpha1
>
> Attachments: hs_err_pid17371.log, hs_err_pid18745.log
>
>
> Installing JBT on Eclipse -4.4.M4- 4.4.M3 JEE package (linux_64), after JBT installation update site and restart I have:
> {code}
> !ENTRY org.eclipse.osgi 4 0 2013-12-16 15:35:03.535
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> at java.util.ArrayList.iterator(ArrayList.java:814)
> at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:962)
> at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:454)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:412)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:402)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1510)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1481)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1424)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> {code}
> Even if I raise a memory for JVM, Eclipse doesn't start but not error message is written
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16308) Cannot start JBT 4.2.0.Alpha1 on Fedora 19
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16308?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-16308:
------------------------------------
Have tried these options in eclipse.ini, but with no better success. I can get Eclipse to open & pop the usage tracker dialog before crashing, but that's not much better.
{code}
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20131025-1931
-product
org.eclipse.epp.package.standard.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
512m
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.7
-XX:MaxPermSize=2048m
-Xms512m
-Xmx2048m
{code}
> Cannot start JBT 4.2.0.Alpha1 on Fedora 19
> ------------------------------------------
>
> Key: JBIDE-16308
> URL: https://issues.jboss.org/browse/JBIDE-16308
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Environment: JBT 4.2.Alpha1, L64, Fedora 19, 64-bit, Open JDK 1.7
> Reporter: Jiri Peterka
> Priority: Blocker
> Fix For: 4.2.0.Alpha1
>
> Attachments: hs_err_pid17371.log, hs_err_pid18745.log
>
>
> Installing JBT on Eclipse -4.4.M4- 4.4.M3 JEE package (linux_64), after JBT installation update site and restart I have:
> {code}
> !ENTRY org.eclipse.osgi 4 0 2013-12-16 15:35:03.535
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> at java.util.ArrayList.iterator(ArrayList.java:814)
> at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:962)
> at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:454)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:412)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:402)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1510)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1481)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1424)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> {code}
> Even if I raise a memory for JVM, Eclipse doesn't start but not error message is written
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16272) Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16272?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-16272:
----------------------------------------
I don't see <a4j:calendar> at all. Ctrl+Space or autocompletion. The same result for me.
It looks like that <a4j:calendar> provided by some third party plug-ins. Do you have anything else installed or just Eclipse + JBoss Tools + dependencies?
To make sure it's not a JBT please try the following:
1. Ctrl+Space for <a4j:
2. When the list of proposals are shown press Ctrl+Space a few times until you see "Press Ctrl+Space to show JBoss JSF Tag Proposals":
!jbthtml.png!
3. Then press Ctrl+Space one more time. You will see the list of JSF tags provided by JBoss Tools only:
!jbtca.png!
> Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16272
> URL: https://issues.jboss.org/browse/JBIDE-16272
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.1.0.1.Final
> Reporter: Juraj Húska
> Assignee: Alexey Kazakov
> Fix For: 4.2.x
>
> Attachments: a4jTagLibCtrlClick.png, jbtca.png, jbthtml.png, myAutocompletion1.png, myAutocompletion2.png, myAutocompletion3.png, scr.png, scr2.png, scr3.png, taglib2.png, tagLibraries1.png
>
>
> When I create new JSF project, where I add RichFaces libraries needed to create _RichFaces 4.5_ (a special version which should be some kind of bridge between RichFaces 4 and 5) application:
> * richfaces-5.0.0.Alpha2.jar
> * richfaces-components-a4j-4.5.0.Alpha1.jar
> * richfaces-components-rich-4.5.0.Alpha1.jar
> Then if you have all supported namespaces included, auto completion triggered e.g. on {{<a4j:}} will provides also non existing components, like {{<a4j:calendar}} (it should be {{<rich:calendar}} )
> Please see steps to reproduce.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16272) Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16272?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-16272:
-----------------------------------
Attachment: jbtca.png
jbthtml.png
> Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16272
> URL: https://issues.jboss.org/browse/JBIDE-16272
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.1.0.1.Final
> Reporter: Juraj Húska
> Assignee: Alexey Kazakov
> Fix For: 4.2.x
>
> Attachments: a4jTagLibCtrlClick.png, jbtca.png, jbthtml.png, myAutocompletion1.png, myAutocompletion2.png, myAutocompletion3.png, scr.png, scr2.png, scr3.png, taglib2.png, tagLibraries1.png
>
>
> When I create new JSF project, where I add RichFaces libraries needed to create _RichFaces 4.5_ (a special version which should be some kind of bridge between RichFaces 4 and 5) application:
> * richfaces-5.0.0.Alpha2.jar
> * richfaces-components-a4j-4.5.0.Alpha1.jar
> * richfaces-components-rich-4.5.0.Alpha1.jar
> Then if you have all supported namespaces included, auto completion triggered e.g. on {{<a4j:}} will provides also non existing components, like {{<a4j:calendar}} (it should be {{<rich:calendar}} )
> Please see steps to reproduce.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-16286:
----------------------------------------
[~adietish] a few more questions for you:
1. What is your environment?
2. VM arguments?
3. Do you have anything else installed or this is only Luna + TP 4.40.x?
> CDI builder (not import, workspace rebuild) is very slow in wildfly
> -------------------------------------------------------------------
>
> Key: JBIDE-16286
> URL: https://issues.jboss.org/browse/JBIDE-16286
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.1.1.Final
> Reporter: Andre Dietisheim
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.1.2.Final, 4.2.0.Alpha2
>
> Attachments: cdi-builder.ogv, cleanBuild.png, maven-preferences-hide-children.png, thread-dump-7_05.txt, thread-dump-7_19.txt, updatingPom.png, VisualVM 1.3.2 _083.png
>
>
> When working in a wildfly workspace with all wildfly projects imported and CDI builder enabled, workspace rebuilds (that you trigger by changing poms and then do maven update project) are a lot slower than without it. Re-building the whole workspace can easily take up to 20 minutes for me.
> Hard to give more general purpose details, I did a quick screencast to give an impression how slow things are for me.
> [^cdi-builder.ogv]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16308) Cannot start JBT 4.2.0.Alpha1 on Fedora 19
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16308?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-16308:
-------------------------------
Attachment: hs_err_pid18745.log
Error report from warn restart: [^hs_err_pid17371.log]
Error report from cold restart: [^hs_err_pid18745.log]
> Cannot start JBT 4.2.0.Alpha1 on Fedora 19
> ------------------------------------------
>
> Key: JBIDE-16308
> URL: https://issues.jboss.org/browse/JBIDE-16308
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Environment: JBT 4.2.Alpha1, L64, Fedora 19, 64-bit, Open JDK 1.7
> Reporter: Jiri Peterka
> Priority: Blocker
> Fix For: 4.2.0.Alpha1
>
> Attachments: hs_err_pid17371.log, hs_err_pid18745.log
>
>
> Installing JBT on Eclipse -4.4.M4- 4.4.M3 JEE package (linux_64), after JBT installation update site and restart I have:
> {code}
> !ENTRY org.eclipse.osgi 4 0 2013-12-16 15:35:03.535
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> at java.util.ArrayList.iterator(ArrayList.java:814)
> at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:962)
> at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:454)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:412)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:402)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1510)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1481)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1424)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> {code}
> Even if I raise a memory for JVM, Eclipse doesn't start but not error message is written
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16308) Cannot start JBT 4.2.0.Alpha1 on Fedora 19
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16308?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-16308 at 12/16/13 12:29 PM:
---------------------------------------------------------------
I can reproduce this on Fedora 18 using this launch script for Eclipse 4.4.M3 Standard (not JEE) bundle, installing ALL categorized features from http://download.jboss.org/jbosstools/updates/JBossTools-4.2.0.Alpha1.core/.
{code}
$➔ uname -a
Linux thunk 3.11.9-100.fc18.x86_64 #1 SMP Wed Nov 20 21:22:39 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
$➔ /opt/sun-java2-7.0/bin/java -version
java version "1.7.0_17"
Java(TM) SE Runtime Environment (build 1.7.0_17-b02)
Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
{code}
{code}
#!/bin/bash
workspace=/home/nboldt/eclipse/workspace-clean44
target=/home/nboldt/eclipse/44clean
eclipse=/home/nboldt/tmp/Eclipse_Bundles/eclipse-standard-luna-M3-linux-gtk-x86_64.tar.gz
cd ${target}
if [[ $1 == "e" ]]; then
echo "Wipe $target/eclipse and $workspace ..."
rm -fr $target/eclipse $workspace
echo "Unpack $eclipse ..."
tar xzf $eclipse
shift
fi
#export GDK_NATIVE_WINDOWS=true
${target}/eclipse/eclipse -clean -showLocation -data $workspace -consolelog -console -vm /opt/sun-java2-7.0/bin/java "$*" 2>&1 | tee "logs/eclipse.log.`date`.txt"
{code}
After installation and cold restart w/ -debug flag, I get this crash, though it took 6 minutes to appear:
{code}
[11:47:38] nboldt@thunk:~/eclipse/44clean
$➔ ./e -debug
Install location:
file:/home/nboldt/eclipse/44clean/eclipse/
Configuration file:
file:/home/nboldt/eclipse/44clean/eclipse/configuration/config.ini loaded
Configuration location:
file:/home/nboldt/eclipse/44clean/eclipse/configuration/
Framework located:
file:/home/nboldt/eclipse/44clean/eclipse/plugins/org.eclipse.osgi_3.10.0.v20131024-2025.jar
Loading extension: reference:file:org.eclipse.osgi.compatibility.state_1.0.0.v20131023-1243.jar
eclipse.properties not found
Loading extension: reference:file:org.eclipse.birt.jetty.overlay_4.3.1.v201308301349.jar
eclipse.properties not found
Framework classpath:
file:/home/nboldt/eclipse/44clean/eclipse/plugins/org.eclipse.osgi_3.10.0.v20131024-2025.jar
file:/home/nboldt/eclipse/44clean/eclipse/plugins/
file:/home/nboldt/eclipse/44clean/eclipse/plugins/org.eclipse.osgi.compatibility.state_1.0.0.v20131023-1243.jar
file:/home/nboldt/eclipse/44clean/eclipse/plugins/org.eclipse.birt.jetty.overlay_4.3.1.v201308301349.jar
Splash location:
/home/nboldt/eclipse/44clean/eclipse//plugins/org.eclipse.platform_4.4.0.v20131030-2000/splash.bmp
Debug options:
file:/home/nboldt/eclipse/44clean/.options not found
Time to load bundles: 45
Starting application: 338649
osgi> #
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f8429af2255, pid=18745, tid=140208137373440
#
# JRE version: 7.0_17-b02
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libxul.so+0xc81255] JSD_DebuggerOnForUser+0x978a2
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/nboldt/eclipse/44clean/hs_err_pid18745.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Start VM: /opt/sun-java2-7.0/bin/java
-Dosgi.requiredJavaVersion=1.6
-XX:MaxPermSize=256m
-Xms40m
-Xmx512m
-jar /home/nboldt/eclipse/44clean/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
-os linux
-ws gtk
-arch x86_64
-showsplash /home/nboldt/eclipse/44clean/eclipse//plugins/org.eclipse.platform_4.4.0.v20131030-2000/splash.bmp
-launcher /home/nboldt/eclipse/44clean/eclipse/eclipse
-name Eclipse
--launcher.library /home/nboldt/eclipse/44clean/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20131025-1931/eclipse_1601.so
-startup /home/nboldt/eclipse/44clean/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.appendVmargs
-exitdata cb802d
-product org.eclipse.epp.package.standard.product
-clean
-showLocation
-data /home/nboldt/eclipse/workspace-clean44
-consolelog
-console
-debug
-vm /opt/sun-java2-7.0/bin/java
-vmargs
-Dosgi.requiredJavaVersion=1.6
-XX:MaxPermSize=256m
-Xms40m
-Xmx512m
-jar /home/nboldt/eclipse/44clean/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
[11:53:39] nboldt@thunk:~/eclipse/44clean
{code}
was (Author: nickboldt):
I can reproduce this on Fedora 18 using this launch script for Eclipse 4.4.M3 Standard (not JEE) bundle, installing ALL categorized features from http://download.jboss.org/jbosstools/updates/JBossTools-4.2.0.Alpha1.core/.
{code}
$➔ uname -a
Linux thunk 3.11.9-100.fc18.x86_64 #1 SMP Wed Nov 20 21:22:39 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
$➔ /opt/sun-java2-7.0/bin/java -version
java version "1.7.0_17"
Java(TM) SE Runtime Environment (build 1.7.0_17-b02)
Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
{code}
{code}
#!/bin/bash
workspace=/home/nboldt/eclipse/workspace-clean44
target=/home/nboldt/eclipse/44clean
eclipse=/home/nboldt/tmp/Eclipse_Bundles/eclipse-standard-luna-M3-linux-gtk-x86_64.tar.gz
cd ${target}
if [[ $1 == "e" ]]; then
echo "Wipe $target/eclipse and $workspace ..."
rm -fr $target/eclipse $workspace
echo "Unpack $eclipse ..."
tar xzf $eclipse
shift
fi
#export GDK_NATIVE_WINDOWS=true
${target}/eclipse/eclipse -clean -showLocation -data $workspace -consolelog -console -vm /opt/sun-java2-7.0/bin/java "$*" 2>&1 | tee "logs/eclipse.log.`date`.txt"
{code}
After installation and warm restart, I get this:
{code}
Wipe /home/nboldt/eclipse/44clean/eclipse and /home/nboldt/eclipse/workspace-clean44 ...
Unpack /home/nboldt/tmp/Eclipse_Bundles/eclipse-standard-luna-M3-linux-gtk-x86_64.tar.gz ...
osgi> osgi> #
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f7e952f2255, pid=15646, tid=140184237340416
#
# JRE version: 7.0_17-b02
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libxul.so+0xc81255] JSD_DebuggerOnForUser+0x978a2
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/nboldt/eclipse/43clean/hs_err_pid15646.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
{code}
Same crash occurs for a cold restart, though it may take over a minute for the crash to occur.
> Cannot start JBT 4.2.0.Alpha1 on Fedora 19
> ------------------------------------------
>
> Key: JBIDE-16308
> URL: https://issues.jboss.org/browse/JBIDE-16308
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Environment: JBT 4.2.Alpha1, L64, Fedora 19, 64-bit, Open JDK 1.7
> Reporter: Jiri Peterka
> Priority: Blocker
> Fix For: 4.2.0.Alpha1
>
> Attachments: hs_err_pid17371.log
>
>
> Installing JBT on Eclipse -4.4.M4- 4.4.M3 JEE package (linux_64), after JBT installation update site and restart I have:
> {code}
> !ENTRY org.eclipse.osgi 4 0 2013-12-16 15:35:03.535
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> at java.util.ArrayList.iterator(ArrayList.java:814)
> at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:962)
> at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:454)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:412)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:402)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1510)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1481)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1424)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> {code}
> Even if I raise a memory for JVM, Eclipse doesn't start but not error message is written
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months