Bug#847581: jabref: doesn't always exit and throws exception upon exit

[tony mancill]

On Fri, Dec 9, 2016 at 8:17 AM, tony mancill <tmancill at debian.org> wrote:
> Package: jabref
> Version: 3.6+ds-1
> Severity: normal
>
> In case this helps others, this is a known issue with JabRef 3.6.
> When exiting jabref on some machines (but not others), it prints the
> following exception and hangs with:
>
> 08:05:46.741 [AWT-EventQueue-1] DEBUG net.sf.jabref.logic.remote.server.RemoteListenerServerThread - Interrupting JabRef - Remote Listener Server on port 6050
> 08:05:46.741 [JabRef - FileUpdateMonitor - low prio] DEBUG net.sf.jabref.collab.FileUpdateMonitor - FileUpdateMonitor has been interrupted. Terminating...
> java.lang.InterruptedException: sleep interrupted
>         at java.lang.Thread.sleep(Native Method) ~[?:1.8.0_111]
>         at net.sf.jabref.collab.FileUpdateMonitor.run(FileUpdateMonitor.java:43) [JabRef-3.6.jar:?]
>         at net.sf.jabref.JabRefExecutorService$AutoCleanupRunnable.run(JabRefExecutorService.java:81) [JabRef-3.6.jar:?]
>         at java.lang.Thread.run(Thread.java:745) [?:1.8.0_111]
>
> The user then has to press CTRL-C before the JVM process will terminate.

To date I have only observed and been able to reproduce this within a
VirtualBox image, which leads me to believe that it could be a problem
Java's interaction with X server or something else not directly
related to JabRef.