@(jboss)
CentOs 安装配置Jboss
安装JDK
#vi /etc/profile
export JAVA_HOME=/usr/java/jdk1.7.0_05 export CLASSPATH=$JAVA_HOME/lib/dt.jar:$JAVA_HOME/lib/tools.jar:$JAVA_HOME/jre/lib/rt.jar export PATH=$PATH:$JAVA_HOME/bin
# source /etc/profile
BOSS安装
安装
# tar -zxvf /opt/jboss.tar.gz
环境配置
# vi /etc/profile
export JBOSS_HOME=/usr/jboss/jboss-as-7.1.1.Final export PATH=$PATH:$JBOSS_HOME/bin
# source /etc/profile
配置
- 日志文件设置
若需要修改JBoss默认的log4j设置,可修改JBoss安装目录”server”default”conf下的jboss-log4j.xml文件,在该文件中可以看到,log4j的日志输出在JBoss安装目录”server”default”log下的server.log文件中。对于log4j的设置,读者可以在网上搜索更加详细的信息。 web 服务的端口号的修改
这点在前文中有所提及,即修改JBoss安装目录”server”default”deploy”jboss-web.deployer下的server.xml文件,内容如下:<Connector port="8080" address="${jboss.bind.address}" maxThreads="250" maxHttpHeaderSize="8192" emptySessionPath="true" protocol="HTTP/1.1" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" />
将上面的8080端口修改为你想要的端口即可
启动设置(centOs启动JBoss shell脚本)
#!/bin/sh export JAVA_OPTS="-Xms2048m -Xmx2048m -XX:+UseParallelGC -XX:MaxPermSize=512m -Xss256k -XX:+HeapDumpOnOutOfMemoryError -Djava.rmi.server.hostname=10.39.59.182 -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=1690 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.awt.headless=true" rm -rf /opt/jboss/server/default/work/* rm -rf /opt/jboss/server/default/tmp/* nohup sh /opt/jboss/bin/run.sh -Djboss.http.thread=800 -Djboss.http.acceptCount=600 -Djboss.http.port=80 -c default -b 0.0.0.0 -Dfile.encoding=utf-8 & tail -f nohup.out
各项参数 @JBoss介绍
hostname配置解决在Linux上java.net.InetAddress.getLocalHost取本机ip的时候访问出现拒绝访问地址127.0.1.1的问题配置数据源
/opt/jboss/docs/examples/jca
选择相应数据库JNDI配置模板copy到/opt/jboss/server/defult/deploy/
下eg : mysql
<datasources> <local-tx-datasource> <jndi-name>jdbc/ewechatds</jndi-name> <connection-url>jdbc:mysql://10.39.60.115:3306/ewechat</connection-url> <driver-class>com.mysql.jdbc.Driver</driver-class> <user-name>ewechat</user-name> <password>ewechat#123</password> <min-pool-size>10</min-pool-size> <max-pool-size>50</max-pool-size> <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name> <!-- should only be used on drivers after 3.22.1 with "ping" support <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-class-name> --> <!-- sql to call when connection is created <new-connection-sql>some arbitrary sql</new-connection-sql> --> <!-- sql to call on an existing pooled connection when it is obtained from pool - MySQLValidConnectionChecker is preferred for newer drivers <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql> --> <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) --> <metadata> <type-mapping>mySQL</type-mapping> </metadata> </local-tx-datasource> </datasources>
web.xml
<resource-ref> <res-ref-name>jdbc/butterflyds</res-ref-name> <res-type>javax.sql.DataSource</res-type> <res-auth>Container</res-auth> </resource-ref>
jboss-web.xml
<resource-ref> <res-ref-name>jdbc/butterflyds</res-ref-name> <jndi-name>java:jdbc/butterflyds</jndi-name> </resource-ref>
spring.xml
<bean id="masterDataSourceSpied" class="org.springframework.jndi.JndiObjectFactoryBean"> <property name="jndiName"> <value>jdbc/butterflyds</value> </property> <property name="resourceRef" value="true" /> </bean>