linux下jboss的安装配置
分类:多线程

CentOS安装JDK、Maven、Jboss

之前的项目全都在windows系统环境下部署的,这次尝试在Linux系统环境下部署,于是这次我们组织在7台主机上安装了JDK、Maven、Jboss其中一台安装了Mysql,并将局域网配置好,终于大功告成了。下面将安装步骤与大家分享!

系统版本:centos6.332位操作系统

硬件配置:内核Intel(R) Pentium(R) 4 CPU 3.00GHz 内存998.5M

安装环境:使用shell 命令

JDK安装

  1. 首先查看系统是否已安装,若已经安装,则可卸载然后安装目的版本

[html]view plaincopy

  1. rpm-qa|grepjdk

2.假设已安装的版本为java-1.6.0-openjdk-1.6.0.0-1.7.b09.el5,执行以下命令

[html]view plaincopy

  1. rpm-e--nodepsjava-1.6.0-openjdk-1.6.0.0-1.7.b09.el5

卸载后,执行步骤1的命令,验卸载是否已经成功

3.我们的安装包jdk-8u45-linux-i586.rpm,执行以下命令进行安装[html]view plaincopy

  1. rpm-ivhjdk-8u45-linux-i586.rpm

该命令将jdk自行安装到了/usr/java/java1.8.0_45下

4.在执行安装命令的时候,可能会出现没有执行权限的问题,可执行以下命令授权

[html]view plaincopy

  1. chmod+xjdk-8u45-linux-x64.rpm

5.为了统一路径,修改JDK所在文件夹名称

[html]view plaincopy

  1. mv/usr/java/java1.8.0_45/usr/java/jdk1.8

6.执行该命令,打开 profile文件,为JDK配置环境变量

[html]view plaincopy

  1. vi/etc/profile

vi打开文件,打开后默认是命令模式,输入a或i可进入编辑模式,下面提示insert的…在文件最后配置如下变量,编辑完成按ESC键退出编辑,然后输入:wq或者:x保存退出。按照如下进行配置:

图片 1

7.保存退出后,使更改生效

[html]view plaincopy

  1. source/etc/profile

8.检测版本信息,查验配置是否正确

[html]view plaincopy

  1. java-version

如出现一下信息,则说明安装配置成功
图片 2

maven安装

采用免安装的方式,直接将目的文件夹拷贝到目的文件夹,配置环境变量即可。

1.初始文件为apache-maven-3.2.5-bin.tar.gz,先要解压该文件

[html]view plaincopy

  1. tar-zxvfapache-maven-3.2.5-bin.tar.gz

2.将解压后的文件移动到 /usr/local下,并命名为mamen-3.2.5

[html]view plaincopy

  1. mvapache-maven-3.2.5/usr/local/maven-3.2.5

3.编辑profile文件,配置环境变量

[html]view plaincopy

  1. vi/etc/profile

如下编辑:

图片 3
4.使编辑生效

[html]view plaincopy

  1. source/etc/profile

5.检测版本信息,查验配置是否正确

[html]view plaincopy

  1. mvn-v

若出现以下信息,则配置成功

图片 4

Jboss安装

同样是免安装的方式,配置好即可。初始文件为jboss-eap-6.2.zip

1.将JBoss压缩包放到usr/local下.该命令是解压缩.

[html]view plaincopy

  1. unzipjboss-eap-6.2.zip

2.将文件jboss-eap-6.2重命名为jboss6.2 并复制到usr/local/下

[html]view plaincopy

  1. mvjboss-eap-6.2jboss6.2

3.启动jboss

你可以先通过cd /usr/local/jboss6.2/bin进入JBoss的bin目录,然后输入命令./run.sh它会问你要standalone(独立运行模式)启动服务器还是domain(域模式),根据需要选择其提供的相应命令即可.
./standalone.sh 即独立运行模式
./domain.sh 即域模式
在运行命令过程中可能遇到权限不够的提示,可以使用如下命令:

chmod 777 *

意思是为所有文件/文件夹添加读/写/执行权限.

查看控制台输出命令,查看启动是否成功

图片 5

4.添加JBoss用户.有管理型和应用型两种.按照下面的步骤来就行。

在/usr/local/jboss6.2/bin下,执行该命令

[html]view plaincopy

  1. ./add-user.sh

按照提示添加用户即可

图片 6

jboss到此就配置好了。

最后展示两张jboss以domain方式运行时候,内存占用情况:

启动前

图片 7

启动后

图片 8

内存占用貌似有点让人捉急呀,等部署测试一下看是不是要拓展一下内存。

之前的项目全都在windows系统环境下部署的,这次尝试在Linux系统环境下部署,于是这次我们组织在7台主机上安装了...

在centOS上安装MySQL,JDK,Jboss

 

前面我们一直在windows服务器上部署项目,JBoss启动时,系统内存直线上升至95%,当系统上线时,这个状况是顶不住同一时刻上千次的访问的,ear包过大,远程调用等都是亟待解决的问题.从服务器出发,改装兼容性更好的Linux系统.半个下午+半个晚上部署好这些开发环境,主要过程整理如下,方便朋友们一次性安装Linux服务器.

 

 

一、简介

MySQL

在线安装没有什么挑战性,但最简单最直接最快速的达到目的不正是我们所需要的吗?

打开终端(Ubuntu的快捷键Ctrl+Alt+T在这里不适用,可以自定义.但我没找到Run a terminal,有知道的朋友要给我留言哦~).

开始输入命令,共3步.

1. wget

(Linux系统中的wget是一个下载文件的工具,用在命令行下,是World,Wide,Web和get的合称.我们经常要下载一些软件或从远程服务器恢复备份到本地服务器.wget支持HTTP,HTTPS和FTP协议,可以使用HTTP代理.所谓的自动下载是指,wget可以在用户退出系统之后在后台执行.你可以登录系统,启动一个wget下载任务,然后退出系统,wget将在后台执行直到任务完成,不像常使的浏览器下载个东西还得一直看着它.)

这里还有我收藏的一个MySQL的下载地址,很方便.

 

2. rpm -ivh mysql-community-release-el7-5.noarch.rpm

(rpm命令的作用就相当于windows里面的添加/删除程序,但功能更强大,它是Red Hat Package Manager的缩写,被广泛应用于Linux下的安装和删除软件)

 

3 yum install mysql-community-server

(yum命令的全称为 Yellow dog Updater,Modified)是一个在Fedora和RedHat以及SUSE中的Shell前端软件包管理器.基于RPM包管理,能够从指定的服务器自动下载RPM包并且安装,可以自动处理依赖性关系,并且一次安装所有依赖的软体包,yum提供了查找、安装、删除某一个、一组甚至全部软件包的命令.

4. service mysqld restart

(重启MySQL服务)

 

5.mysql -u root

(进入MySQL数据库,这时候是没有密码的,自己可以再设置.设置完密码后进入数据库输入命令:mysql -u root -p,提示输入密码后再输入密码.)

看到类似如下欢迎界面表示MySQL数据库安装成功 :

图片 9

 

在公司做性能测试,最近比较清闲没事所以就索性研究一下tomcat和jboss的性能对比,说做就做,由于tomcat使用的比较熟悉,环境搭建比较成熟,就是jboss这玩意刚刚接触,所以有点生,但是我相信和tomcat应该没多大的区别,这就很自信的开始干起来。

JBoss是一个运行EJB的J2EE应用服务器。它是开放源代码的项目,遵循最新的J2EE规范。从JBoss项目开始至今,它已经从一个EJB容器发展成为一个基于的J2EE的一个web 操作系统(operating system for web),它体现了J2EE规范中最新的技术。无论是学习还是应用,JBoss为我们提供了一个非常优秀的平台。

JDK

 

如果系统自带jdk,我们可以先给它卸载掉.然后安装我们需要的jdk.

1.rpm -qa |grep jdk

(查看系统中已安装的jdk,假设已安装的版本为java-1.6.0-openjdk-1.6.0.0-1.7.b09.el5,执行以下命令)

 

2.rpm-e --nodeps java-1.6.0-openjdk-1.6.0.0-1.7.b09.el5

(卸载完成后,再输入第一个命令查看下,确保已卸载.如果原本就不存在jdk就不用卸载了.直接安装即可.)

 

3.chmod +x jdk-8u45-linux-x64.rpm

(我已从官网上载下来1.8的jdk,并放到了usr下,这个命令是给资源添加执行权限,如果没有这步,下一步会提示权限不够)

 

4.rpm -ivh jdk-8u45-linux-x64.rpm

 

(该命令将jdk安装到了/usr/java下)

 

5.mv /usr/java/java1.8.0_45 /usr/java/jdk1.8

(mv 是重命名,这个也不是必须的,个人习惯.)

 

6.vi /etc/profile

(vi打开文件,打开后默认是命令模式,输入a或i可进入编辑模式,下面提示insert的…在文件最后配置如下变量,编辑完成按ESC键退出编辑,然后输入:wq或者:x保存退出)

图片 10

 

7.java -version

出现如下版本,则说明一切OK.

图片 11

 

 

JBoss是一个管理EJB的容器和服务器,支持EJB 1.1、EJB 2.0和EJB3.0的规范。但JBoss核心服务不包括支持servlet/JSP的WEB容器,一般与Tomcat或Jetty绑定使用。

Jboss

 

这个不分平台,但是Linux比windows对JBoss更兼容.

1.unzip jboss-eap-6.2.zip

在原来的windows服务器上copy过来JBoss压缩包,放到usr/local下.该命令是解压缩.

 

2.mv jboss-eap-6.2 jboss6.2

mv是重命名,将文件jboss-eap-6.2重命名为jboss6.2,这个不是必须的,只是我习惯了.

 

3.启动JBoss服务.

你可以先通过cd /usr/local/jboss6.2/bin进入JBoss的bin目录,然后输入命令./run.sh

包含一个.和一个/,不要把命令输错了.它会问你要启动单实例服务器还是多实例服务器,根据需要选择其提供的相应命令即可.

我这里运行 ./standalone.sh以a single server instance的模式启动JBoss,(另一个是 ./domain.sh)

在运行命令过程中可能遇到权限不够的提示,可以使用如下命令:chmod 777*,意思是为所有文件/文件夹添加读/写/执行权限.

 

JBoss配置完成后在浏览器输入网址localhost:8080看到如下界面表示启动成功了.

图片 12

 

4../add-user.sh

添加JBoss用户.有管理型和应用型两种.按照下面的步骤来就行.

图片 13

 

整理完了,总结一下,工作效率还是一定要提高的.怎么提高,踏踏实实地修炼才是正道.写代码是一方面,调错是一方面,配置和部署各种服务器也是基本功啊!我觉得,企业需要的是放到哪里都能行的干将!

前面我们一直在windows服务器上部署项目,JBoss启动时,系统内存直线上升至95%,当系统上线时,这个状况是顶不住...

首先下载需要准备的安装包:

JBoss具有如下优点:
1、JBoss是免费的,开放源代码J2EE的实现,通过LGPL许可证进行发布.但同时也有闭源的,开源和闭源流入流出的不是同一途径。  
2、 JBoss需要的内存和硬盘空间比较小。  
3、安装便捷:解压后,只需配置一些环境变量即可。  
4、JBoss支持"热部署",部署BEAN时,只拷贝BEAN的JAR文件到部署路径下即可自动加载它,如果有改动,也会自动更新
5、JBoss与Web服务器在同一个Java虚拟机中运行,Servlet调用EJB不经过网络,从而大大提高运行效率,提升安全性能
6、用户可以直接实施J2EE-EAR,而不是以前分别实施EJB- JAR和Web-WAR,非常方便。  
7、Jboss支持集群。

Linux版本:Linux  redhat

2006年,Jboss公司(

JDK版本:jdk1.6.0_27

有关JBoss的详细信息请参阅其主页

Jboss版本:jboss-5.1 

二、系统环境

 

系统平台:RHEL 5.4

JDK安装开始:

Java version:jdk-6u17-linux-i586

1、上传安装包到linux的usr目录下

Jboss version:jboss-5.1.0.GA-jdk6

2。#chmod +x jdk1.6.0_27-linux-i586-rpm.bin给出权限下来让别的用户也能用到。

三、安装准备

3。# ./jdk1.6.0_27-linux-i586-rpm.bin 可以得到一个jdk1.6.0_27-linux-i586-rpm的文件。

下载jboss 5.1和jdk1.6
jboss
jdk1.6

4。# chmod +x jdk1.6.0_27-linux-i586-rpm 对得到文件进行修改权限。

四、解压

5。#rpm -ivh jdk1.6.0_27-linux-i586-rpm  进行安装程序。

#./jdk-6u17-linux-i586.bin //当前目录生成一个jdk1.6.0_17
#mv jdk1.6.0_17 /usr/local/java //把刚生成的目录"jdk1.6.0_17"重命名为"java"
#unzip jboss-5.1.0.GA-jdk6.zip -d /usr/local/ //解压到/usr/local目录下
#mv jboss-5.1.0.GA jboss //重命名为jboss

此时我们应该看到的是安装的协议,我们就一直按回车键来完成安装。

五、配置环境变量

接下来我们就要设置环境变量了。

#vi /etc/profile
//添加如下内容
JAVA_HOME="/usr/local/java"
CLASS_PATH="$JAVA_HOME/lib:$JAVA_HOME/jre/lib"
PATH=".:$PATH:$JAVA_HOME/bin"
export JAVA_HOME CLASS_PATH PATH

6。# vi /etc/profile.d/java.sh   这样作的目的是让所有的用户用到。在编辑java.sh文件的时候,我们进入的是命令模式,所以要进行模式切换,切换到文本模式用i就可以了,然后我们进行编辑,也就是把下面的配置写上去,如下:

六、运行

JAVA_HOME=/usr/java/jdk1.6.0_27

#/usr/local/jboss/bin/run.sh -b 10.0.0.133 //IP写本机地址

CLASSPATH=.:$JAVA_HOME/lib.tools.jar

[[email protected] bin]# ./run.sh -b 10.0.0.133            =========================================================================  JBoss Bootstrap Environment  JBOSS_HOME: /usr/local/jboss  JAVA: /usr/local/jdk/jdk1.6.0_17/bin/java  JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true  CLASSPATH: /usr/local/jboss/bin/run.jar:/usr/local/jdk/jdk1.6.0_17/lib/tools.jar=========================================================================01:57:50,713 INFO  [ServerImpl] Starting JBoss (Microcontainer)...01:57:50,718 INFO  [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)01:57:50,725 INFO  [ServerImpl] Bootstrap URL: null01:57:50,727 INFO  [ServerImpl] Home Dir: /usr/local/jboss01:57:50,742 INFO  [ServerImpl] Home URL: file:/usr/local/jboss/01:57:50,756 INFO  [ServerImpl] Library URL: file:/usr/local/jboss/lib/01:57:50,761 INFO  [ServerImpl] Patch URL: null01:57:50,776 INFO  [ServerImpl] Common Base URL: file:/usr/local/jboss/common/01:57:50,778 INFO  [ServerImpl] Common Library URL: file:/usr/local/jboss/common/lib/01:57:50,806 INFO  [ServerImpl] Server Name: default01:57:50,811 INFO  [ServerImpl] Server Base Dir: /usr/local/jboss/server01:57:50,814 INFO  [ServerImpl] Server Base URL: file:/usr/local/jboss/server/01:57:50,817 INFO  [ServerImpl] Server Config URL: file:/usr/local/jboss/server/default/conf/01:57:50,818 INFO  [ServerImpl] Server Home Dir: /usr/local/jboss/server/default01:57:50,826 INFO  [ServerImpl] Server Home URL: file:/usr/local/jboss/server/default/01:57:50,829 INFO  [ServerImpl] Server Data Dir: /usr/local/jboss/server/default/data01:57:50,832 INFO  [ServerImpl] Server Library URL: file:/usr/local/jboss/server/default/lib/01:57:50,834 INFO  [ServerImpl] Server Log Dir: /usr/local/jboss/server/default/log01:57:50,840 INFO  [ServerImpl] Server Native Dir: /usr/local/jboss/server/default/tmp/native01:57:50,857 INFO  [ServerImpl] Server Temp Dir: /usr/local/jboss/server/default/tmp01:57:50,860 INFO  [ServerImpl] Server Temp Deploy Dir: /usr/local/jboss/server/default/tmp/deploy01:57:52,509 INFO  [ServerImpl] Starting Microcontainer, bootstrapURL=file:/usr/local/jboss/server/default/conf/bootstrap.xml01:57:53,876 INFO  [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]01:57:53,888 INFO  [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]01:57:54,617 INFO  [CopyMechanism] VFS temp dir: /usr/local/jboss/server/default/tmp01:57:54,637 INFO  [ZipEntryContext] VFS force nested jars copy-mode is enabled.01:57:58,247 INFO  [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc.01:57:58,249 INFO  [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_17-b04)01:57:58,259 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc.01:57:58,266 INFO  [ServerInfo] OS-System: Linux 2.6.18-194.el5,i38601:57:58,283 INFO  [ServerInfo] VM arguments: -Dprogram.name=run.sh -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Djava.endorsed.dirs=/usr/local/jboss/lib/endorsed 01:57:58,408 INFO  [JMXKernel] Legacy JMX core initialized01:58:04,694 INFO  [ProfileServiceBootstrap] Loading profile: [email protected][domain=default, server=default, name=default]01:58:10,585 INFO  [WebService] Using RMI server codebase: http://10.0.0.133:8083/01:58:32,816 INFO  [NativeServerConfig] JBoss Web Services - Stack Native Core01:58:32,823 INFO  [NativeServerConfig] 3.1.2.GA01:58:34,296 INFO  [AttributeCallbackItem] Owner callback not implemented.01:58:37,600 INFO  [LogNotificationListener] Adding notification listener for logging mbean "jboss.system:service=Logging,type=Log4jService" to server [email protected][ defaultDomain='jboss' ]01:59:05,890 INFO  [Ejb3DependenciesDeployer] Encountered deployment [email protected]{vfsfile:/usr/local/jboss/server/default/deploy/profileservice-secured.jar/}01:59:05,904 INFO  [Ejb3DependenciesDeployer] Encountered deployment [email protected]{vfsfile:/usr/local/jboss/server/default/deploy/profileservice-secured.jar/}01:59:05,908 INFO  [Ejb3DependenciesDeployer] Encountered deployment [email protected]{vfsfile:/usr/local/jboss/server/default/deploy/profileservice-secured.jar/}01:59:05,927 INFO  [Ejb3DependenciesDeployer] Encountered deployment [email protected]{vfsfile:/usr/local/jboss/server/default/deploy/profileservice-secured.jar/}01:59:13,087 INFO  [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://10.0.0.133/jndi/rmi://10.0.0.133:1090/jmxconnector01:59:15,053 INFO  [MailService] Mail Service bound to java:/Mail01:59:41,437 WARN  [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.01:59:41,508 WARN  [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent01:59:41,673 WARN  [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent01:59:41,797 INFO  [TransactionManagerService] JBossTS Transaction Service (JTA version - tag:JBOSSTS_4_6_1_GA) - JBoss Inc.01:59:41,802 INFO  [TransactionManagerService] Setting up property manager MBean and JMX layer01:59:42,339 INFO  [TransactionManagerService] Initializing recovery manager01:59:43,127 INFO  [TransactionManagerService] Recovery manager configured01:59:43,131 INFO  [TransactionManagerService] Binding TransactionManager JNDI Reference01:59:44,517 INFO  [TransactionManagerService] Starting transaction recovery manager01:59:45,893 INFO  [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/local/jdk/jdk1.6.0_17/jre/lib/i386/server:/usr/local/jdk/jdk1.6.0_17/jre/lib/i386:/usr/local/jdk/jdk1.6.0_17/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib01:59:46,259 INFO  [Http11Protocol] Initializing Coyote HTTP/1.1 on http-10.0.0.133-808001:59:46,266 INFO  [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-10.0.0.133-800901:59:46,375 INFO  [StandardService] Starting service jboss.web01:59:46,389 INFO  [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.3.GA01:59:46,482 INFO  [Catalina] Server startup in 214 ms01:59:46,554 INFO  [TomcatDeployment] deploy, ctxPath=/jbossws01:59:47,951 INFO  [TomcatDeployment] deploy, ctxPath=/web-console01:59:48,849 INFO  [TomcatDeployment] deploy, ctxPath=/invoker01:59:49,346 INFO  [RARDeployment] Required license terms exist, view vfszip:/usr/local/jboss/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml01:59:49,997 INFO  [RARDeployment] Required license terms exist, view vfszip:/usr/local/jboss/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml01:59:50,087 INFO  [RARDeployment] Required license terms exist, view vfszip:/usr/local/jboss/server/default/deploy/jms-ra.rar/META-INF/ra.xml01:59:50,134 INFO  [RARDeployment] Required license terms exist, view vfszip:/usr/local/jboss/server/default/deploy/mail-ra.rar/META-INF/ra.xml01:59:50,221 INFO  [RARDeployment] Required license terms exist, view vfszip:/usr/local/jboss/server/default/deploy/quartz-ra.rar/META-INF/ra.xml01:59:50,456 INFO  [SimpleThreadPool] Job execution threads will use class loader of thread: main01:59:51,545 INFO  [QuartzScheduler] Quartz Scheduler v.1.5.2 created.01:59:51,559 INFO  [RAMJobStore] RAMJobStore initialized.01:59:51,561 INFO  [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'01:59:51,563 INFO  [StdSchedulerFactory] Quartz scheduler version: 1.5.201:59:51,566 INFO  [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.01:59:53,273 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'01:59:55,170 INFO  [ServerPeer] JBoss Messaging 1.4.3.GA server [0] started01:59:55,735 INFO  [ConnectionFactory] Connector bisocket://10.0.0.133:4457 has leasing enabled, lease period 10000 milliseconds01:59:55,739 INFO  [ConnectionFactory] [email protected] started01:59:55,795 INFO  [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=200001:59:55,801 INFO  [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover01:59:55,813 INFO  [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing01:59:55,835 INFO  [ConnectionFactory] Connector bisocket://10.0.0.133:4457 has leasing enabled, lease period 10000 milliseconds01:59:55,845 INFO  [ConnectionFactory] [email protected] started01:59:55,850 INFO  [ConnectionFactory] Connector bisocket://10.0.0.133:4457 has leasing enabled, lease period 10000 milliseconds01:59:55,852 INFO  [ConnectionFactory] [email protected] started01:59:55,881 INFO  [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=200001:59:56,199 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'02:00:09,338 INFO  [JBossASKernel] Created KernelDeployment for: profileservice-secured.jar02:00:09,384 INFO  [JBossASKernel] installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB302:00:09,385 INFO  [JBossASKernel]   with dependencies:02:00:09,388 INFO  [JBossASKernel]   and demands:02:00:09,400 INFO  [JBossASKernel]      jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView02:00:09,402 INFO  [JBossASKernel]      jboss.ejb:service=EJBTimerService02:00:09,404 INFO  [JBossASKernel]   and supplies:02:00:09,406 INFO  [JBossASKernel]      Class:org.jboss.profileservice.spi.ProfileService02:00:09,408 INFO  [JBossASKernel]      jndi:SecureProfileService/remote02:00:09,410 INFO  [JBossASKernel]      jndi:SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService02:00:09,414 INFO  [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3) to KernelDeployment of: profileservice-secured.jar02:00:09,422 INFO  [JBossASKernel] installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB302:00:09,424 INFO  [JBossASKernel]   with dependencies:02:00:09,426 INFO  [JBossASKernel]   and demands:02:00:09,430 INFO  [JBossASKernel]      jboss.ejb:service=EJBTimerService02:00:09,432 INFO  [JBossASKernel]   and supplies:02:00:09,435 INFO  [JBossASKernel]      jndi:SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deploy.DeploymentManager02:00:09,437 INFO  [JBossASKernel]      Class:org.jboss.deployers.spi.management.deploy.DeploymentManager02:00:09,443 INFO  [JBossASKernel]      jndi:SecureDeploymentManager/remote02:00:09,450 INFO  [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3) to KernelDeployment of: profileservice-secured.jar02:00:09,452 INFO  [JBossASKernel] installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB302:00:09,454 INFO  [JBossASKernel]   with dependencies:02:00:09,459 INFO  [JBossASKernel]   and demands:02:00:09,461 INFO  [JBossASKernel]      jboss.ejb:service=EJBTimerService02:00:09,462 INFO  [JBossASKernel]   and supplies:02:00:09,464 INFO  [JBossASKernel]      jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView02:00:09,466 INFO  [JBossASKernel]      Class:org.jboss.deployers.spi.management.ManagementView02:00:09,468 INFO  [JBossASKernel]      jndi:SecureManagementView/remote02:00:09,470 INFO  [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3) to KernelDeployment of: profileservice-secured.jar02:00:09,505 INFO  [EJB3EndpointDeployer] Deploy [email protected]{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}02:00:09,522 INFO  [EJB3EndpointDeployer] Deploy [email protected]{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}02:00:09,523 INFO  [EJB3EndpointDeployer] Deploy [email protected]{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}02:00:10,269 INFO  [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB302:00:10,447 INFO  [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureDeploymentManager ejbName: SecureDeploymentManager02:00:10,817 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:        SecureDeploymentManager/remote - EJB3.x Default Remote Business Interface        SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deploy.DeploymentManager - EJB3.x Remote Business Interface02:00:10,940 INFO  [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB302:00:10,945 INFO  [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureManagementView ejbName: SecureManagementView02:00:11,059 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:        SecureManagementView/remote - EJB3.x Default Remote Business Interface        SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView - EJB3.x Remote Business Interface02:00:11,217 INFO  [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB302:00:11,226 INFO  [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureProfileServiceBean ejbName: SecureProfileService02:00:11,254 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:        SecureProfileService/remote - EJB3.x Default Remote Business Interface        SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService - EJB3.x Remote Business Interface02:00:11,982 INFO  [TomcatDeployment] deploy, ctxPath=/admin-console02:00:12,321 INFO  [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/admin-console'02:00:20,855 INFO  [TomcatDeployment] deploy, ctxPath=/02:00:20,988 INFO  [TomcatDeployment] deploy, ctxPath=/jmx-console02:00:21,378 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-10.0.0.133-808002:00:21,436 INFO  [AjpProtocol] Starting Coyote AJP/1.3 on ajp-10.0.0.133-800902:00:21,475 INFO  [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] Started in 2m:30s:582ms

PATH=$JAVA_HOME/bin:$PATH

七、测试

export JAVA_HOME CLASSPATH PATH

写好了以后,我们要重文本模式转换到命令模式,用esc来切换。然后用:wq保存退出。我们现在是要用来重启机器用

图片 14

#shutdown -r now 命令就可以做到。好了以后用java -version,得到:

web-console

java version "1.6.0_27"

图片 15

那么恭喜你,JDK安装成功了。

八、关闭服务器
#/usr/local/jboss/bin//shutdown.sh -S

 

或找到它的pid号,然后kill掉。

JDK安装成功了,那么就继续安装JBOSS了

[[email protected] bin]# ps -ef|grep jbossroot      3775  3754 26 01:57 pts/0    00:02:38 /usr/local/jdk/jdk1.6.0_17/bin/java -Dprogram.name=run.sh -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Djava.endorsed.dirs=/usr/local/jboss/lib/endorsed -classpath /usr/local/jboss/bin/run.jar:/usr/local/jdk/jdk1.6.0_17/lib/tools.jar org.jboss.Main -b 10.0.0.133root      3919  3464  0 02:07 pts/1    00:00:00 grep jboss[[email protected] bin]# kill -9 3775[[email protected] bin]# 

8。从本地上文件到系统下

JBoss是一个运行EJB的J2EE应用服务器。它是开放源代码的项目,遵循最新的J2EE规范。从JBoss项目开始至今,它已经从一个EJB容器发展...

然后就上传文件到/usr/local/jboss-5.1 .GA.zip下面。

9。要对文件进行解压缩

#unzip jboss-5.1 .GA.zip 当然你也可以解压缩到你指定的目录下面去了。

10。要设置环境变量了

#vi /etc/profile

然后在文件加入下面信息: www.2cto.com

JBOSS_HOME=/usr/local//jboss-5.1-GA

PATH=$PATH:/usr/local/install/thirdparty/arm/2.95.3/bin

export JBOSS_HOME PATH

11。我们修改了文件,那么需要让他立即有效

# source /etc/profile

12。#echo $JBOSS_HOME  用来查看你的环境变量是不是输出了。

13。#cd $JBOSS_HOME/bin  进入到bin目录下用:

./run.sh来启动Jboss.

 

用IP来访问页面,

安装也就基本完成了。

 

不过不要高兴的太早,如果不用本机访问一下试试,这就会让你失望的~~~~不过不要太着急,看看下面的解决方法

 

1。用IP访问不了页面,但启动服务器的话是完全对的,这个问题让我大伤脑经。最后查下来原来是JBOSS启动下需要绑定IP。

解决办法:

#cd $JBOSS_HOME/bin

#mkdir start.sh

#vi start.sh

添加以下内容  ./run.sh -Djboss.bind.address=jboss安装机器的IP&

退出并保存

#./start.sh启动了jboss这样就可以在外网访问了。

 

摘自 gzh0222的专栏

...

本文由10bet手机官网发布于多线程,转载请注明出处:linux下jboss的安装配置

上一篇:没有了 下一篇:没有了
猜你喜欢
热门排行
精彩图文