Bug 466897 - VMDisconnectedException in PacketSendManager.sendPacket (90)
Summary: VMDisconnectedException in PacketSendManager.sendPacket (90)
Status: CLOSED DUPLICATE of bug 7804
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.5   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Sarika Sinha CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-09 04:26 EDT by EPP Error Reports CLA
Modified: 2015-06-01 06:31 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description EPP Error Reports CLA 2015-05-09 04:26:12 EDT
The following incident was reported via the automated error reporting:


    code:                   125
    plugin:                 org.eclipse.jdt.debug_3.9.0.v20150314-0247
    message:                Internal error logged from JDI Debug: 
    fingerprint:            239e6f4f
    exception class:        com.sun.jdi.VMDisconnectedException
    exception message:      Got IOException from Virtual Machine
    number of children:     0
    
    com.sun.jdi.VMDisconnectedException: Got IOException from Virtual Machine
    at org.eclipse.jdi.internal.connect.PacketSendManager.sendPacket(PacketSendManager.java:90)
    at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:187)
    at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:227)
    at org.eclipse.jdi.internal.VirtualMachineImpl.classesBySignature(VirtualMachineImpl.java:652)
    at org.eclipse.jdi.internal.VirtualMachineImpl.classesByName(VirtualMachineImpl.java:682)
    at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.jdiClassesByName(JDIDebugTarget.java:1630)
    at org.eclipse.jdt.internal.debug.core.hcr.JavaHotCodeReplaceManager.getTypesToBytes(JavaHotCodeReplaceManager.java:721)
    at org.eclipse.jdt.internal.debug.core.hcr.JavaHotCodeReplaceManager.redefineTypesJDK(JavaHotCodeReplaceManager.java:613)
    at org.eclipse.jdt.internal.debug.core.hcr.JavaHotCodeReplaceManager.doHotCodeReplace(JavaHotCodeReplaceManager.java:491)
    at org.eclipse.jdt.internal.debug.core.hcr.JavaHotCodeReplaceManager.access$0(JavaHotCodeReplaceManager.java:445)
    at org.eclipse.jdt.internal.debug.core.hcr.JavaHotCodeReplaceManager$1.run(JavaHotCodeReplaceManager.java:316)
    at org.eclipse.debug.core.DebugPlugin$AsynchRunner.run(DebugPlugin.java:1116)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.debug.core.DebugPlugin$AsynchRunner.async(DebugPlugin.java:1097)
    at org.eclipse.debug.core.DebugPlugin$EventDispatchJob.run(DebugPlugin.java:439)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
   
  

General Information:

    reported-by:      
    anonymous-id:     cb629dba-4c48-4ea8-9a30-cee19c00421d
    eclipse-build-id: 4.5.0.I20150320-0800
    eclipse-product:  org.eclipse.epp.package.jee.product
    operating system: Linux 3.8.0 (x86_64) - gtk
    jre-version:      1.7.0_09-b05

The following plug-ins were present on the execution stack (*):
    1. org.eclipse.core.jobs_3.7.0.v20150316-1238
    2. org.eclipse.core.runtime_3.11.0.v20150316-1241
    3. org.eclipse.debug.core_3.10.0.v20150303-1130
    4. org.eclipse.jdt.debug_3.9.0.v20150314-0247
    5. org.eclipse.jdt_3.11.0.v20150320-0800

Please note that:
* Messages, stacktraces, and nested status objects may be shortened.
* Bug fields like status, resolution, and whiteboard are sent
  back to reporters.
* The list of present bundles and their respective versions was
  calculated by package naming heuristics. This may or may not reflect reality.

Other Resources:
* Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/55222668e4b026254ee0135a  
* Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide


Thank you for your assistance.
Your friendly error-reports-inbox.
Comment 1 Marcel Bruch CLA 2015-05-10 03:38:26 EDT
The vm actually crashed:
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x000000010fa22d8c, pid=19251, tid=18691
#
# JRE version: Java(TM) SE Runtime Environment (8.0_20-b26) (build 1.8.0_20-b26)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.20-b23 mixed mode bsd-amd64 compressed oops)
# Problematic frame:
# V  [libjvm.dylib+0x422d8c]
#
# 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:
# /Users/marcel/Git/com.codetrails.confess-master/com.codetrails.confess2.server/hs_err_pid19251.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
#

There is nothing to fix. But maybe we don't need to log this error - or use a better message + stacktrace?
Comment 2 Sarika Sinha CLA 2015-06-01 06:31:33 EDT

*** This bug has been marked as a duplicate of bug 7804 ***