Class loading exception in Protege 5 and Windows 7

[GoogleCodeExporter]

There seems to be a problem using the Protege plugin with P5 on Win 7. An 
attempt to start the reasoner leads to the following:

Error logged
org.semanticweb.elk.util.concurrent.computation.ComputationRuntimeException: 
Uncaught exception in a worker thread:
        at org.semanticweb.elk.util.concurrent.computation.ComputationExecutor$W
orker.run(ComputationExecutor.java:188)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.RuntimeException: java.lang.InterruptedException
        at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findCla
ss(BundleWiringImpl.java:2102)
        at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDele
gation(BundleWiringImpl.java:1501)
        at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringIm
pl.java:75)
        at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadCla
ss(BundleWiringImpl.java:1955)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at org.semanticweb.elk.reasoner.saturation.properties.ReflexivePropertyC
omputationFactory.getEngine(ReflexivePropertyComputationFactory.java:61)
        at org.semanticweb.elk.reasoner.saturation.properties.ReflexivePropertyC
omputationFactory.getEngine(ReflexivePropertyComputationFactory.java:44)
        at org.semanticweb.elk.util.concurrent.computation.ConcurrentComputation
WithInputs$Worker.run(ConcurrentComputationWithInputs.java:151)
        at org.semanticweb.elk.util.concurrent.computation.ComputationExecutor$W
orker.run(ComputationExecutor.java:186)
        ... 3 more
Caused by: java.lang.InterruptedException
        at java.lang.Object.wait(Native Method)
        at java.lang.Object.wait(Object.java:503)
        at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findCla
ss(BundleWiringImpl.java:2097)
        ... 11 more
Property Saturation Initialization started
Property Saturation Initialization using 8 workers
Property Saturation Initialization finished in 0 ms
Reflexive Property Computation started
Reflexive Property Computation using 8 workers
...

Original issue reported on code.google.com by pavel.kl...@gmail.com on 28 Jul 2014 at 2:51