jetty在Linux下的配置

jetty官网：http://www.eclipse.org/jetty/

 

具体配置流程如下1, 2:

1. Nginx 添加监听域名和路由端口.

    #当前应用的可用流(可无限添加) 

    upstream pisaTbt0 {

         server  10.221.12.182:8051 weight=1;

         server  10.221.12.182:8052 weight=1;

         keepalive 256;

    }

    upstream pisaTbt1 {

         server  10.221.12.182:8061 weight=1;

         server  10.221.12.182:8062 weight=1;

         keepalive 256;

    }

    #监听域名，此处可配置监听多个端口

    server {

         listen  80;

         server_name  203.195.182.194;

         location ^~ /pisa-tbt/ {

             proxy_pass        http://pisaTbt0;

             proxy_set_header   Host             $host;

             proxy_set_header   X-Real-IP        $remote_addr;

             proxy_set_header   X-Forwarded-For  $proxy_add_x_forwarded_for;

         }

     }

     server {

         listen  8080;

         server_name  203.195.182.194;

         location ^~ /pisa-tbt/ {

             proxy_pass        http://pisaTbt1;

             proxy_set_header   Host             $host:8080;

             proxy_set_header   X-Real-IP        $remote_addr;

             proxy_set_header   X-Forwarded-For  $proxy_add_x_forwarded_for;

         }

     }

 

2. 配置和启动Jetty独立服务

    1) 拷贝davinciDev或WukongDev为自己的应用目录(除了配置文件和日志目录其余全部为软连接, 不用担心版本问题)

    3) 进入{Jetty目录}/standalone/{自己的应用地址}

    4) 修改server.conf, 指定当前服务的两个端口号, 和上方的Nginx流内的端口号对应.

    5) 修改etc/jetty-http.xml中的jetty.host为要启动的host

    6) 执行   server.sh start   启动服务, 启动后将自动在两个端口号内选择一个执行.

    7) 如果需要热重启服务时则执行   server.sh switch   进行切换, 脚本会启动新服务并保证可用的情况下关闭老服务.  Nginx则会自动路由请求到新服务.

 

Jetty独立服务介绍:

 

目录结构:

./data                  存储PID和启动进度信息.

./etc                    应用目录配置, 启动监听配置.(设置项会自动配置, 所以无需更改)，此目录中主要包括jetty-deploy.xml和jetty-started.xml，这两个文件会替代全局配置

./log                    jetty的启动日志(针对当前独立应用)

./server.conf       启动端口号配置

./server.sh           独立服务执行脚本(包括三个命令, server.sh start:启动服务, server.sh stop:关闭服务, server.sh switch:切换服务)

./webapps           应用存放位置

 

jetty-deploy.xml样例

<?xml version="1.0"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">

<!-- =============================================================== -->
<!-- Create the deployment manager -->
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<!-- The deplyment manager handles the lifecycle of deploying web -->
<!-- applications. Apps are provided by instances of the -->
<!-- AppProvider interface. -->
<!-- =============================================================== -->
<Configure id="Server" class="org.eclipse.jetty.server.Server">

<Call name="addBean">
<Arg>
<New id="DeploymentManager" class="org.eclipse.jetty.deploy.DeploymentManager">
<Set name="contexts">
<Ref refid="Contexts" />
</Set>
<Call name="setContextAttribute">
<Arg>org.eclipse.jetty.server.webapp.ContainerIncludeJarPattern</Arg>
<Arg>.*/servlet-api-[^/]*\.jar$</Arg>
</Call>

<!-- Add a customize step to the deployment lifecycle -->
<!-- uncomment and replace DebugBinding with your extended AppLifeCycle.Binding class
<Call name="insertLifeCycleNode">
<Arg>deployed</Arg>
<Arg>starting</Arg>
<Arg>customise</Arg>
</Call>
<Call name="addLifeCycleBinding">
<Arg>
<New class="org.eclipse.jetty.deploy.bindings.DebugBinding">
<Arg>customise</Arg>
</New>
</Arg>
</Call> -->

<Call id="webappprovider" name="addAppProvider">
<Arg>
<New class="org.eclipse.jetty.deploy.providers.WebAppProvider">
<Set name="monitoredDirName"><Property name="jetty.webapps"/></Set>
<Set name="defaultsDescriptor"><Property name="jetty.home" default="." />/etc/webdefault.xml</Set>
<Set name="scanInterval">0</Set>
<Set name="extractWars">true</Set>
<Set name="configurationManager">
<New class="org.eclipse.jetty.deploy.PropertiesConfigurationManager"></New>
</Set>
</New>
</Arg>
</Call>
</New>
</Arg>
</Call>

</Configure>

jetty-started.xml样例

<?xml version="1.0"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">

<!-- =============================================================== -->
<!-- Mixin the Start FileNoticeLifeCycleListener -->
<!-- =============================================================== -->
<Configure id="Server" class="org.eclipse.jetty.server.Server">
<Call name="addLifeCycleListener">
<Arg>
<New class="org.eclipse.jetty.util.component.FileNoticeLifeCycleListener">
<Arg><Property name="jetty.state"/></Arg>
</New>
</Arg>
</Call>
</Configure>

server.sh样例

#!/usr/bin/env bash
#Author Simon
# set profile
source ~/.bash_profile

# set project directory
if [ -z "$PROJECT_HOME" ]
then
START_SH=$0
case "$START_SH" in
/*) PROJECT_HOME=${START_SH%/*} ;;
./*/*/*) PROJECT_HOME=${START_SH%/*} ;;
./*) PROJECT_HOME=. ;;
esac
fi

cd "$PROJECT_HOME"
PROJECT_HOME=$PWD

# set jetty home directory
JETTY_HOME=${PROJECT_HOME%/*/*}
cd "$JETTY_HOME"


# create project log directory
logDir="$PROJECT_HOME/log"
if [ ! -d ${logDir} ]
then
$(mkdir -p ${logDir})
fi

# create project data directory
dataDir="$PROJECT_HOME/data"
if [ ! -d ${dataDir} ]
then
$(mkdir -p ${dataDir})
fi

source "$PROJECT_HOME/server.conf"

# jetty status
if [ -z "$JETTY_STATE" ]
then
JETTY_STATE=$dataDir/jetty.state
fi
rm -f $JETTY_STATE

if [ -z "$JAVA" ]
then
JAVA=$(which java)
fi

# Add jetty properties to Java VM options.
TMPDIR=${TMPDIR:-/tmp}
JAVA_OPTIONS+=("-Djetty.home=$JETTY_HOME" "-Djava.io.tmpdir=$TMPDIR")

# This is how the Jetty server will be started
JETTY_START=$JETTY_HOME/start.jar
[ ! -f "$JETTY_START" ] && JETTY_START=$JETTY_HOME/lib/start.jar

START_INI=$(dirname $JETTY_START)/start.ini
[ -r "$START_INI" ] || START_INI=""

CONFIGS=(
${JETTY_HOME}/etc/jetty-logging.xml
${PROJECT_HOME}/etc/jetty-deploy.xml
${PROJECT_HOME}/etc/jetty-started.xml
)
JETTY_ARGS=(
"jetty.logs"=${PROJECT_HOME}/log
"jetty.webapps"=${PROJECT_HOME

转载于:https://www.cnblogs.com/etiao/p/4173857.html