JBoss Port Settings

Source: Internet
Author: User

JBOSS5

[email protected] jbossweb.sar]# LL

Total 4868

-rw-r--r--1 Appman appman 625 Sep context.xml

-rw-r--r--1 Appman appman 1410325 Sep Jasper-jdt.jar

-rw-r--r--1 Appman appman 2640860 Sep Jbossweb.jar

-rw-r--r--1 Appman appman 431060 Sep Jboss-web-service.jar

Drwxr-xr-x 2 Appman appman 4096 Sep jsf-libs

-rw-r--r--1 Appman appman 452458 Sep Jstl.jar

Drwxr-xr-x 2 Appman appman 4096 Sep Meta-inf

-rw-r--r--1 Appman appman 8485 Mar 10:28 server.xml

[Email protected] jbossweb.sar]# pwd

/opt/uums-ula/jboss-eap-5.1/jboss-as/server/default/deploy/jbossweb.sar


[email protected] jbossweb.sar]# cat Server.xml

<Server>


<!--Optional Listener which ensures correct init and shutdown of APR,

and provides information if it is not installed and

<listener classname= "Org.apache.catalina.core.AprLifecycleListener" sslengine= "on"/>

<!--Initialize Jasper prior to WebApps is loaded. Documentation At/docs/jasper-howto.html--

<listener classname= "Org.apache.catalina.core.JasperListener"/>


<service name= "Jboss.web" >


<!--A http/1.1 Connector on port 8080--

<connector protocol= "http/1.1" port= "8080" address= "${jboss.bind.address}"

connectiontimeout= "20000" redirectport= "8443" uriencoding= "UTF-8"/>


<!--Add This option to the connector-avoid problems with

. NET clients that don ' t implement http/1.1 correctly

restricteduseragents= "^.*ms Web Services Client Protocol 1.1.4322.*$"

-


<!--A AJP 1.3 Connector on port 8009--

<connector protocol= "ajp/1.3" port= "8009" address= "${jboss.bind.address}"

redirectport= "8443"/>


<!--SSL/TLS Connector configuration using the admin DEVL guide KeyStore

<connector protocol= "http/1.1" sslenabled= "true"

Port= "8443" address= "${jboss.bind.address}"

Scheme= "https" secure= "true" Clientauth= "false"

Keystorefile= "${jboss.server.home.dir}/conf/chap8.keystore"

keystorepass= "Rmi+ssl" Sslprotocol = "TLS"/>

[Email protected] meta-inf]# pwd

/opt/uums-ula/jboss-eap-5.1/jboss-as/server/default/conf/bindingservice.beans/meta-inf

[email protected] meta-inf]# LL

Total 60

-rw-r--r--1 Appman appman 53910 Sep bindings-jboss-beans.xml

[Email protected] meta-inf]# vim bindings-jboss-beans.xml

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M02/7D/61/wKioL1bnhFPxYKlnAADIpVFG6Ck341.png "style=" float: none; "title=" 1.png "alt=" Wkiol1bnhfpxyklnaadipvfg6ck341.png "/>

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M02/7D/64/wKiom1bng8ijCDYAAADKyQFN-No852.png "style=" float: none; "title=" 2.png "alt=" Wkiom1bng8ijcdyaaadkyqfn-no852.png "/>


After this setting

[email protected] jboss-eap-5.1]# cat startapp.sh

#cd/OPT/JBOSS-EAP-5.1/

#!/bin/bash

Echo ===============================

Name=ula

Id= ' Ps-ef | grep "$NAME" | Grep-v "$" | Grep-v "grep" | awk ' {print $} '

If ["$ID"! = ""]; Then

For ID in $ID

Do

echo "Liao Pu. Shu ㈡.? ″...."

Kill-9 $id

Done

echo "?..? -Hi van called. Shu?? Hao.? PU:??.. "

Sleep 5

Else

echo "?..? -Hi van called:?..? Rudder.? Hao..? ュ.??.. "

Sleep 5

Fi

rm-rf/opt/uums-ula/jboss-eap-5.1/jboss-as/server/default/tmp/*

#cp-F/opt/jenkins/test_newpackage/ula-*.war/opt/uums-ula/jboss-eap-5.1/jboss-as/server/default/deploy

cp/opt/jenkins/test_newpackage/ula-resource-web-*.war/opt/uums-ula/jboss-eap-5.1/jboss-as/server/default/ Deploy/ula-resource-web.war

cp/opt/jenkins/test_newpackage/ula-web-*-snapshot.war/opt/uums-ula/jboss-eap-5.1/jboss-as/server/default/ Deploy/ula-web.war

Nohup./jboss-as/bin/run.sh-debug-b 0.0.0.0-djboss.service.binding.set=ports-02 >/opt/uums-ula/ Jboss-eap-5.1/nohup.out 2>&1 &

Tail-f/opt/uums-ula/jboss-eap-5.1/nohup.out|sed '/started in/q '

echo "?..?.."

Here the ports-02 is set, the port is 8280 or you can directly modify the Server.xml port settings here. However, if this method is not suitable for multi-instance multi-instance scenarios, it is best to start the specified port number in the script again.


JBOSS6 Port

[Email protected] configuration]# pwd

/opt/jboss6/jboss-eap-6.2/standalone/configuration

[email protected] configuration]# LL

Total 168

-rwxr-xr-x 1 root root 711 Mar application-roles.properties

-rwxr-xr-x 1 root root 935 Mar application-users.properties

-rwxr-xr-x 1 root root 1908 Mar 16:52 logging.properties

-rwxr-xr-x 1 root root 669 Mar mgmt-groups.properties

-rwxr-xr-x 1 root root 1112 Mar mgmt-users.properties

-rw-r--r--1 root root 0 Mar standalone

-rwxr-xr-x 1 root root 27314 Mar standalone-full-ha.xml

-rwxr-xr-x 1 root root 21476 Mar standalone-full.xml

-rwxr-xr-x 1 root root 20914 Mar standalone-ha.xml

-rwxr-xr-x 1 root root 17846 Mar standalone-osgi.xml

-rw-r--r--1 root root 23072 Mar 14:27 standalone.xml

-rw-r--r--1 root root 23072 Mar 8 11:50 Standalone.xml.bak

Drwxr-xr-x root root 4096 Mar 16:52 standalone_xml_history

[email protected] configuration]# cat Standalone.xml

<socket-binding-group name= "Standard-sockets" default-interface= "public" port-offset= "${ jboss.socket.binding.port-offset:0} ">

<socket-binding name= "management-native" interface= "Management" port= "${jboss.management.native.port:9999}"/ >

<socket-binding name= "Management-http" interface= "Management" port= "${jboss.management.http.port:9990}"/>

<socket-binding name= "Management-https" interface= "Management" port= "${jboss.management.https.port:9443}"/>

<socket-binding name= "AJP" port= "8009"/>

<socket-binding name= "http" port= "8080"/>

<socket-binding name= "https" port= "8443"/>

<socket-binding name= "Remoting" port= "4447"/>

<socket-binding name= "txn-recovery-environment" port= "4712"/>

<socket-binding name= "Txn-status-manager" port= "4713"/>

<outbound-socket-binding name= "MAIL-SMTP" >

<remote-destination host= "localhost" port= "/>"

</outbound-socket-binding>

</socket-binding-group>


</server>


JBoss Port Settings

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.