task #5375
opencdm-server without jsvc
0%
Description
jsvc is used to start the cdm-server as daemon. Jetty 8 is however no longer using jsvc it is using the apache commons-daemon which actually is the successor to jsvc. The commons-daemon website still suggests the usage of the native jsvc library but jetty no longer has a package dependency to it.
jetty 8 startup command:
/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java -Xmx256m -Djava.awt.headless=true -Djava.io.tmpdir=/var/cache/jetty8/data -Djava.library.path=/usr/lib -DSTART=/etc/jetty8/start.config -Djetty.home=/usr/share/jetty8 -Djetty.logs=/var/log/jetty8 -Djetty.state=/var/lib/jetty8/jetty.state -Djetty.host=0.0.0.0 -Djetty.port=8080 -cp /usr/share/java/commons-daemon.jar:/usr/share/jetty8/start.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/tools.jar org.eclipse.jetty.start.Main --daemon etc/jetty-logging.xml etc/jetty-started.xml
a related story on tomcat: http://blogs.mulesoft.com/dev/tomcat-tcat-server/a-better-tomcat-for-ubuntu-and-debian/
Interesting links on this topic:
Related issues
Updated by Andreas Kohlbecker over 7 years ago
- Related to task #6522: package cdm-server in docker container added
Updated by Andreas Kohlbecker about 7 years ago
jsvc seems to cause Sigfaults in the jvm with the latest debian jessy updates, which where:
- libc6-dev amd64 2.19-18+deb8u10 [2003 kB]
- libc-dev-bin amd64 2.19-18+deb8u10 [238 kB]
- linux-libc-dev amd64 3.16.43-2+deb8u1 [1060 kB]
- libc-bin amd64 2.19-18+deb8u10 [1281 kB]
- libc6 amd64 2.19-18+deb8u10 [4665 kB]
- libffi6 amd64 3.1-2+deb8u1 [20.2 kB]
- linux-image-3.16.0-4-amd64 amd64 3.16.43-2+deb8u1 [33.9 MB]
- multiarch-support amd64 2.19-18+deb8u10 [181 kB]
- exim4-config all 4.84.2-2+deb8u4 [502 kB]
- exim4 all 4.84.2-2+deb8u4 [8584 B]
- exim4-base amd64 4.84.2-2+deb8u4 [1049 kB]
- exim4-daemon-light amd64 4.84.2-2+deb8u4 [632 kB]
- locales all 2.19-18+deb8u10 [3930 kB]
after starting the cdm-server daemon jsvc starts up normally and subsequenlty starts the jvm process which crashes early when loading the java runtime class libraries:
.... [Loaded java.lang.Character from /opt/java-oracle/jdk1.8.0_131/jre/lib/rt.jar] [Loaded java.lang.Number from /opt/java-oracle/jdk1.8.0_131/jre/lib/rt.jar] [Loaded java.lang.Float from /opt/java-oracle/jdk1.8.0_131/jre/lib/rt.jar] [Loaded java.lang.Double from /opt/java-oracle/jdk1.8.0_131/jre/lib/rt.jar] [Loaded java.lang.Byte from /opt/java-oracle/jdk1.8.0_131/jre/lib/rt.jar] [Loaded java.lang.Short from /opt/java-oracle/jdk1.8.0_131/jre/lib/rt.jar] [Loaded java.lang.Integer from /opt/java-oracle/jdk1.8.0_131/jre/lib/rt.jar] [Loaded java.lang.Long from /opt/java-oracle/jdk1.8.0_131/jre/lib/rt.jar] [Loaded java.lang.NullPointerException from /opt/java-oracle/jdk1.8.0_131/jre/lib/rt.jar] [Loaded java.lang.ArithmeticException from /opt/java-oracle/jdk1.8.0_131/jre/lib/rt.jar] Service killed by signal 11 Waiting 60 s to prevent looping Service killed by signal 11 Service killed by signal 11
Updated by Andreas Kohlbecker about 7 years ago
- Priority changed from New to Highest
- Target version changed from Unassigned CDM tickets to Release 4.9
- Severity changed from normal to critical
Updated by Andreas Kohlbecker about 7 years ago
reverting package upgrades can easily be done by the method that I described at stack overflow: https://superuser.com/questions/38717/how-can-i-undo-or-rollback-an-apt-get-upgrade-command-on-ubuntu/1221092#1221092
Updated by Andreas Müller about 7 years ago
- Target version changed from Release 4.9 to Release 4.10
Updated by Andreas Kohlbecker almost 7 years ago
A potential solution for the Service killed by signal 11
problem:
Updated by Andreas Kohlbecker almost 7 years ago
- Status changed from New to In Progress
- Priority changed from Highest to Priority13
- Severity changed from critical to normal
Andreas Kohlbecker wrote:
A potential solution for the
Service killed by signal 11
problem:
I tested a package upgrade on a clone from edit-jobber-1 by which kernel version 3.16.43-2+deb8u3 was installed. According to the above referenced post this is exactly the version which fixed the problem with jsvc.
After installing the upgrade the cdm-server reboots normally again. Even after a full system restart everything is ok.
Updated by Andreas Müller almost 7 years ago
- Target version changed from Release 4.10 to Release 4.11
Updated by Andreas Müller almost 7 years ago
- Target version changed from Release 4.11 to Release 4.12
Updated by Andreas Müller almost 7 years ago
- Target version changed from Release 4.12 to Release 4.13
Updated by Andreas Müller over 6 years ago
- Target version changed from Release 4.13 to Release 4.14
Updated by Andreas Müller over 6 years ago
- Target version changed from Release 4.14 to Release 5.0
Updated by Andreas Kohlbecker over 6 years ago
- Target version changed from Release 5.0 to Release 5.1
Updated by Andreas Kohlbecker about 6 years ago
- Target version changed from Release 5.1 to cdmlib - Old Next Major Release
Updated by Andreas Müller about 6 years ago
- Target version changed from cdmlib - Old Next Major Release to Unassigned CDM tickets
next major release is not to be used anymore
Updated by Andreas Kohlbecker about 6 years ago
- Target version changed from Unassigned CDM tickets to Release 5.3
Updated by Andreas Kohlbecker about 6 years ago
- Target version changed from Release 5.3 to Release 5.4
Updated by Andreas Kohlbecker almost 6 years ago
- Target version changed from Release 5.4 to Release 5.5
Updated by Andreas Kohlbecker almost 6 years ago
- Related to report #7898: using jstack on cdmserver with jsvc reports all non native threads as BLOCKED added
Updated by Andreas Kohlbecker over 5 years ago
- Target version changed from Release 5.5 to Release 5.6
Updated by Andreas Kohlbecker over 5 years ago
- Related to bug #5048: cdm-server causes unusual high native memory consumption for jvm added
Updated by Andreas Kohlbecker over 5 years ago
- Target version changed from Release 5.6 to Reviewed Next Major Release
Updated by Andreas Kohlbecker over 2 years ago
for the solution fond in the jetty project, you may refer to https://github.com/eclipse/jetty.project/issues/1485
Updated by Andreas Müller over 2 years ago
- Priority changed from Priority13 to Highest