blocks|key|2078106|text|我不知道在Java应用程序中有什么“标准”的收缩包装方式可以做到这一点，但这绝对是一个好主意(您希望从操作系统的保持活动和监视功能中受益)。从Spring+Boot工具支持(maven和gradle)中提供一些东西是路线图上的目标，但现在您可能不得不使用自己的工具。目前我所知道的最好的解决方案是Foreman，它有一种声明式的方法和一行命令来将初始化脚本打包成各种标准的操作系统格式(monit，sys+V，upstart等)。也有证据表明人们已经设置了gradle的东西(例如here)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2078107|entityMap|0|LINK|mutability|MUTABLE|url|http://rubygems.org/gems/foreman|1|https://stackoverflow.com/questions/18619369/how-to-write-gradle-startup-script^0|44|7|0|6O|4|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

I don't know of a "standard" shrink-wrapped way to do that with a Java app, but it's definitely a good idea (you want to benefit from the keep-alive and monitoring capabilities of the operating system if they are there). It's on the roadmap to provide something from the Spring Boot tool support (maven and gradle), but for now you are probably going to have to roll your own. The best solution I know of right now is <a href="http://rubygems.org/gems/foreman" rel="nofollow noreferrer">Foreman</a>, which has a declarative approach and one line commands for packaging init scripts for various standard OS formats (monit, sys V, upstart etc.). There is also evidence of people having set stuff up with gradle (e.g. <a href="https://stackoverflow.com/questions/18619369/how-to-write-gradle-startup-script">here</a>).

blocks|key|1864553|text|在这个问题中，来自@PbxMan的答案应该会让你开始：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1864554|Run+a+Java+Application+as+a+Service+on+Linux|offset|length|1864555|编辑：|1864556|还有另一种在重新引导时启动进程的不太好的方法，使用cron：|1864557|@reboot+user-to-run-under+/usr/bin/java+-jar+/path/to/application.jar|code-block|syntax|javascript|1864558|这是可行的，但没有为您的应用程序提供良好的启动/停止接口。无论如何，你仍然可以简单地kill它。|style|CODE|1864559|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/11203483/run-a-java-application-as-a-service-on-linux^0|0|0|18|0|0|0|0|0|16|4|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@$D|12|E|13|1|14]]|A|$]]|$1|F|3|G|5|6|7|15|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|17|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|18|8|@$D|19|E|1A|Q|R]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

In this question, the answer from @PbxMan should get you started:

<a href="https://stackoverflow.com/questions/11203483/run-a-java-application-as-a-service-on-linux">Run a Java Application as a Service on Linux</a>

Edit:

There is another, less nice way to start a process on reboot, using cron:

<pre><code>@reboot user-to-run-under /usr/bin/java -jar /path/to/application.jar
</code></pre>

This works, but gives you no nice start/stop interface for your application. You can still simply <code>kill</code> it anyway...

blocks|key|1864569|text|下面是在Linux中将Java应用程序作为系统服务安装的最简单方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1864570|假设您使用的是systemd+(现在的任何现代发行版都是这样)：|offset|length|style|CODE|1864571|首先，在/etc/systemd/system中创建一个名为javaservice.service的服务文件，其中包含以下内容：|1864572|[Unit]
Description=Java+Service

[Service]
User=nobody
#+The+configuration+file+application.properties+should+be+here:
WorkingDirectory=/data+
ExecStart=/usr/bin/java+-Xmx256m+-jar+application.jar+--server.port=8081
SuccessExitStatus=143
TimeoutStopSec=10
Restart=on-failure
RestartSec=5

[Install]
WantedBy=multi-user.target|code-block|syntax|javascript|1864573|其次，将新的服务文件通知systemd：|1864574|systemctl+daemon-reload|1864575|并启用它，这样它就可以在启动时运行：|1864576|systemctl+enable+javaservice.service|1864577|最后，您可以使用以下命令来启动/停止新服务：|1864578|systemctl+start+javaservice
systemctl+stop+javaservice
systemctl+restart+javaservice
systemctl+status+javaservice|1864579|如果您使用的是systemd，这是将Java应用程序设置为系统服务的最无干扰和最干净的方法。|1864580|我特别喜欢这个解决方案的一点是，您不需要安装和配置任何其他软件。附带的systemd为您完成了所有工作，您的服务的行为与任何其他系统服务一样。我现在已经在产品中使用了一段时间，在各种发行版上，它就像你所期望的那样工作。|1864581|另一个优点是，通过使用/usr/bin/java，您可以轻松地添加jvm参数，如-Xmx256m。|1864582|还要阅读官方Spring+Boot文档中的systemd部分：http://docs.spring.io/spring-boot/docs/current/reference/html/deployment-install.html|1864583|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.spring.io/spring-boot/docs/current/reference/html/deployment-install.html^0|0|7|7|0|4|J|U|J|0|0|C|7|0|0|0|0|0|0|7|7|0|Z|7|0|B|D|X|3|14|8|0|L|7|V|2D|0|0^^$0|@$1|2|3|4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1H|8|@$D|1I|E|1J|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1K|8|@$D|1L|E|1M|F|G]|$D|1N|E|1O|F|G]]|9|@]|A|$]]|$1|J|3|K|5|L|7|1P|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|1Q|8|@$D|1R|E|1S|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|L|7|1T|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|1U|8|@]|9|@]|A|$]]|$1|U|3|V|5|L|7|1V|8|@]|9|@]|A|$M|N]]|$1|W|3|X|5|6|7|1W|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|L|7|1X|8|@]|9|@]|A|$M|N]]|$1|10|3|11|5|6|7|1Y|8|@$D|1Z|E|20|F|G]]|9|@]|A|$]]|$1|12|3|13|5|6|7|21|8|@$D|22|E|23|F|G]]|9|@]|A|$]]|$1|14|3|15|5|6|7|24|8|@$D|25|E|26|F|G]|$D|27|E|28|F|G]|$D|29|E|2A|F|G]]|9|@]|A|$]]|$1|16|3|17|5|6|7|2B|8|@$D|2C|E|2D|F|G]]|9|@$D|2E|E|2F|1|2G]]|A|$]]|$1|18|3|-4|5|6|7|2H|8|@]|9|@]|A|$]]]|19|$1A|$5|1B|1C|1D|A|$1E|1F]]]]

What follows is the easiest way to install a Java application as system service in Linux.
Let's assume you are using <code>systemd</code> (which any modern distro nowadays does):
Firstly, create a service file in <code>/etc/systemd/system</code> named e.g. <code>javaservice.service</code> with this content:
<pre><code>[Unit]
Description=Java Service

[Service]
User=nobody
# The configuration file application.properties should be here:
WorkingDirectory=/data 
ExecStart=/usr/bin/java -Xmx256m -jar application.jar --server.port=8081
SuccessExitStatus=143
TimeoutStopSec=10
Restart=on-failure
RestartSec=5

[Install]
WantedBy=multi-user.target
</code></pre>
Secondly, notify <code>systemd</code> of the new service file:
<pre><code>systemctl daemon-reload
</code></pre>
and enable it, so it runs on boot:
<pre><code>systemctl enable javaservice.service
</code></pre>
Eventually, you can use the following commands to start/stop your new service:
<pre><code>systemctl start javaservice
systemctl stop javaservice
systemctl restart javaservice
systemctl status javaservice
</code></pre>
Provided you are using <code>systemd</code>, this is the most non-intrusive and clean way to set up a Java application as system-service.
What I like especially about this solution is the fact that you don't need to install and configure any other software. The shipped <code>systemd</code> does all the work for you, and your service behaves like any other system service. I use it in production for a while now, on various distros, and it just works as you would expect.
Another plus is that, by using <code>/usr/bin/java</code>, you can easily add <code>jvm</code> paramters such as <code>-Xmx256m</code>.
Also read the <code>systemd</code> part in the official Spring Boot documentation:
<a href="http://docs.spring.io/spring-boot/docs/current/reference/html/deployment-install.html" rel="nofollow noreferrer">http://docs.spring.io/spring-boot/docs/current/reference/html/deployment-install.html</a>

blocks|key|1864600|text|我刚刚开始自己做这件事，所以下面就是我到目前为止关于CentOS+init.d服务控制器脚本的内容。到目前为止，它工作得很好，但我不是leet+Bash黑客，所以我相信还有改进的空间，所以欢迎您考虑改进它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1864601|首先，我为每个服务提供了一个简短的配置脚本/data/svcmgmt/conf/my-spring-boot-api.sh，用于设置环境变量。|offset|length|style|CODE|1864602|#!/bin/bash
export+JAVA_HOME=/opt/jdk1.8.0_05/jre
export+APP_HOME=/data/apps/my-spring-boot-api
export+APP_NAME=my-spring-boot-api
export+APP_PORT=40001|code-block|syntax|javascript|1864603|我使用的是CentOS，因此为了确保我的服务在服务器重新启动后启动，我在/etc/init.d/my-spring-boot-api中有一个服务控制脚本|1864604|#!/bin/bash
#+description:+my-spring-boot-api+start+stop+restart
#+processname:+my-spring-boot-api
#+chkconfig:+234+20+80

.+/data/svcmgmt/conf/my-spring-boot-api.sh

/data/svcmgmt/bin/spring-boot-service.sh+$1

exit+0|1864605|如您所见，它调用初始配置脚本来设置环境变量，然后调用我用来重新启动所有Spring+Boot服务的共享脚本。这个共享脚本就是它的精华所在：|1864606|#!/bin/bash

echo+"Service+[$APP_NAME]+-+[$1]"

echo+"++++JAVA_HOME=$JAVA_HOME"
echo+"++++APP_HOME=$APP_HOME"
echo+"++++APP_NAME=$APP_NAME"
echo+"++++APP_PORT=$APP_PORT"

function+start+{
++++if+pkill+-0+-f+$APP_NAME.jar+>+/dev/null+2>&1
++++then
++++++++echo+"Service+[$APP_NAME]+is+already+running.+Ignoring+startup+request."
++++++++exit+1
++++fi
++++echo+"Starting+application..."
++++nohup+$JAVA_HOME/bin/java+-jar+$APP_HOME/$APP_NAME.jar+\
++++++++--spring.config.location=file:$APP_HOME/config/+++\
++++++++<+/dev/null+>+$APP_HOME/logs/app.log+2>&1+&
}

function+stop+{
++++if+!+pkill+-0+-f+$APP_NAME.jar+>+/dev/null+2>&1
++++then
++++++++echo+"Service+[$APP_NAME]+is+not+running.+Ignoring+shutdown+request."
++++++++exit+1
++++fi

++++#+First,+we+will+try+to+trigger+a+controlled+shutdown+using+
++++#+spring-boot-actuator
++++curl+-X+POST+http://localhost:$APP_PORT/shutdown+<+/dev/null+>+/dev/null+2>&1

++++#+Wait+until+the+server+process+has+shut+down
++++attempts=0
++++while+pkill+-0+-f+$APP_NAME.jar+>+/dev/null+2>&1
++++do
++++++++attempts=$[$attempts+%2B+1]
++++++++if+[+$attempts+-gt+5+]
++++++++then
++++++++++++#+We+have+waited+too+long.+Kill+it.
++++++++++++pkill+-f+$APP_NAME.jar+>+/dev/null+2>&1
++++++++fi
++++++++sleep+1s
++++done
}

case+$1+in
start)
++++start
;;
stop)
++++stop
;;
restart)
++++stop
++++start
;;
esac
exit+0|1864607|停止时，它将尝试使用Spring+Boot+Actuator执行受控关闭。但是，如果Actuator没有配置或者未能在合理的时间范围内关闭(我给它5秒，这真的有点短)，进程将被终止。|1864608|此外，该脚本还假设运行应用程序的java进程将是进程详细信息文本中唯一包含"my-spring-boot-api.jar“的进程。在我的环境中，这是一个安全的假设，意味着我不需要跟踪PID。|1864609|entityMap^0|0|L|14|0|0|10|U|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|14|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|15|8|@$D|16|E|17|F|G]]|9|@]|A|$]]|$1|O|3|P|5|J|7|18|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|19|8|@]|9|@]|A|$]]|$1|S|3|T|5|J|7|1A|8|@]|9|@]|A|$K|L]]|$1|U|3|V|5|6|7|1B|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|Z|$]]

I just got around to doing this myself, so the following is where I am so far in terms of a CentOS init.d service controller script. It's working quite nicely so far, but I'm no leet Bash hacker, so I'm sure there's room for improvement, so thoughts on improving it are welcome.

First of all, I have a short config script <code>/data/svcmgmt/conf/my-spring-boot-api.sh</code> for each service, which sets up environment variables.

<pre><code>#!/bin/bash
export JAVA_HOME=/opt/jdk1.8.0_05/jre
export APP_HOME=/data/apps/my-spring-boot-api
export APP_NAME=my-spring-boot-api
export APP_PORT=40001
</code></pre>

I'm using CentOS, so to ensure that my services are started after a server restart, I have a service control script in <code>/etc/init.d/my-spring-boot-api</code>:

<pre><code>#!/bin/bash
# description: my-spring-boot-api start stop restart
# processname: my-spring-boot-api
# chkconfig: 234 20 80

. /data/svcmgmt/conf/my-spring-boot-api.sh

/data/svcmgmt/bin/spring-boot-service.sh $1

exit 0
</code></pre>

As you can see, that calls the initial config script to set up environment variables and then calls a shared script which I use for restarting all of my Spring Boot services. That shared script is where the meat of it all can be found:

<pre><code>#!/bin/bash

echo "Service [$APP_NAME] - [$1]"

echo " JAVA_HOME=$JAVA_HOME"
echo " APP_HOME=$APP_HOME"
echo " APP_NAME=$APP_NAME"
echo " APP_PORT=$APP_PORT"

function start {
 if pkill -0 -f $APP_NAME.jar &gt; /dev/null 2&gt;&amp;1
 then
 echo "Service [$APP_NAME] is already running. Ignoring startup request."
 exit 1
 fi
 echo "Starting application..."
 nohup $JAVA_HOME/bin/java -jar $APP_HOME/$APP_NAME.jar \
 --spring.config.location=file:$APP_HOME/config/ \
 &lt; /dev/null &gt; $APP_HOME/logs/app.log 2&gt;&amp;1 &amp;
}

function stop {
 if ! pkill -0 -f $APP_NAME.jar &gt; /dev/null 2&gt;&amp;1
 then
 echo "Service [$APP_NAME] is not running. Ignoring shutdown request."
 exit 1
 fi

 # First, we will try to trigger a controlled shutdown using 
 # spring-boot-actuator
 curl -X POST http://localhost:$APP_PORT/shutdown &lt; /dev/null &gt; /dev/null 2&gt;&amp;1

 # Wait until the server process has shut down
 attempts=0
 while pkill -0 -f $APP_NAME.jar &gt; /dev/null 2&gt;&amp;1
 do
 attempts=$[$attempts + 1]
 if [ $attempts -gt 5 ]
 then
 # We have waited too long. Kill it.
 pkill -f $APP_NAME.jar &gt; /dev/null 2&gt;&amp;1
 fi
 sleep 1s
 done
}

case $1 in
start)
 start
;;
stop)
 stop
;;
restart)
 stop
 start
;;
esac
exit 0
</code></pre>

When stopping, it will attempt to use Spring Boot Actuator to perform a controlled shutdown. However, in case Actuator is not configured or fails to shut down within a reasonable time frame (I give it 5 seconds, which is a bit short really), the process will be killed.

Also, the script makes the assumption that the java process running the appllication will be the only one with "my-spring-boot-api.jar" in the text of the process details. This is a safe assumption in my environment and means that I don't need to keep track of PIDs.

blocks|key|2078185|text|我的CentOS6/+RHEL的SysVInit脚本(还不理想)。此脚本需要ApplicationPidListener。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2078186|/etc/init.d/app的来源|style|CODE|2078187|#!/bin/sh
#
#+app+Spring+Boot+Application+
#
#+chkconfig:+++345+20+80
#+description:+App+Service
#+++++++++++

###+BEGIN+INIT+INFO
#+Provides:+App
#+Required-Start:+$local_fs+$network
#+Required-Stop:+$local_fs+$network
#+Default-Start:+3+4+5+
#+Default-Stop:+0+1+2+6
#+Short-Description:+Application
#+Description:++++++
###+END+INIT+INFO

#+Source+function+library.
.+/etc/rc.d/init.d/functions

#+Source+networking+configuration.
.+/etc/sysconfig/network

exec="/usr/bin/java"
prog="app"
app_home=/home/$prog/
user=$prog

[+-e+/etc/sysconfig/$prog+]+&&+.+/etc/sysconfig/$prog

lockfile=/var/lock/subsys/$prog++++
pid=$app_home/$prog.pid

start()+{

++++[+-x+$exec+]+%7C%7C+exit+5
++++[+-f+$config+]+%7C%7C+exit+6
++++#+Check+that+networking+is+up.
++++[+"$NETWORKING"+=+"no"+]+&&+exit+1
++++echo+-n+$"Starting+$prog:+"
++++cd+$app_home
++++daemon+--check+$prog+--pidfile+$pid+--user+$user+$exec+$app_args+&
++++retval=$?
++++echo
++++[+$retval+-eq+0+]+&&+touch+$lockfile
++++return+$retval
}

stop()+{
++++echo+-n+$"Stopping+$prog:+"
++++killproc+-p+$pid+$prog
++++retval=$?
++++[+$retval+-eq+0+]+&&+rm+-f+$lockfile
++++return+$retval
}

restart()+{
++++stop
++++start
}

reload()+{
++++restart
}

force_reload()+{
++++restart
}

rh_status()+{
++++status+-p+$pid+$prog
}

rh_status_q()+{
++++rh_status+>/dev/null+2>&1
}

case+"$1"+in
++++start)
++++++++rh_status_q+&&+exit+0
++++++++$1
++++++++;;
++++stop)
++++++++rh_status_q+%7C%7C+exit+0
++++++++$1
++++++++;;
++++restart)
++++++++$1
++++++++;;
++++reload)
++++++++rh_status_q+%7C%7C+exit+7
++++++++$1
++++++++;;
++++force-reload)
++++++++force_reload
++++++++;;
++++status)
++++++++rh_status
++++++++;;
++++condrestart%7Ctry-restart)
++++++++rh_status_q+%7C%7C+exit+0
++++++++restart
++++++++;;
++++*)
++++++++echo+$"Usage:+$0+{start%7Cstop%7Cstatus%7Crestart%7Ccondrestart%7Ctry-restart%7Creload%7Cforce-reload}"
++++++++exit+2
esac
exit+$?|code-block|syntax|javascript|2078188|示例配置文件/etc/sysconfig/app|2078189|exec=/opt/jdk1.8.0_05/jre/bin/java

user=myuser
app_home=/home/mysuer/

app_args="-jar+app.jar"

pid=$app_home/app.pid|2078190|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/actuate/system/ApplicationPidListener.htm^0|12|M|0|0|0|F|0|0|6|I|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|D|3|E|5|6|7|12|8|@$A|13|B|14|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|15|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|16|8|@$A|17|B|18|F|G]]|9|@]|C|$]]|$1|O|3|P|5|J|7|19|8|@]|9|@]|C|$K|L]]|$1|Q|3|-4|5|6|7|1A|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]]]

My SysVInit script for Centos 6 / RHEL (not ideal yet). This script requires <a href="http://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/actuate/system/ApplicationPidListener.htm" rel="nofollow">ApplicationPidListener</a>.

Source of <code>/etc/init.d/app</code>

<pre><code>#!/bin/sh
#
# app Spring Boot Application 
#
# chkconfig: 345 20 80
# description: App Service
# 

### BEGIN INIT INFO
# Provides: App
# Required-Start: $local_fs $network
# Required-Stop: $local_fs $network
# Default-Start: 3 4 5 
# Default-Stop: 0 1 2 6
# Short-Description: Application
# Description: 
### END INIT INFO

# Source function library.
. /etc/rc.d/init.d/functions

# Source networking configuration.
. /etc/sysconfig/network

exec="/usr/bin/java"
prog="app"
app_home=/home/$prog/
user=$prog

[ -e /etc/sysconfig/$prog ] &amp;&amp; . /etc/sysconfig/$prog

lockfile=/var/lock/subsys/$prog 
pid=$app_home/$prog.pid

start() {

 [ -x $exec ] || exit 5
 [ -f $config ] || exit 6
 # Check that networking is up.
 [ "$NETWORKING" = "no" ] &amp;&amp; exit 1
 echo -n $"Starting $prog: "
 cd $app_home
 daemon --check $prog --pidfile $pid --user $user $exec $app_args &amp;
 retval=$?
 echo
 [ $retval -eq 0 ] &amp;&amp; touch $lockfile
 return $retval
}

stop() {
 echo -n $"Stopping $prog: "
 killproc -p $pid $prog
 retval=$?
 [ $retval -eq 0 ] &amp;&amp; rm -f $lockfile
 return $retval
}

restart() {
 stop
 start
}

reload() {
 restart
}

force_reload() {
 restart
}

rh_status() {
 status -p $pid $prog
}

rh_status_q() {
 rh_status &gt;/dev/null 2&gt;&amp;1
}

case "$1" in
 start)
 rh_status_q &amp;&amp; exit 0
 $1
 ;;
 stop)
 rh_status_q || exit 0
 $1
 ;;
 restart)
 $1
 ;;
 reload)
 rh_status_q || exit 7
 $1
 ;;
 force-reload)
 force_reload
 ;;
 status)
 rh_status
 ;;
 condrestart|try-restart)
 rh_status_q || exit 0
 restart
 ;;
 *)
 echo $"Usage: $0 {start|stop|status|restart|condrestart|try-restart|reload|force-reload}"
 exit 2
esac
exit $?
</code></pre>

Sample config file <code>/etc/sysconfig/app</code>:

<pre><code>exec=/opt/jdk1.8.0_05/jre/bin/java

user=myuser
app_home=/home/mysuer/

app_args="-jar app.jar"

pid=$app_home/app.pid
</code></pre>

blocks|key|2078200|text|我知道这是一个古老的问题，但我想用另一种方式来介绍appassembler-maven-plugin。以下是我的POM中的相关部分，其中包括许多我们发现有用的附加选项值：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2078201|<plugin>
++++<groupId>org.codehaus.mojo</groupId>
++++<artifactId>appassembler-maven-plugin</artifactId>
++++<configuration>
++++++++<generateRepository>true</generateRepository>
++++++++<repositoryLayout>flat</repositoryLayout>
++++++++<useWildcardClassPath>true</useWildcardClassPath>
++++++++<includeConfigurationDirectoryInClasspath>true</includeConfigurationDirectoryInClasspath>
++++++++<configurationDirectory>config</configurationDirectory>
++++++++<target>${project.build.directory}</target>
++++++++<daemons>
++++++++++++<daemon>
++++++++++++++++<id>${installer-target}</id>
++++++++++++++++<mainClass>${mainClass}</mainClass>
++++++++++++++++<commandLineArguments>
++++++++++++++++++++<commandLineArgument>--spring.profiles.active=dev</commandLineArgument>
++++++++++++++++++++<commandLineArgument>--logging.config=${rpmInstallLocation}/config/${installer-target}-logback.xml</commandLineArgument>
++++++++++++++++</commandLineArguments>
++++++++++++++++<platforms>
++++++++++++++++++++<platform>jsw</platform>
++++++++++++++++</platforms>
++++++++++++++++<generatorConfigurations>
++++++++++++++++++++<generatorConfiguration>
++++++++++++++++++++++++<generator>jsw</generator>
++++++++++++++++++++++++<includes>
++++++++++++++++++++++++++++<include>linux-x86-64</include>
++++++++++++++++++++++++</includes>
++++++++++++++++++++++++<configuration>
++++++++++++++++++++++++++++<property>
++++++++++++++++++++++++++++++++<name>wrapper.logfile</name>
++++++++++++++++++++++++++++++++<value>logs/${installer-target}-wrapper.log</value>
++++++++++++++++++++++++++++</property>
++++++++++++++++++++++++++++<property>
++++++++++++++++++++++++++++++++<name>wrapper.logfile.maxsize</name>
++++++++++++++++++++++++++++++++<value>5m</value>
++++++++++++++++++++++++++++</property>
++++++++++++++++++++++++++++<property>
++++++++++++++++++++++++++++++++<name>run.as.user.envvar</name>
++++++++++++++++++++++++++++++++<value>${serviceUser}</value>
++++++++++++++++++++++++++++</property>
++++++++++++++++++++++++++++<property>
++++++++++++++++++++++++++++++++<name>wrapper.on_exit.default</name>
++++++++++++++++++++++++++++++++<value>RESTART</value>
++++++++++++++++++++++++++++</property>
++++++++++++++++++++++++</configuration>
++++++++++++++++++++</generatorConfiguration>
++++++++++++++++</generatorConfigurations>
++++++++++++++++<jvmSettings>
++++++++++++++++++++<initialMemorySize>256M</initialMemorySize>
++++++++++++++++++++<maxMemorySize>1024M</maxMemorySize>
++++++++++++++++++++<extraArguments>
++++++++++++++++++++++++<extraArgument>-server</extraArgument>
++++++++++++++++++++</extraArguments>
++++++++++++++++</jvmSettings>
++++++++++++</daemon>
++++++++</daemons>
++++</configuration>
++++<executions>
++++++++<execution>
++++++++++++<id>generate-jsw-scripts</id>
++++++++++++<phase>package</phase>
++++++++++++<goals>
++++++++++++++++<goal>generate-daemons</goal>
++++++++++++</goals>
++++++++</execution>
++++</executions>
</plugin>|code-block|syntax|javascript|2078202|entityMap|0|LINK|mutability|MUTABLE|url|http://mojo.codehaus.org/appassembler/appassembler-maven-plugin/index.html^0|P|P|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

I know this is an older question, but I wanted to present yet another way which is the <a href="http://mojo.codehaus.org/appassembler/appassembler-maven-plugin/index.html" rel="noreferrer">appassembler-maven-plugin</a>. Here's the relevant part from my POM that includes a lot of additional option values we found useful:

<pre><code>&lt;plugin&gt;
 &lt;groupId&gt;org.codehaus.mojo&lt;/groupId&gt;
 &lt;artifactId&gt;appassembler-maven-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;generateRepository&gt;true&lt;/generateRepository&gt;
 &lt;repositoryLayout&gt;flat&lt;/repositoryLayout&gt;
 &lt;useWildcardClassPath&gt;true&lt;/useWildcardClassPath&gt;
 &lt;includeConfigurationDirectoryInClasspath&gt;true&lt;/includeConfigurationDirectoryInClasspath&gt;
 &lt;configurationDirectory&gt;config&lt;/configurationDirectory&gt;
 &lt;target&gt;${project.build.directory}&lt;/target&gt;
 &lt;daemons&gt;
 &lt;daemon&gt;
 &lt;id&gt;${installer-target}&lt;/id&gt;
 &lt;mainClass&gt;${mainClass}&lt;/mainClass&gt;
 &lt;commandLineArguments&gt;
 &lt;commandLineArgument&gt;--spring.profiles.active=dev&lt;/commandLineArgument&gt;
 &lt;commandLineArgument&gt;--logging.config=${rpmInstallLocation}/config/${installer-target}-logback.xml&lt;/commandLineArgument&gt;
 &lt;/commandLineArguments&gt;
 &lt;platforms&gt;
 &lt;platform&gt;jsw&lt;/platform&gt;
 &lt;/platforms&gt;
 &lt;generatorConfigurations&gt;
 &lt;generatorConfiguration&gt;
 &lt;generator&gt;jsw&lt;/generator&gt;
 &lt;includes&gt;
 &lt;include&gt;linux-x86-64&lt;/include&gt;
 &lt;/includes&gt;
 &lt;configuration&gt;
 &lt;property&gt;
 &lt;name&gt;wrapper.logfile&lt;/name&gt;
 &lt;value&gt;logs/${installer-target}-wrapper.log&lt;/value&gt;
 &lt;/property&gt;
 &lt;property&gt;
 &lt;name&gt;wrapper.logfile.maxsize&lt;/name&gt;
 &lt;value&gt;5m&lt;/value&gt;
 &lt;/property&gt;
 &lt;property&gt;
 &lt;name&gt;run.as.user.envvar&lt;/name&gt;
 &lt;value&gt;${serviceUser}&lt;/value&gt;
 &lt;/property&gt;
 &lt;property&gt;
 &lt;name&gt;wrapper.on_exit.default&lt;/name&gt;
 &lt;value&gt;RESTART&lt;/value&gt;
 &lt;/property&gt;
 &lt;/configuration&gt;
 &lt;/generatorConfiguration&gt;
 &lt;/generatorConfigurations&gt;
 &lt;jvmSettings&gt;
 &lt;initialMemorySize&gt;256M&lt;/initialMemorySize&gt;
 &lt;maxMemorySize&gt;1024M&lt;/maxMemorySize&gt;
 &lt;extraArguments&gt;
 &lt;extraArgument&gt;-server&lt;/extraArgument&gt;
 &lt;/extraArguments&gt;
 &lt;/jvmSettings&gt;
 &lt;/daemon&gt;
 &lt;/daemons&gt;
 &lt;/configuration&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;generate-jsw-scripts&lt;/id&gt;
 &lt;phase&gt;package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;generate-daemons&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
&lt;/plugin&gt;
</code></pre>

blocks|key|1864654|text|如果你想在Spring+Boot+Maven插件1.3.0.M2中使用Spring+Boot+1.2.5，这里有一个解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1864655|<parent>
++++<groupId>org.springframework.boot</groupId>
++++<artifactId>spring-boot-starter-parent</artifactId>
++++<version>1.2.5.RELEASE</version>
</parent>

<build>
++++<plugins>
++++++++<plugin>
++++++++++++<groupId>org.springframework.boot</groupId>
++++++++++++<artifactId>spring-boot-maven-plugin</artifactId>
++++++++++++<version>1.3.0.M2</version>
++++++++++++<configuration>
++++++++++++++++<executable>true</executable>
++++++++++++</configuration>
++++++++</plugin>
++++</plugins>
</build>

<pluginRepositories>
++++<pluginRepository>
++++++++<id>spring-libs-milestones</id>
++++++++<url>http://repo.spring.io/libs-milestone</url>
++++</pluginRepository>+
</pluginRepositories>|code-block|syntax|javascript|1864656|然后编译为make：mvn+clean+package，创建一个符号链接ln+-s+/.../myapp.jar+/etc/init.d/myapp，将其设置为可执行的chmod+%2Bx+/etc/init.d/myapp，然后启动service+myapp+start+(使用Ubuntu+Server)|offset|length|style|CODE|1864657|entityMap^0|0|0|A|H|10|12|2C|Q|37|J|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]|$I|V|J|W|K|L]|$I|X|J|Y|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|N|$]]

If you want to use Spring Boot 1.2.5 with Spring Boot Maven Plugin 1.3.0.M2, here's out solution:

<pre><code>&lt;parent&gt;
 &lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
 &lt;artifactId&gt;spring-boot-starter-parent&lt;/artifactId&gt;
 &lt;version&gt;1.2.5.RELEASE&lt;/version&gt;
&lt;/parent&gt;

&lt;build&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
 &lt;artifactId&gt;spring-boot-maven-plugin&lt;/artifactId&gt;
 &lt;version&gt;1.3.0.M2&lt;/version&gt;
 &lt;configuration&gt;
 &lt;executable&gt;true&lt;/executable&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
&lt;/build&gt;

&lt;pluginRepositories&gt;
 &lt;pluginRepository&gt;
 &lt;id&gt;spring-libs-milestones&lt;/id&gt;
 &lt;url&gt;http://repo.spring.io/libs-milestone&lt;/url&gt;
 &lt;/pluginRepository&gt; 
&lt;/pluginRepositories&gt;
</code></pre>

Then compile as ususal: <code>mvn clean package</code>, make a symlink <code>ln -s /.../myapp.jar /etc/init.d/myapp</code>, make it executable <code>chmod +x /etc/init.d/myapp</code> and start it <code>service myapp start</code> (with Ubuntu Server)

blocks|key|1864707|text|下面是一个脚本，它将可执行jar部署为systemd服务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1864708|它为服务和.service文件创建一个用户，并将jar文件放在/var下，并对权限进行一些基本锁定。|1864709|#!/bin/bash

#+Argument:+The+jar+file+to+deploy
APPSRCPATH=$1

#+Argument:+application+name,+no+spaces+please,+used+as+folder+name+under+/var
APPNAME=$2

#+Argument:+the+user+to+use+when+running+the+application,+may+exist,+created+if+not+exists
APPUSER=$3

#+Help+text
USAGE="
Usage:+sudo+$0+<jar-file>+<app-name>+<runtime-user>
If+an+app+with+the+name+<app-name>+already+exist,+it+is+stopped+and+deleted.
If+the+<runtime-user>+does+not+already+exist,+it+is+created.
"

#+Check+that+we+are+root
if+[+!+"root"+=+"$(whoami)"+];+then
++++echo+"Must+be+root.+Please+use+e.g.+sudo"
++++echo+"$USAGE"
++++exit
fi

#+Check+arguments
if+[+"$#"+-ne+3+-o+${#APPSRCPATH}+=+0+-o+${#APPNAME}+=+0+-o+${#APPUSER}+=+0+];+then
++++echo+"Incorrect+number+of+parameters."
++++echo+"$USAGE"
++++exit
fi

if+[+!+-f+$APPSRCPATH+];+then
++++echo+"Can't+find+jar+file+$APPSRCPATH"
++++echo+"$USAGE"
++++exit
fi

#+Infered+values
APPFILENAME=$(basename+$APPSRCPATH)
APPFOLDER=/var/javaapps/$APPNAME
APPDESTPATH=$APPFOLDER/$APPFILENAME

#+Stop+the+service+if+it+already+exist+and+is+running
systemctl+stop+$APPNAME+>/dev/null+2>&1

#+Create+the+app+folder,+deleting+any+previous+content
rm+-fr+$APPFOLDER
mkdir+-p+$APPFOLDER

#+Create+the+user+if+it+does+not+exist
if+id+"$APPUSER"+>/dev/null+2>&1;+then
++++echo+"Using+existing+user+$APPUSER"
else
++++adduser+--disabled-password+--gecos+""+$APPUSER
++++echo+"Created+user+$APPUSER"
fi

#+Place+app+in+app+folder,+setting+owner+and+rights
cp+$APPSRCPATH+$APPDESTPATH
chown+$APPUSER+$APPDESTPATH
chmod+500+$APPDESTPATH
echo+"Added+or+updated+the+$APPDESTPATH+file"

#+Create+the+.service+file+used+by+systemd
echo+"
[Unit]
Description=$APPNAME
After=syslog.target
[Service]
User=$APPUSER
ExecStart=/usr/bin/java+-jar+$APPDESTPATH
SuccessExitStatus=143
[Install]
WantedBy=multi-user.target
"+>+/etc/systemd/system/$APPNAME.service
echo+"Created+the+/etc/systemd/system/$APPNAME.service+file"

#+Reload+the+daemon
systemctl+daemon-reload

#+Start+the+deployed+app
systemctl+start+$APPNAME
systemctl+status+$APPNAME|code-block|syntax|javascript|1864710|示例：|1864711|📷|atomic|offset|length|1864712|​|1864713|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/72e4c60ff8e124e841be1c694219d504.png|imageAlt^0|0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|14|8|@]|9|@$N|15|O|16|1|17]]|A|$]]|$1|P|3|Q|5|6|7|18|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y|Z|-4]]]]

Here is a script that deploys an executable jar as a systemd service.

It creates a user for the service and the .service file, and place the jar file under /var, and makes some basic lock down of privileges.

<pre><code>#!/bin/bash

# Argument: The jar file to deploy
APPSRCPATH=$1

# Argument: application name, no spaces please, used as folder name under /var
APPNAME=$2

# Argument: the user to use when running the application, may exist, created if not exists
APPUSER=$3

# Help text
USAGE="
Usage: sudo $0 &lt;jar-file&gt; &lt;app-name&gt; &lt;runtime-user&gt;
If an app with the name &lt;app-name&gt; already exist, it is stopped and deleted.
If the &lt;runtime-user&gt; does not already exist, it is created.
"

# Check that we are root
if [ ! "root" = "$(whoami)" ]; then
 echo "Must be root. Please use e.g. sudo"
 echo "$USAGE"
 exit
fi

# Check arguments
if [ "$#" -ne 3 -o ${#APPSRCPATH} = 0 -o ${#APPNAME} = 0 -o ${#APPUSER} = 0 ]; then
 echo "Incorrect number of parameters."
 echo "$USAGE"
 exit
fi

if [ ! -f $APPSRCPATH ]; then
 echo "Can't find jar file $APPSRCPATH"
 echo "$USAGE"
 exit
fi

# Infered values
APPFILENAME=$(basename $APPSRCPATH)
APPFOLDER=/var/javaapps/$APPNAME
APPDESTPATH=$APPFOLDER/$APPFILENAME

# Stop the service if it already exist and is running
systemctl stop $APPNAME &gt;/dev/null 2&gt;&amp;1

# Create the app folder, deleting any previous content
rm -fr $APPFOLDER
mkdir -p $APPFOLDER

# Create the user if it does not exist
if id "$APPUSER" &gt;/dev/null 2&gt;&amp;1; then
 echo "Using existing user $APPUSER"
else
 adduser --disabled-password --gecos "" $APPUSER
 echo "Created user $APPUSER"
fi

# Place app in app folder, setting owner and rights
cp $APPSRCPATH $APPDESTPATH
chown $APPUSER $APPDESTPATH
chmod 500 $APPDESTPATH
echo "Added or updated the $APPDESTPATH file"

# Create the .service file used by systemd
echo "
[Unit]
Description=$APPNAME
After=syslog.target
[Service]
User=$APPUSER
ExecStart=/usr/bin/java -jar $APPDESTPATH
SuccessExitStatus=143
[Install]
WantedBy=multi-user.target
" &gt; /etc/systemd/system/$APPNAME.service
echo "Created the /etc/systemd/system/$APPNAME.service file"

# Reload the daemon
systemctl daemon-reload

# Start the deployed app
systemctl start $APPNAME
systemctl status $APPNAME
</code></pre>

Example:
<a href="https://i.stack.imgur.com/N8JXA.png" rel="noreferrer"><img src="https://i.stack.imgur.com/N8JXA.png" alt="enter image description here"></a>

blocks|key|1864800|text|这可以使用Ubuntu中的Systemd服务来完成|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1864801|[Unit]
Description=A+Spring+Boot+application
After=syslog.target

[Service]
User=baeldung
ExecStart=/path/to/your-app.jar+SuccessExitStatus=143

[Install]+
WantedBy=multi-user.target|code-block|syntax|javascript|1864802|您可以通过此链接获得更详细的描述和不同的方法。http://www.baeldung.com/spring-boot-app-as-a-service|offset|length|1864803|entityMap|0|LINK|mutability|MUTABLE|url|http://www.baeldung.com/spring-boot-app-as-a-service^0|0|0|N|1G|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

It can be done using Systemd service in Ubuntu

<pre><code>[Unit]
Description=A Spring Boot application
After=syslog.target

[Service]
User=baeldung
ExecStart=/path/to/your-app.jar SuccessExitStatus=143

[Install] 
WantedBy=multi-user.target
</code></pre>

You can follow this link for more elaborated description and different ways to do so.
<a href="http://www.baeldung.com/spring-boot-app-as-a-service" rel="nofollow noreferrer">http://www.baeldung.com/spring-boot-app-as-a-service</a>

blocks|key|1864870|text|我最终为WAR/JAR布局做了systemd服务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1864871|我称java为-jar，因为它更灵活。我也试着把ExecStart=spring-mvc.war放进去，但即使是可执行的，我也得到了'Exec+format+error‘|1864872|无论如何，这些天来，systemd出现在所有发行版上，并提供了一个很好的解决方案来重定向日志(当您的服务甚至不启动log4j文件位置将为空时，syserr非常重要:)+)。|1864873|cat+/etc/systemd/system/spring-mvc.service+
[Unit]
Description=Spring+MVC+Java+Service

[Service]
User=spring-mvc
#+The+configuration+file+application.properties+should+be+here:
WorkingDirectory=/usr/local/spring-mvc


#+Run+ExecStartPre+with+root-permissions
PermissionsStartOnly=true

ExecStartPre=-/bin/mkdir+-p+/var/log/spring-mvc


ExecStartPre=/bin/chown+-R+spring-mvc:syslog+/var/log/spring-mvc
ExecStartPre=/bin/chmod+-R+775+/var/log/spring-mvc



#https://www.freedesktop.org/software/systemd/man/systemd.service.html#ExecStart=
ExecStart=/usr/bin/java+\
++++++++-Dlog4j.configurationFile=log4j2-spring.xml+\
++++++++-DLog4jContextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector+\
++++++++-Dspring.profiles.active=dev+\
++++++++-Denvironment-type=dev+\
++++++++-XX:%2BUseConcMarkSweepGC+\
++++++++-XX:CMSInitiatingOccupancyFraction=80+\
++++++++-XX:NewSize=756m+\
++++++++-XX:MetaspaceSize=256m+\
++++++++-Dsun.net.inetaddr.ttl=5+\
++++++++-Xloggc:/var/log/spring-mvc/gc.log+\
++++++++-verbose:gc+\
++++++++-verbosegc+\
++++++++-XX:%2BDisableExplicitGC+\
++++++++-XX:%2BPrintGCDetails+\
++++++++-XX:%2BPrintGCDateStamps+\
++++++++-XX:%2BPreserveFramePointer+\
++++++++-XX:%2BStartAttachListener+\
++++++++-Xms1024m+\
++++++++-Xmx1024m+\
++++++++-XX:%2BHeapDumpOnOutOfMemoryError+\
++++++++-jar+spring-mvc.war

SuccessExitStatus=143
StandardOutput=journal
StandardError=journal


KillSignal=SIGINT
TimeoutStopSec=20
Restart=always
RestartSec=5
StartLimitInterval=0
StartLimitBurst=10

LimitNOFILE=500000
LimitNPROC=500000

#https://www.freedesktop.org/software/systemd/man/systemd.exec.html#LimitCPU=
#LimitCPU=,+LimitFSIZE=,+LimitDATA=,+LimitSTACK=,+LimitCORE=,+LimitRSS=,+LimitNOFILE=,+LimitAS=,+LimitNPROC=,+LimitMEMLOCK=,+LimitLOCKS=,+LimitSIGPENDING=,+LimitMSGQUEUE=,+LimitNICE=,+LimitRTPRIO=,+LimitRTTIME=¶

SyslogIdentifier=spring-mvc

[Install]
WantedBy=multi-user.target


#+https://www.freedesktop.org/software/systemd/man/journalctl.html
#check+logs+---+journalctl+-u+spring-mvc+-f+-o+cat|code-block|syntax|javascript|1864874|rsyslog+-将系统日志输入从应用程序重定向到特定文件夹/文件|1864875|cat+/etc/rsyslog.d/30-spring-mvc.conf+
if+$programname+==+'spring-mvc'+then+/var/log/spring-mvc/spring-mvc.log
&+stop|1864876|logrotate|1864877|cat+/etc/logrotate.d/spring-mvc.conf+
/var/log/spring-mvc/spring-mvc.log
{
++++daily
++++rotate+30
++++maxage+30
++++copytruncate
++++missingok
++++notifempty
++++compress
++++dateext
++++dateformat+_%25Y-%25m-%25d_%25H-%25M
++++delaycompress
++++create+644+spring-mvc+syslog
++++su+spring-mvc+syslog
}|1864878|logrotate+gc|1864879|cat+/etc/logrotate.d/spring-mvc-gc.conf+
/var/log/spring-mvc/gc.log
{
++++daily
++++rotate+30
++++maxage+30
++++copytruncate
++++missingok
++++notifempty
++++compress
++++dateext
++++dateformat+_%25Y-%25m-%25d_%25H-%25M
++++delaycompress
++++create+644+spring-mvc+syslog
++++su+spring-mvc+syslog
}|1864880|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|13|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|R|5|H|7|15|8|@]|9|@]|A|$I|J]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|V|5|H|7|17|8|@]|9|@]|A|$I|J]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

I ended up doing systemd service for WAR/JAR layout 

I'm calling java -jar because its more flexible. Tried also putting the ExecStart=spring-mvc.war but even though is executable, I got 'Exec format error'

Anyway these days, systemd is present on all distros, and offers a nice solution to redirect logs(syserr is important when you service doesn't even start log4j file location will be empty :) ).

<pre><code>cat /etc/systemd/system/spring-mvc.service 
[Unit]
Description=Spring MVC Java Service

[Service]
User=spring-mvc
# The configuration file application.properties should be here:
WorkingDirectory=/usr/local/spring-mvc


# Run ExecStartPre with root-permissions
PermissionsStartOnly=true

ExecStartPre=-/bin/mkdir -p /var/log/spring-mvc


ExecStartPre=/bin/chown -R spring-mvc:syslog /var/log/spring-mvc
ExecStartPre=/bin/chmod -R 775 /var/log/spring-mvc



#https://www.freedesktop.org/software/systemd/man/systemd.service.html#ExecStart=
ExecStart=/usr/bin/java \
 -Dlog4j.configurationFile=log4j2-spring.xml \
 -DLog4jContextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector \
 -Dspring.profiles.active=dev \
 -Denvironment-type=dev \
 -XX:+UseConcMarkSweepGC \
 -XX:CMSInitiatingOccupancyFraction=80 \
 -XX:NewSize=756m \
 -XX:MetaspaceSize=256m \
 -Dsun.net.inetaddr.ttl=5 \
 -Xloggc:/var/log/spring-mvc/gc.log \
 -verbose:gc \
 -verbosegc \
 -XX:+DisableExplicitGC \
 -XX:+PrintGCDetails \
 -XX:+PrintGCDateStamps \
 -XX:+PreserveFramePointer \
 -XX:+StartAttachListener \
 -Xms1024m \
 -Xmx1024m \
 -XX:+HeapDumpOnOutOfMemoryError \
 -jar spring-mvc.war

SuccessExitStatus=143
StandardOutput=journal
StandardError=journal


KillSignal=SIGINT
TimeoutStopSec=20
Restart=always
RestartSec=5
StartLimitInterval=0
StartLimitBurst=10

LimitNOFILE=500000
LimitNPROC=500000

#https://www.freedesktop.org/software/systemd/man/systemd.exec.html#LimitCPU=
#LimitCPU=, LimitFSIZE=, LimitDATA=, LimitSTACK=, LimitCORE=, LimitRSS=, LimitNOFILE=, LimitAS=, LimitNPROC=, LimitMEMLOCK=, LimitLOCKS=, LimitSIGPENDING=, LimitMSGQUEUE=, LimitNICE=, LimitRTPRIO=, LimitRTTIME=¶

SyslogIdentifier=spring-mvc

[Install]
WantedBy=multi-user.target


# https://www.freedesktop.org/software/systemd/man/journalctl.html
#check logs --- journalctl -u spring-mvc -f -o cat
</code></pre>

rsyslog - redirect syslog input from app to specific folder/file

<pre><code>cat /etc/rsyslog.d/30-spring-mvc.conf 
if $programname == 'spring-mvc' then /var/log/spring-mvc/spring-mvc.log
&amp; stop
</code></pre>

logrotate

<pre><code>cat /etc/logrotate.d/spring-mvc.conf 
/var/log/spring-mvc/spring-mvc.log
{
 daily
 rotate 30
 maxage 30
 copytruncate
 missingok
 notifempty
 compress
 dateext
 dateformat _%Y-%m-%d_%H-%M
 delaycompress
 create 644 spring-mvc syslog
 su spring-mvc syslog
}
</code></pre>

logrotate gc

<pre><code>cat /etc/logrotate.d/spring-mvc-gc.conf 
/var/log/spring-mvc/gc.log
{
 daily
 rotate 30
 maxage 30
 copytruncate
 missingok
 notifempty
 compress
 dateext
 dateformat _%Y-%m-%d_%H-%M
 delaycompress
 create 644 spring-mvc syslog
 su spring-mvc syslog
}
</code></pre>

blocks|key|2078526|text|对于SpringBoot+2.4.4，除了@ismael提供的说明外|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2078527|我在maven+pom.xml中设置了以下内容，以使其成为可执行的jar|2078528|<build>
++++<plugins>
++++++++<plugin>
++++++++++++<groupId>org.springframework.boot</groupId>
++++++++++++<artifactId>spring-boot-maven-plugin</artifactId>+++++++++++++++
++++++++++++<configuration>
++++++++++++++++<executable>true</executable>
++++++++++++</configuration>
++++++++++++<executions>
++++++++++++++++<execution>
++++++++++++++++++++<goals>
++++++++++++++++++++++++<goal>repackage</goal>
++++++++++++++++++++</goals>
++++++++++++++++</execution>
++++++++++++</executions>
++++++++</plugin>
++++</plugins>
</build>|code-block|syntax|javascript|2078529|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/58099599/7955174^0|L|7|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

For SpringBoot 2.4.4, in addition to instructions by
<a href="https://stackoverflow.com/a/58099599/7955174">@ismael</a>
I had the following in my maven pom.xml to make it an executable jar
<pre><code>&lt;build&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
 &lt;artifactId&gt;spring-boot-maven-plugin&lt;/artifactId&gt; 
 &lt;configuration&gt;
 &lt;executable&gt;true&lt;/executable&gt;
 &lt;/configuration&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;goals&gt;
 &lt;goal&gt;repackage&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
&lt;/build&gt;
</code></pre>

How to configure nicely Spring Boot application packaged as executable jar as a Service in the Linux system? Is this recommended approach, or should I convert this app to war and install it into Tomcat?
Currently, I can run Spring boot application from the <code>screen</code> session, which is nice but requires manual start after a server reboot.
What I'm looking for is general advice/direction or sample <code>init.d</code> the script, if my approach with executable jar is proper.

Spring Boot application as a Service

Spring Boot

服务器

CentOS

Ubuntu

Linux

Java

如何在Linux系统中配置打包为可执行jar即服务的Spring Boot应用程序？这是推荐的方法，还是应该将此应用程序转换为war并将其安装到Tomcat中？目前，我可以从screen会话运行Spring boot应用程序，这很好，但需要在服务器重新启动后手动启动。如果我使用可执行jar的方法是正确的，我正在寻找的是...

问Spring Boot应用程序即服务
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Spring Boot应用程序即服务EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Spring Boot应用程序即服务
EN