xRouteServer feature layer installation on Linux

This forum deals with any kind of routing computation whether it is simple A:B-routing, calculation of isochrones, simple matrix computation or nearest search.
Post Reply
biro.daniel
Posts: 41
Joined: Tue Aug 23, 2016 8:08 am

xRouteServer feature layer installation on Linux

Post by biro.daniel »

Hello Guys,

I would like to use PTV xRouteServer with feature layer (with TruckAttributes) on linux but unfortunatelly I have some issues. When "featurelayer" folder is presented under the map folder (EuroPremium.geo) xRoute server could not be started. If I remove the "featurelayer" folder the server can be started but obviously feature layer could not be used in route planning.

Here are my environment's parameters:

xRouteServer version: 1.24.0.0 x64 gcc4
JVM: Java SE Runtime Environment1.8.0_121-b13 (amd64)
OS: Ubuntu Server 16.04 LTS
Map: PTV_Europe_City_Map_Premium_2017_1H_8

Here are the xRoute error logs when "featurelayer" folder is presented:

Code: Select all

Running PTV xRoute Server 1.24.0.0...
STATUS | --> Wrapper Started as Console
STATUS | Java Service Wrapper Standard Edition 64-bit 3.5.25
STATUS |   Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
STATUS |     http://wrapper.tanukisoftware.com
STATUS |   Licensed to PTV Group for PTV xServer
STATUS |
STATUS | Launching a JVM...
INFO   | WrapperManager: Initializing...
INFO   | [com.ptvag.xserver.utils.startuptasks.StartupTasksExecutor] Looking for startup tasks in directory /opt/xroute/work/startup-tasks
INFO   | [com.ptvag.xserver.utils.startuptasks.StartupTasksExecutor] Startup tasks directory /opt/xroute/work/startup-tasks does not exist - continuing with server startup ...
INFO   | May 23, 2017 1:36:07 PM org.apache.coyote.AbstractProtocol init
INFO   | INFO: Initializing ProtocolHandler ["http-bio-50030"]
INFO   | May 23, 2017 1:36:07 PM org.apache.catalina.startup.Catalina load
INFO   | INFO: Initialization processed in 563 ms
INFO   | May 23, 2017 1:36:07 PM org.apache.catalina.core.StandardService startInternal
INFO   | INFO: Starting service PtvXServerService
INFO   | May 23, 2017 1:36:07 PM org.apache.catalina.core.StandardEngine startInternal
INFO   | INFO: Starting Servlet Engine: Apache Tomcat/7.0.57
INFO   | May 23, 2017 1:36:07 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO   | INFO: Deploying configuration descriptor /opt/xroute/conf/Catalina/localhost/ROOT.xml
INFO   | May 23, 2017 1:36:08 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO   | INFO: Deployment of configuration descriptor /opt/xroute/conf/Catalina/localhost/ROOT.xml has finished in 978 ms
INFO   | May 23, 2017 1:36:08 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO   | INFO: Deploying web application directory /opt/xroute/webapps/derby
INFO   | May 23, 2017 1:36:10 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO   | INFO: Deployment of web application directory /opt/xroute/webapps/derby has finished in 2,039 ms
INFO   | May 23, 2017 1:36:10 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO   | INFO: Deploying web application directory /opt/xroute/webapps/xroute
INFO   | May 23, 2017 1:36:13 PM org.apache.catalina.core.ApplicationContext log
INFO   | INFO: org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: loaded (conf ok)
INFO   | log4j:WARN No appenders could be found for logger (org.apache.cxf.common.logging.LogUtils).
INFO   | log4j:WARN Please initialize the log4j system properly.
INFO   | XRoute server starting...
INFO   | ... initializing server environment ...
INFO   | 2017-05-23 13:36:15,617;WARN;com.ptvgroup.xserver.framework.XServer1Dispatcher;queueing timeout <= 0 (-1ms) - using  60 secs instead
INFO   | 2017-05-23 13:36:15,644;INFO;com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper;xroute: Starting module instance m0001 in external process...
INFO   | 2017-05-23 13:36:15,644;INFO;com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper;xroute: Starting module instance m0002 in external process...
INFO   | 2017-05-23 13:36:16,877;INFO;com.ptvag.xserver.module.xroute.m0001;<no-request>;-;-;-;Created default directory for ShMemPath /opt/xroute/dyn/shm/
INFO   | 2017-05-23 13:36:16,878;INFO;com.ptvag.xserver.module.xroute.m0001;<no-request>;-;-;-;Created default directory for CurrREDBPath /opt/xroute/dyn/layer/
INFO   | 2017-05-23 13:36:34,353;ERROR;com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper;xroute: Module instance m0001 shutting down with exit code 134.
INFO   | 2017-05-23 13:36:34,682;ERROR;com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper;xroute: Error on starting module instance m0001: java.lang.RuntimeException: Module instance has terminated unexpectedly
INFO   | java.lang.RuntimeException: Module instance has terminated unexpectedly
INFO   |        at com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper.waitForStartup(ModuleInstanceProcessWrapper.java:597)
INFO   |        at com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper.startProcess(ModuleInstanceProcessWrapper.java:558)
INFO   |        at com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper.doStartSeparateProcess(ModuleInstanceProcessWrapper.java:415)
INFO   |        at com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper.doStart(ModuleInstanceProcessWrapper.java:388)
INFO   |        at com.google.common.util.concurrent.AbstractService.start(AbstractService.java:171)
INFO   |        at com.google.common.util.concurrent.AbstractService.startAndWait(AbstractService.java:221)
INFO   |        at com.ptvgroup.xserver.framework.ModuleAgent$ModuleRunner.startProcessor(ModuleAgent.java:371)
INFO   |        at com.ptvgroup.xserver.framework.ModuleAgent$ModuleRunner.run(ModuleAgent.java:243)
INFO   |        at java.lang.Thread.run(Thread.java:745)
INFO   | 2017-05-23 13:36:34,686;ERROR;com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper;xroute: Error during starting module instance m0001: ModuleInstanceStartupException, exitCode = 134
INFO   | ModuleInstanceStartupException, exitCode = 134
INFO   |        at com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper.startProcess(ModuleInstanceProcessWrapper.java:572)
INFO   |        at com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper.doStartSeparateProcess(ModuleInstanceProcessWrapper.java:415)
INFO   |        at com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper.doStart(ModuleInstanceProcessWrapper.java:388)
INFO   |        at com.google.common.util.concurrent.AbstractService.start(AbstractService.java:171)
INFO   |        at com.google.common.util.concurrent.AbstractService.startAndWait(AbstractService.java:221)
INFO   |        at com.ptvgroup.xserver.framework.ModuleAgent$ModuleRunner.startProcessor(ModuleAgent.java:371)
INFO   |        at com.ptvgroup.xserver.framework.ModuleAgent$ModuleRunner.run(ModuleAgent.java:243)
INFO   |        at java.lang.Thread.run(Thread.java:745)
INFO   | 2017-05-23 13:36:34,758;ERROR;com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper;xroute: Module instance m0002 shutting down with exit code 134.
INFO   | 2017-05-23 13:36:35,701;ERROR;com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper;xroute: Error on starting module instance m0002: java.lang.RuntimeException: Module instance has terminated unexpectedly
INFO   | java.lang.RuntimeException: Module instance has terminated unexpectedly
INFO   |        at com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper.waitForStartup(ModuleInstanceProcessWrapper.java:597)
INFO   |        at com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper.startProcess(ModuleInstanceProcessWrapper.java:558)
INFO   |        at com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper.doStartSeparateProcess(ModuleInstanceProcessWrapper.java:415)
INFO   |        at com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper.doStart(ModuleInstanceProcessWrapper.java:388)
INFO   |        at com.google.common.util.concurrent.AbstractService.start(AbstractService.java:171)
INFO   |        at com.google.common.util.concurrent.AbstractService.startAndWait(AbstractService.java:221)
INFO   |        at com.ptvgroup.xserver.framework.ModuleAgent$ModuleRunner.startProcessor(ModuleAgent.java:371)
INFO   |        at com.ptvgroup.xserver.framework.ModuleAgent$ModuleRunner.run(ModuleAgent.java:243)
INFO   |        at java.lang.Thread.run(Thread.java:745)
INFO   | 2017-05-23 13:36:35,701;ERROR;com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper;xroute: Error during starting module instance m0002: ModuleInstanceStartupException, exitCode = 134
INFO   | ModuleInstanceStartupException, exitCode = 134
INFO   |        at com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper.startProcess(ModuleInstanceProcessWrapper.java:572)
INFO   |        at com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper.doStartSeparateProcess(ModuleInstanceProcessWrapper.java:415)
INFO   |        at com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper.doStart(ModuleInstanceProcessWrapper.java:388)
INFO   |        at com.google.common.util.concurrent.AbstractService.start(AbstractService.java:171)
INFO   |        at com.google.common.util.concurrent.AbstractService.startAndWait(AbstractService.java:221)
INFO   |        at com.ptvgroup.xserver.framework.ModuleAgent$ModuleRunner.startProcessor(ModuleAgent.java:371)
INFO   |        at com.ptvgroup.xserver.framework.ModuleAgent$ModuleRunner.run(ModuleAgent.java:243)
INFO   |        at java.lang.Thread.run(Thread.java:745)
INFO   | System.exit(50)
INFO   | May 23, 2017 1:36:36 PM org.apache.catalina.core.StandardContext loadOnStartup
INFO   | SEVERE: Servlet /xroute threw load() exception
INFO   | ModuleInstanceStartupException, exitCode = 50
INFO   |        at com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper.startProcess(ModuleInstanceProcessWrapper.java:580)
INFO   |        at com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper.doStartSeparateProcess(ModuleInstanceProcessWrapper.java:415)
INFO   |        at com.ptvgroup.xserver.framework.ModuleInstanceProcessWrapper.doStart(ModuleInstanceProcessWrapper.java:388)
INFO   |        at com.google.common.util.concurrent.AbstractService.start(AbstractService.java:171)
INFO   |        at com.google.common.util.concurrent.AbstractService.startAndWait(AbstractService.java:221)
INFO   |        at com.ptvgroup.xserver.framework.ModuleAgent$ModuleRunner.startProcessor(ModuleAgent.java:371)
INFO   |        at com.ptvgroup.xserver.framework.ModuleAgent$ModuleRunner.run(ModuleAgent.java:243)
INFO   |        at java.lang.Thread.run(Thread.java:745)
INFO   |
INFO   | Derby database stopped
STATUS | <-- Wrapper Stopped
Could you please help use to figure out why we get the above errors?

Thank you in advance
BR
Daniel
User avatar
Bernd Welter
Site Admin
Posts: 2564
Joined: Mon Apr 14, 2014 10:28 am
Contact:

Re: xRouteServer feature layer installation on Linux

Post by Bernd Welter »

Hi guys,

as mentioned via email: in case of a blocking issue you should always get in touch with support.
So let's raise a ticket!

Best regards Bernd
Bernd Welter
Technical Partner Manager Developer Components
PTV Logistics - Germany

Bernd at... The Forum,LinkedIn, Youtube, StackOverflow
I like the smell of PTV Developer in the morning... :twisted:
User avatar
Bernd Welter
Site Admin
Posts: 2564
Joined: Mon Apr 14, 2014 10:28 am
Contact:

Re: xRouteServer feature layer installation on Linux

Post by Bernd Welter »

Here we go. Looks like we have found the cause for the trouble:
  • the customer uses our default deployment generated from the data setup. The deployment contains all featurelayers without trafficincidents. Docker has a default shared memory size of 64Mb. In our test deployment the /dev/shm folder has 220Mb after starting the xRoute.
  • We think the shared memory should not increase after the server startup, at least regarding the FeatureLayer side. We are doing some tests, but 100 Mb should be sufficient for the TomTom 2017 Europe map, for all the FL.
  • Of course, the more FL themes you use, the higher shared-memory size you'll need.
  • We think a recommendation of 256mb of shared memory should make a docker production system safe. The memory is only required on startup and no additional memory is required per request.
  • So please check the option "--shm-size=256MB" of "docker run" (produces a shared-memory segment of 256MB in size)
Strike, thanks to Reinhard and Rüdiger and the colleagues in Cergy for the research and to NEXOGEN for the patience ;-)

Bernd
Bernd Welter
Technical Partner Manager Developer Components
PTV Logistics - Germany

Bernd at... The Forum,LinkedIn, Youtube, StackOverflow
I like the smell of PTV Developer in the morning... :twisted:
Post Reply