[arjan.tijms]

Hi,

I’m running on a C2Q Q6600/2GB on Debian Lenny using Java 6 update 4, MyEclipse 6.0.1 and Eclipse 3.3.1. I’m running in 64 bits mode. MyEclipse was installed using the manual install.

The problem I’m running in to is that every time a deployment is being done (either the initial deployment or the builder triggered one if I modify a resource), the JVM crashes.

The error reported by the JVM is the following:

# An unexpected error has been detected by Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00002b508c4d622a, pid=28173, tid=1085491536
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (10.0-b19 mixed mode linux-amd64)
# Problematic frame:
# V  [libjvm.so+0x1f122a]
#
# An error report file with more information is saved as:
# /home/arjan.tijms/programs/eclipse33/eclipse/hs_err_pid28173.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

I tried this a great number of times. Occasionally, the deployment succeeds, but then iMyEclipse crashes as soon as I modify a resource and the automatic deployment starts. The error reported by the JVM is always the same.

I downgraded to Java 1.6 update 3, and it seems to work now. I do however still get a number of errors in my .log:

!SESSION 2008-02-19 15:35:39.349 -----------------------------------------------
eclipse.buildId=M20071023-1652
java.version=1.6.0_03
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments:  -product com.genuitec.myeclipse.product.ide
Command-line arguments:  -os linux -ws gtk -arch x86_64 -clean -product com.genuitec.myeclipse.product.ide

!ENTRY org.eclipse.update.configurator 2008-02-19 15:35:41.378
!MESSAGE Could not install bundle ../myeclipse/eclipse/plugins/org.apache.commons.el_1.0.0.v200706111724.jar   Bundle "org.apache.commons.el" version "1.0.0.v200706111724" has already been installe
d from: update@plugins/org.apache.commons.el_1.0.0.v200706111724.jar

!ENTRY org.eclipse.update.configurator 2008-02-19 15:35:41.495
!MESSAGE Could not install bundle ../myeclipse/eclipse/plugins/org.apache.commons.logging_1.0.4.v200706111724.jar   Bundle "org.apache.commons.logging" version "1.0.4.v200706111724" has already bee
n installed from: update@plugins/org.apache.commons.logging_1.0.4.v200706111724.jar

!ENTRY org.eclipse.update.configurator 2008-02-19 15:35:41.841
!MESSAGE Could not install bundle ../myeclipse/eclipse/plugins/javax.servlet_2.4.0.v200706111738.jar   Bundle "javax.servlet" version "2.4.0.v200706111738" has already been installed from: update@p
lugins/javax.servlet_2.4.0.v200706111738.jar

!ENTRY org.eclipse.update.configurator 2008-02-19 15:35:41.910
!MESSAGE Could not install bundle ../myeclipse/eclipse/plugins/javax.servlet.jsp_2.0.0.v200706191603.jar   Bundle "javax.servlet.jsp" version "2.0.0.v200706191603" has already been installed from: 
update@plugins/javax.servlet.jsp_2.0.0.v200706191603.jar

!ENTRY org.eclipse.core.resources 2 1 2008-02-19 15:36:04.426
!MESSAGE Skipping builder 'de.bb.bje.eclipse.IncrementalJspBuilder' for project 'm4n_J2EE'. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled.

Any help would be appreciated.

[Riyad Kalla]

Arjan,
I’m glad to hear that _03 fixed the issue, we have seen some strange issues with any JDK release after 1.5.0_11, it seems something changed in the VM. We haven’t officially side-stepped any development work to troubleshoot it, that will naturally come with the Ganymede move I’m sure.

As for the errors, all the Bundle stuff is harmless, it’s just notifying you it’s being installed from somewhere else first.

And the last message… bje was the *original* JSP compiler we had in MyEclipse back in the 2.x days (I think you were with us then?). I have no idea why that would be coming up, but it’s harmless as well. I’ll make a note to figure out why that is getting logged and remove it.

So in short, looks like things are OK.

[arjan.tijms]

@support-rkalla wrote:

Arjan,
I’m glad to hear that _03 fixed the issue, we have seen some strange issues with any JDK release after 1.5.0_11, it seems something changed in the VM.

There were indeed a lot of compiler/hotspot related updates in Java 6 u 4. As a programmer I wonder though what kind of Java code could very reproducible cause the JVM to crash. It may be an interesting case to report back to the JDK team.

And the last message… bje was the *original* JSP compiler we had in MyEclipse back in the 2.x days (I think you were with us then?).

We were, since early 2004 😉

[Riyad Kalla]

It may be an interesting case to report back to the JDK team.

If the devs dig up anything interesting during 7.0 dev I’ll let you know.

We were, since early 2004 😉

Nice! Thanks for the long time support, we hope you guys have been happy.

[Author]

Posts