search

eclipse-qvto / org.eclipse.qvto

Eclipse Public License 2.0
0 stars 0 forks source link

EOFException below VMRemoteClient.sendRequest (thrown in ObjectInputStream$BlockDataInputStream.peekByte) #993

Open eclipse-qvt-oml-bot opened 5 hours ago

eclipse-qvt-oml-bot commented 5 hours ago

| --- | --- | | Bugzilla Link | 512413 | | Status | UNCONFIRMED | | Importance | P3 normal | | Reported | Feb 20, 2017 04:19 EDT | | Modified | Feb 20, 2017 04:24 EDT | | Reporter | EPP Error Reports |

Description

The following problem was reported via the automated error reporting:

Message: Send debug request failed\ java.io.EOFException: null\ at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2903)\ at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1502)\ at java.io.ObjectInputStream.readObject(ObjectInputStream.java:422)\ at org.eclipse.m2m.qvt.oml.debug.core.vm.VMRemoteClient.sendRequest(VMRemoteClient.java:91)\ at org.eclipse.m2m.qvt.oml.debug.core.vm.QVTOVirtualMachineProxy.sendRequest(QVTOVirtualMachineProxy.java:60)\ at org.eclipse.m2m.qvt.oml.debug.core.QVTODebugTarget.sendRequest(QVTODebugTarget.java:194)\ at org.eclipse.m2m.qvt.oml.debug.core.QVTODebugTarget.(QVTODebugTarget.java:97)\ at org.eclipse.m2m.internal.qvt.oml.jdt.debug.ui.launch.QVTODebugApplicationConfiguration$2.(QVTODebugApplicationConfiguration.java:110)\ at org.eclipse.m2m.internal.qvt.oml.jdt.debug.ui.launch.QVTODebugApplicationConfiguration.launch(QVTODebugApplicationConfiguration.java:110)\ at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)\ at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)\ at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)\ at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)\ at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Bundles:\ | org.eclipse.core.jobs | 3.8.0.v20160509-0411 | 3.8.0.v20160509-0411 |\ | org.eclipse.debug.core | 3.10.100.v20160419-1720 | 3.10.100.v20160419-1720 |\ | org.eclipse.debug.ui | 3.11.202.v20161114-0338 | 3.11.202.v20161114-0338 |\ | org.eclipse.m2m.qvt.oml | 3.6.0.v20160606-1156 | 3.6.0.v20160606-1156 |\ | org.eclipse.m2m.qvt.oml.debug.core | 2.6.0.v20160606-1156 | 2.6.0.v20160606-1156 |

Operating Systems:\ | Linux | 4.9.6 | 4.9.6 |

The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/58a3a22ce4b05548a19b392b for the latest data.

Thank you for your assistance.\ Your friendly error-reports-inbox.

Created on behalf of ed@xxxxxx.xxx

eclipse-qvt-oml-bot commented 5 hours ago

By Ed Willink on Feb 20, 2017 04:21

Bug 512414 has been marked as a duplicate of this bug.

eclipse-qvt-oml-bot commented 5 hours ago

By Ed Willink on Feb 20, 2017 04:24

Looks like a normal debug connection problem. Probably shouldn't happen, but they seem to, particularly if machines are busy and timeouts too short.

Real issue is that the QVTo debig ctivation was interactive, so the user deserves a popup to notify the SNAFU. If there is already a popup, the error log is bloat. If not, a popup is needed, and the error log is still bloat.