[ https://issues.jboss.org/browse/JBIDE-17264?page=com.atlassian.jira.plugi... ] Vineet Reynolds commented on JBIDE-17264: ----------------------------------------- I'm not sure if I've tracked this down completely, but the stack trace is quite clear on whether the above reported exception by George is thrown: {code} public abstract class AbstractCommand implements Command { public abstract CommandType getType(); public void handle(Document document) { AeshCorePlugin.log(new Throwable("Unimplemented command: " + getType())); } } {code} The {{org.jboss.tools.aesh.core.internal.ansi.CursorUp}} and other similar commands including the reported {{org.jboss.tools.aesh.core.internal.ansi.DeviceStatusReport}} all implement the same {{handle(Document)}} method through the super type {{AbstractCommand}}, which is to log the created {{Throwable}}. Other ANSI escape sequences like Cursor Back or Cursor Horizontal Absolute have valid implementations. However, I don't see this as the root cause. The console is capable of accepting input from the user after this. My current suspicion is that the underlying JFace document location is not in sync with the console location. And hence I sometimes see the following exception being logged (after I hit the enter key in the hung state): {code} !ENTRY org.jboss.tools.forge.aesh.ui 4 1 2014-08-26 12:48:38.189 !MESSAGE Error logged from Aesh UI Plugin: !STACK 0 org.eclipse.jface.text.BadLocationException at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1179) at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210) at org.jboss.tools.aesh.ui.internal.document.DocumentImpl$3.run(DocumentImpl.java:103) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) at org.eclipse.equinox.launcher.Main.run(Main.java:1465) at org.eclipse.equinox.launcher.Main.main(Main.java:1438) {code} Note that the command if valid is executed by Forge. -- This message was sent by Atlassian JIRA (v6.3.1#6329)