[Routing] PluginLifecycleException during TurnRestrictedMultiTargetDijkstraRouter.route method execution

[Oleg Demchenko]

Hi Markus and all.

I'm running this method from java web app under TomCat.
Sources of libosm, osmnavigation and ts are downloaded from SVN, modified
and recompiled with my application.
I've did a series of corrections to make method more "stable" with a
different country speed restrictions, illegal way width, height, length,
maximal speed tags permanently
occurred within OSM database used.

It works pretty fine with a short distance, but server CPU/RAM is not good
enough to find path  for 150 Kms and more. It takes several minutes.
For my last soap call I get the following exception under TomCat:
*SEVERE: org/java/plugin/PluginLifecycleException
java.lang.NoClassDefFoundError: org/java/plugin/PluginLifecycleException
 at
org.openstreetmap.travelingsalesman.routing.selectors.Motorcar.isAllowed(Unknown
Source)
 at
org.openstreetmap.travelingsalesman.routing.routers.TurnRestrictedAStar.getNextNodes(Unknown
Source)
 at
org.openstreetmap.travelingsalesman.routing.routers.TurnRestrictedAStar.route(Unknown
Source)
 at
org.openstreetmap.travelingsalesman.routing.routers.TurnRestrictedAStar.route(Unknown
Source)*
...
* at java.lang.Thread.run(Unknown Source)*
*Caused by: java.lang.ClassNotFoundException:
org.java.plugin.PluginLifecycleException
 at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1645)
 at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1491)
*

It happened after 180 seconds of request execution. In previous Markus
answers I've found reason could be jpf*.jar is missed in CP. But, jpf.jar
with PluginLifeCycle classes is in my Libosm project.

How to make MotorCar plugin object LifeCycle time longer? For example 5
minutes?
Didn't find any parameters within jpf.jar resources.

-- 
All the best
               Oleg Demchenko
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/routing/attachments/20101004/e12435e8/attachment.html>