facebook

Internal error during deployment

  1. MyEclipse Archived
  2.  > 
  3. Bugs
Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #293324 Reply

    Host: Linux splitter 2.6.27-9-server #1 SMP Thu Nov 20 22:56:07 UTC 2008 x86_64 GNU/Linux.

    Eclipse version: MyEclipse 7.0, installed via Pulse. The profile is the standard MyEclipse 7.0 profile with the additon of the Subclipse plugin and SVNKit client adaptor.

    Situation: while debugging an ear file (packaged) in JBoss, I started getting PermGen-full errors. I exited MyEclipse. The running copy of JBoss did not terminate when MyEclipse went down – I had to kill it via a plain kill command (not a kill -9). Subsequently every attempt to redeploy the .ear file shows an “internal Java error” dialog and recommends immediately terminating MyEclipse. I have tried removing and re-instituting the deployment from theEAR project, with no change. The stack trace inside the .log file of the workspace is the following:

    !ENTRY org.eclipse.core.jobs 4 2 2009-01-10 08:01:04.104
    !MESSAGE An internal error occurred during: “Add Deployment”.
    !STACK 0
    java.lang.InternalError
    at java.util.zip.Deflater.init(Native Method)
    at java.util.zip.Deflater.<init>(Unknown Source)
    at java.util.zip.ZipOutputStream.<init>(Unknown Source)
    at com.genuitec.eclipse.core.datatransfer.ZipFileExporter.<init>(ZipFileExporter.java:81)
    at com.genuitec.eclipse.core.datatransfer.ZipFileExportOperation.initialize(ZipFileExportOperation.java:255)
    at com.genuitec.eclipse.core.datatransfer.ZipFileExportOperation.run(ZipFileExportOperation.java:289)
    at com.genuitec.eclipse.ast.deploy.core.DeploymentUtil.archiveDirectory(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.ant.J2EEArchiveDeployer$1.run(Unknown Source)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1782)
    at com.genuitec.eclipse.ast.deploy.ant.J2EEArchiveDeployer.privExportWebProject(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.ant.J2EEArchiveDeployer.privExportWebProject(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.ant.J2EEArchiveDeployer.packageModules(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.ant.J2EEArchiveDeployer.exportEARProject(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.EARDeployment.exportEARProject(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.EARDeployment.deployAsPackageArchive(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.Deployment.deploy(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.jobs.A.�(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.jobs.A.run(Unknown Source)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

    #293405 Reply

    Loyal Water
    Member

    In the pulse explorer, can you right click on MyEclipse profile and select “Reinstall and then Run…”. Does that resolve the issue?

    #293566 Reply

    Nope. I even tried deleting the profile and rebuilding / reinstalling it, with no change.

    #293616 Reply

    Anybody have any thoughts? I’m back to MyEclipse 6.5 until we can get this fixed.

    #293672 Reply

    Loyal Water
    Member

    rws@templarcorp.com,
    The dev team is investigating this issue. Can you go to MyEclipse > Installation Summary > Installation Details and paste the information here for me.

    #293840 Reply

    *** Date:
    Thursday, January 22, 2009 5:14:46 PM EST

    ** System properties:
    OS=Linux
    OS version=2.6.27
    Java version=1.5.0_11

    *** MyEclipse details:
    MyEclipse Enterprise Workbench
    Version: 7.0
    Build id: 7.0-20081201

    *** Eclipse details:
    MyEclipse Enterprise Workbench

    Version: 7.0
    Build id: 7.0-20081201

    Eclipse Project SDK

    Version: 3.3.3.r33x_r20080129-7M7J7LB-u3aphGW6o3_VmiVfGXWO
    Build id: M20080911-1700

    Eclipse Platform

    Version: 3.4.1.r341_v20080731-9I96EiDElYevwz-p1bP5z-NlAaP7vtX6Utotqsu
    Build id: M20080911-1700

    Eclipse Java Development Tools

    Version: 3.4.1.r341_v20080709-0800-7o7tEAfEF_U5qyUgrb2HAp539P97
    Build id: M20080709-0800

    Eclipse Graphical Editing Framework GEF

    Version: 3.4.1.v20080806-67718083A56B4H2A3213573
    Build id: 200809101400

    Eclipse RCP

    Version: 3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341
    Build id: M20080703-0800

    Eclipse Plug-in Development Environment

    Version: 3.4.1.r341_v20080731-7T7U0E9mlRIuGUYviF_VP
    Build id: M20080703-0800

    Eclipse startup command=-os
    linux
    -ws
    gtk
    -arch
    x86_64
    -showsplash
    -launcher
    /home/shorero/Pulse/Software/MyEclipse_7.0 1/myeclipse
    -name
    Myeclipse
    –launcher.library
    /home/shorero/Pulse/Software/MyEclipse_7.0 1/../../Common/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.0.101.R34x_v20080731/eclipse_1115.so
    -startup
    /home/shorero/Pulse/Software/MyEclipse_7.0 1/../../Common/plugins/org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
    -exitdata
    1cf8006
    -clean
    -configuration
    /home/shorero/Pulse/Software/MyEclipse_7.0 1/configuration
    -vm
    /home/shorero/Pulse/Common/binary/com.sun.java.jre.linux.x86_64_1.5.0.011/bin/java

    #293863 Reply

    There’s a posting elsewhere suggesting that I should reinstall with the all-in-one installer rather than using Pulse. Is this a likely/possible solution for the problem?

    #293873 Reply

    Loyal Water
    Member

    rws@templarcorp.com,
    Are you working on a 64 bit OS?

    The All in One installer could be a possible solution.

    #293901 Reply

    Yes, it’s 64 bit. See the 1st line of the original post. OK, will see if bypassing Pulse solves the problem. Stand by…

    #293942 Reply

    Loyal Water
    Member

    ok.

    #294646 Reply

    dbennett455
    Participant

    SOLVED:

    I had the exact same problem under Centos 5.2 x86_64 and was able to resolve it by installing jdk1.5.0_17 from Sun. And then changing the -vm arg in the file ‘/opt/Genuitec/MyEclipse 7.0/myeclipse.ini’ to /usr/java/jdk1.5.0_17/bin/java.

    Note-1: I originally tried changing myeclipse.ini to use the 6.0 JDK but was unable to get network connectivity from inside MyEclipse.

    Note-2: I had trouble installing jdk-1_5_0_17-linux-amd64-rpm.bin as jdk1.6.0_12 was already installed. After running the *.rpm.bin through the shell, I then installed the RPM using ‘rpm -i jdk-1_5_0_17-linux-amd64.rpm –force’

    #294686 Reply

    Loyal Water
    Member

    Thank you for posting this information. I hope it helps the other users as well.

Viewing 12 posts - 1 through 12 (of 12 total)
Reply To: Internal error during deployment

You must be logged in to post in the forum log in