Re: [isabelle] Plugin error with Isabelle-2016

What I am easily and reliably able to reproduce is as follows:

% /opt/Isabelle2016/Isabelle2016 &
(wait for Isabelle to start)
% kill -KILL 29909   # or whatever the PID is of the Java process
[1]  + Killed                        /opt/Isabelle2016/Isabelle2016
% /opt/Isabelle2016/Isabelle2016&
[1] 9015
% 7:40:39 AM [main] [error] PluginJAR: Error while starting plugin isabelle.jedit.Plugin
7:40:39 AM [main] [error] PluginJAR: java.lang.NoClassDefFoundError: scala/Function0
7:40:39 AM [main] [error] PluginJAR:  at java.lang.Class.getDeclaredConstructors0(Native Method)
7:40:39 AM [main] [error] PluginJAR:  at java.lang.Class.privateGetDeclaredConstructors(
7:40:39 AM [main] [error] PluginJAR:  at java.lang.Class.getConstructor0(
7:40:39 AM [main] [error] PluginJAR:  at java.lang.Class.newInstance(
7:40:39 AM [main] [error] PluginJAR:  at org.gjt.sp.jedit.PluginJAR.activatePlugin(
7:40:39 AM [main] [error] PluginJAR:  at org.gjt.sp.jedit.PluginJAR.activatePluginIfNecessary(
7:40:39 AM [main] [error] PluginJAR:  at org.gjt.sp.jedit.jEdit.main(
7:40:39 AM [main] [error] PluginJAR: Caused by: java.lang.ClassNotFoundException: scala.Function0
7:40:39 AM [main] [error] PluginJAR:  at
7:40:39 AM [main] [error] PluginJAR:  at java.lang.ClassLoader.loadClass(
7:40:39 AM [main] [error] PluginJAR:  at sun.misc.Launcher$AppClassLoader.loadClass(
7:40:39 AM [main] [error] PluginJAR:  at java.lang.ClassLoader.loadClass(
7:40:39 AM [main] [error] PluginJAR:  at org.gjt.sp.jedit.JARClassLoader.loadFromParent(
7:40:39 AM [main] [error] PluginJAR:  at org.gjt.sp.jedit.JARClassLoader.loadClass(
7:40:39 AM [main] [error] PluginJAR:  at java.lang.ClassLoader.loadClass(
7:40:39 AM [main] [error] PluginJAR:  ... 7 more
7:40:39 AM [main] [error] ErrorListDialog$ErrorEntry: /opt/Isabelle2016/src/Tools/jEdit/dist/jars/Isabelle-jEdit.jar:
7:40:39 AM [main] [error] ErrorListDialog$ErrorEntry: Cannot start: java.lang.NoClassDefFoundError: scala/Function0
7:40:39 AM [main] [error] ErrorListDialog$ErrorEntry: Try updating to a newer version of the plugin.
7:40:39 AM [main] [error] View: No docking framework PIDE available, using the original one
7:40:43 AM [AWT-EventQueue-0] [error] DockableWindowManagerImpl: Unknown dockable window: isabelle-output
7:40:43 AM [AWT-EventQueue-0] [error] DockableWindowManagerImpl: Unknown dockable window: isabelle-theories

JEdit displays a "Plugin Error" pop-up that says:

Cannot start: java.lang.NoClassDefFoundError: scala/Function0
Try updating to a newer version of the plugin.

(Click on OK)
(Exit JEdit using the menu)

[1]    Done                          /opt/Isabelle2016/Isabelle2016
% /opt/Isabelle2016/Isabelle2016&

(Isabelle starts normally)

This is on Ubuntu 14.04LTS using Unity.

							- Gene Stark

On 07/28/2016 04:21 PM, Makarius wrote:
> On 26/07/16 11:48, Dominic Mulligan via Cl-isabelle-users wrote:
>> Hi Eugene, Hans-Joerg,
>>> Could it be that the failures you are seeing are the result of abnormal
>>> shutdowns of the immediately preceding sessions?
>> It may very well be, though I admit I haven't been paying enough
>> attention to confirm one way or the other!  Hans-Joerg's e-mail seems
>> to suggest that this is a likely cause, however.
> Studying all mails on this thread again, I am unsure if the problems are
> necessarily related.
> The general situation is that Isabelle application startup needs to load
> and warm-up many jars. If anything goes wrong, e.g. due to network
> file-system errors, bad things might happen.
> I am not really an expert on the JVM, even after almost 10 years of
> using it routinely. jEdit has its own tricks for class loading, but this
> is only for the topmost plugin container, not the underlying Scala
> libraries -- these are loaded before jedit.jar itself.
> To rule out accidental problems with a particular JVM version, I've made
> the following alternative application bundles of Isabelle2016 with old
> but stable jdk-7u80 and newly updated jdk-8u102:
> After the summer, we will be heading again towards the next Isabelle
> release (before the end of the year).
> It would be nice if known JVM instabilities are clearly isolated and
> eliminated until then.
> 	Makarius

This archive was generated by a fusion of Pipermail (Mailman edition) and MHonArc.