Jboss EAP6.1 Cluster在Redhat安装过程

最新推荐文章于 2022-07-28 20:24:19 发布
最新推荐文章于 2022-07-28 20:24:19 发布
阅读量150 收藏
点赞数
文章标签： java netty 大数据

第一部分、解压eap
  将解压好的软件分发到要安装的机器上。
  配置服务器要打开8080、9990、9999、8009、8443
  其它如 4447、4712、4713、7600、57600、55200是jboss subsystem使用 ，根据自己情况开。
  建议是集群内部安装Ip地址开，外部按照端口开。

  创建用户、文件系统（非必须），主要是方便管理。
  结构示意图：
A managed domain with one domain controller, three host controllers, and three server groups. Servers are members of server groups, and may be located on any of the host controllers in the domain.A managed domain with one domain controller, three host controllers, and three server groups. Servers are members of server groups, and may be located on any of the host controllers in the domain.
参考文档：
https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.1/html-single/Administration_and_Configuration_Guide/index.html#About_Domain_Controller_Failover

第二部分、domain配置服务器
1、配置domain.xml
   这个文件看懂就行，默认就可以运行，如有特殊需求按需修改。
2、配置host.xml
   a、用 host-master.xml 覆盖原来的host.xml
   host-master.xml（原host.xml默认配置，很全）   
   b、master模版，这个模版只做domain.如果打算还运行server，需要增加下面内容：
  
    jboss.bind.address ( host-master.xml没有这个，需要从host.xml复制 ，如果没有 这个节点只能做manager）

       
          
       
       
            <!-- Used for IIOP sockets in the standard configuration.
                 To secure JacORB you need to setup SSL --&gt
           
           
    
    
    servers 段默认在host-master.xml中也没有 需要从host.xml中复制。其中port-offset参数用来计算server监听的端口。默认以8080开始
   
       
            <!-- Remote JPDA debugging for a specific server
           
             
               
             
          
           --&gt
       
       
            <!-- server-two avoids port conflicts by incrementing the ports in
                 the default socket-group declared in the server-group --&gt
           
       
       
  c、修改，把127地址修改为实际地址。
  d、修改jvms 可选 。根据机器配置与应用情况
  e、修改servers 可选，从控制台看，应该可以从界面增加。
     另外不同host controler下面的的server即使同名也不会冲突。

3、设置用户============
 Realm (admin) : ^C[jboss@hadoop1 bin]$ ./add-user.sh

What type of user do you wish to add?
 a) Management User (mgmt-users.properties)
 b) Application User (application-users.properties)
(a): a

Enter the details of the new user to add.
Realm (ManagementRealm) :
Username : admin
The username 'admin' is easy to guess
Are you sure you want to add user 'admin' yes/no? yes
Password :
Re-enter Password :
About to add user 'admin' for realm 'ManagementRealm'
Is this correct yes/no? yes
Added user 'admin' to file '/home/jboss/jboss-eap-6.1/standalone/configuration/mgmt-users.properties'
Added user 'admin' to file '/home/jboss/jboss-eap-6.1/domain/configuration/mgmt-users.properties'
Is this new user going to be used for one AS process to connect to another AS process?
e.g. for a slave host controller connecting to the master or for a Remoting connection for server to server EJB calls.
yes/no? yes
To represent the user add the following to the server-identities definition
 
[jboss@hadoop1 bin]$ ./add-user.sh

What type of user do you wish to add?
 a) Management User (mgmt-users.properties)
 b) Application User (application-users.properties)
(a): a

Enter the details of the new user to add.
Realm (ManagementRealm) :
Username : slave
User 'slave' already exits, would you like to update the existing user password and roles
Is this correct yes/no? yes
Password :
Re-enter Password :
Updated user 'slave' to file '/home/jboss/jboss-eap-6.1/standalone/configuration/mgmt-users.properties'
Updated user 'slave' to file '/home/jboss/jboss-eap-6.1/domain/configuration/mgmt-users.properties'
Is this new user going to be used for one AS process to connect to another AS process?
e.g. for a slave host controller connecting to the master or for a Remoting connection for server to server EJB calls.
yes/no? yes
To represent the user add the following to the server-identities definition
4、master完整的domain.xml======

注意：profile 段  extensions段  段。


   
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
   
   
       
       
   
   
        <!-- 服务器配置及subsystem集中配置，每个profile是一组完整的配置文件，用来说明个子系统属性。
          jboss eap6 默认带 default ha  full full_ha 四种profile。根据需要修改。一般不用动。 --&gt
       
           
               
                   
                       
                   
                   
                   
                   
               
               
                   
               
               
                   
               
               
                   
               
               
                   
               
               
                   
               
               
                   
               
               
                   
                   
                       
                   
               
           
           
           
               
                   
                        jdbc:h2:mem:test;DB_CLOSE_DELAY=-1
                        h2
                       
                            sa
                            sa
                       
                   
                   
                       
                            org.h2.jdbcx.JdbcDataSource
                       
                   
               
           
           
                false
                true
           
           
               
                   
                       
                   
                   
                   
               
               
                   
                       
                       
                   
               
               
                   
                   
               
               
                   
               
               
               
                   
               
               
               
                   
                       
                       
                   
               
               
               
           
           
               
                   
                       
                   
               
               
                   
                       
                       
                       
                   
                   
                       
                       
                       
                   
                   
                       
                       
                   
               
           
           
           
               
               
               
                   
                       
                       
                       
                       
                   
                   
                       
                       
                       
                       
                   
               
               
           
           
           
               
               
                <!--
           
           
               
           
           
           
               
                   
               
           
           
               
           
           
           
               
           
           
           
           
               
                   
                       
                           
                               
                           
                           
                               
                           
                       
                   
                   
                       
                           
                       
                   
                   
                       
                           
                       
                   
               
           
           
           
               
                   
                       
                   
               
               
               
           
           
               
               
                   
                   
               
           
           
                true
                ${jboss.bind.address:127.0.0.1}
               
               
                   
                       
                   
               
               
           
           
       
       
           
               
                   
                   
                       
                   
               
               
                   
                       
                   
                   
                   
                   
               
               
                   
               
               
                   
               
               
                   
               
               
                   
               
               
                   
               
               
                   
               
               
                   
                   
                       
                       
                   
               
           
           
           
               
                   
                        jdbc:h2:mem:test;DB_CLOSE_DELAY=-1
                        h2
                       
                            sa
                            sa
                       
                   
                   
                       
                            org.h2.jdbcx.JdbcDataSource
                       
                   
               
           
           
                false
                true
           
           
               
                   
                       
                   
                   
                   
               
               
                   
                       
                       
                   
               
               
                   
                   
                   
               
               
                   
                   
               
               
               
                   
               
               
               
                   
                       
                       
                   
               
               
               
           
           
               
                   
                   
                       
                   
               
               
                   
                   
                       
                   
                   
                   
                       
                   
               
               
                   
                   
                       
                       
                   
                    <!--
                      ~  Clustered cache used internally by EJB subsytem for managing the client-mapping(s) of
                      ~                 the socketbinding referenced by the EJB remoting connector
                      --&gt
                   
                   
                       
                       
                   
               
               
                   
                   
                       
                       
                       
                   
                   
                       
                       
                       
                   
                   
                       
                       
                   
               
           
           
           
               
               
               
                   
                       
                       
                       
                       
                   
                   
                       
                       
                       
                       
                   
               
               
           
           
           
               
                   
                   
                   
                   
                   
                   
                   
                   
                   
                   
                   
                   
                   
                   
               
               
                   
                   
                   
                   
                   
                   
                   
                   
                   
                   
                   
                   
                   
                   
               
           
           
               
               
                <!--
           
           
               
           
           
           
               
                   
               
           
           
               
                   
                       
                   
               
           
           
               
           
           
           
               
           
           
           
           
               
                   
                       
                           
                               
                           
                           
                               
                           
                       
                   
                   
                       
                           
                       
                   
                   
                       
                           
                       
                   
               
           
           
           
               
                   
                       
                   
               
               
               
           
           
               
               
               
                   
                   
               
           
           
                true
                ${jboss.bind.address:127.0.0.1}
               
               
                   
                       
                   
               
               
           
           
       
       
           
               
                   
                   
                       
                   
               
               
                   
                       
                   
                   
                   
                   
               
               
                   
               
               
                   
               
               
                   
               
               
                   
               
               
                   
               
               
                   
               
               
                   
                   
                       
                       
                   
               
           
           
           
           
               
                   
                        jdbc:h2:mem:test;DB_CLOSE_DELAY=-1
                        h2
                       
                            sa
                            sa
                       
                   
                   
                       
                            org.h2.jdbcx.JdbcDataSource
                       
                   
               
           
           
                false
                true
           
           
               
                   
                       
                   
                   
                   
               
               
                   
                   
               
               
                   
                       
                       
                   
               
               
                   
                   
               
               
                   
               
               
               
                   
               
               
               
                   
                       
                       
                   
               
               
               
               
           
           
               
                   
                       
                   
               
               
                   
                       
                       
                       
                   
                   
                       
                       
                       
                   
                   
                       
                       
                   
               
           
           
               
                   
               
           
           
               
           
           
           
               
               
               
                   
                       
                       
                       
                       
                   
                   
                       
                       
                       
                       
                   
               
               
           
           
           
               
               
                <!--
           
           
               
           
           
           
           
               
                   
               
           
           
               
                    true
                    NIO
                    2
                   
                       
                       
                           
                       
                       
                   
                   
                       
                       
                           
                           
                       
                       
                   
                   
                       
                           
                           
                           
                           
                       
                   
                   
                       
                       
                            jms.queue.DLQ
                            jms.queue.ExpiryQueue
                            0
                            10485760
                            BLOCK
                            10
                       
                   
                   
                       
                           
                               
                           
                           
                               
                           
                       
                       
                           
                               
                           
                           
                               
                           
                       
                       
                           
                           
                               
                           
                           
                               
                           
                       
                   
               
           
           
               
           
           
           
               
           
           
           
           
               
                   
                       
                           
                               
                           
                           
                               
                           
                       
                   
                   
                       
                           
                       
                   
                   
                       
                           
                       
                   
               
           
           
           
               
                   
                       
                   
               
               
               
           
           
               
               
                   
                   
               
           
           
                true
                ${jboss.bind.address:127.0.0.1}
               
               
                   
                       
                   
               
               
           
           
       
       
           
               
                   
                   
                       
                   
               
               
                   
                       
                   
                   
                   
                   
               
               
                   
               
               
                   
               
               
                   
               
               
                   
               
               
                   
               
               
                   
               
               
                   
                   
                       
                       
                   
               
           
           
           
           
               
                   
                        jdbc:h2:mem:test;DB_CLOSE_DELAY=-1
                        h2
                       
                            sa
                            sa
                       
                   
                   
                       
                            org.h2.jdbcx.JdbcDataSource
                       
                   
               
           
           
                false
                true
           
           
               
                   
                       
                   
                   
                   
               
               
                   
                   
               
               
                   
                       
                       
                   
               
               
                   
                   
                   
               
               
                   
                   
               
               
               
                   
               
               
               
                   
                       
                       
                   
               
               
               
               
           
           
               
                   
                   
                       
                   
               
               
                   
                   
                       
                   
                   
                   
                       
                   
               
               
                   
                   
                       
                       
                   
                    <!--
                      ~  Clustered cache used internally by EJB subsytem for managing the client-mapping(s) of
                      ~                 the socketbinding referenced by the EJB remoting connector
                      --&gt
                   
                   
                       
                       
                   
               
               
                   
                   
                       
                       
                       
                   
                   
                       
                       
                       
                   
                   
                       
                       
                   
               
           
           
               
                   
               
           
           
               
           
           
           
               
               
               
                   
                       
                       
                       
                       
                   
                   
                       
                       
                       
                       
                   
               
               
           
           
           
               
                   
                   
                   
                   
                   
                   
                   
                   
                   
                   
                   
                   
                   
                   
               
               
                   
                   
                   
                   
                   
                   
                   
                   
                   
                   
                   
                   
                   
                   
               
           
           
               
               
                <!--
           
           
               
           
           
           
           
               
                   
               
           
           
               
                    ${jboss.messaging.cluster.password:CHANGE ME!!}
                    true
                    NIO
                    2
                   
                       
                       
                           
                       
                       
                   
                   
                       
                       
                           
                           
                       
                       
                   
                   
                       
                            messaging-group
                            5000
                            netty
                       
                   
                   
                       
                            messaging-group
                            10000
                       
                   
                   
                       
                            jms
                            netty
                           
                       
                   
                   
                       
                           
                           
                           
                           
                       
                   
                   
                       
                       
                            jms.queue.DLQ
                            jms.queue.ExpiryQueue
                            0
                            1000
                            10485760
                            BLOCK
                            10
                       
                   
                   
                       
                           
                               
                           
                           
                               
                           
                       
                       
                           
                               
                           
                           
                               
                           
                            true
                            true
                            1000
                            1.0
                            -1
                       
                       
                           
                           
                               
                           
                           
                               
                           
                       
                   
               
           
           
               
                   
                       
                   
               
           
           
               
           
           
           
               
           
           
           
           
               
                   
                       
                           
                               
                           
                           
                               
                           
                       
                   
                   
                       
                           
                       
                   
                   
                       
                           
                       
                   
               
           
           
           
               
                   
                       
                   
               
               
               
           
           
               
               
               
                   
                   
               
           
           
                true
                ${jboss.bind.address:127.0.0.1}
               
               
                   
                       
                   
               
               
           
           
       
   
    <!--
      ~
      ~          Named interfaces that can be referenced elsewhere in the configuration. The configuration
      ~          for how to associate these logical names with an actual network interface can either
      ~          be specified here or can be declared on a per-host basis in the equivalent element in host.xml.
      ~
      ~          These default configurations require the binding specification to be done in host.xml.
      ~    
      --&gt
   
       
       
       
   
   
       
           
           
           
           
           
           
           
           
               
           
       
       
           
           
           
           
           
           
           
           
           
           
           
           
           
           
               
           
       
       
           
           
           
           
           
           
           
           
           
           
           
           
           
               
           
       
       
           
           
           
           
           
           
           
           
           
           
           
           
           
           
           
           
           
           
           
               
           
       
   
      <!--  定义这个domain中有几个进程组（server group）
     注意 profile属性  --&gt
         
           
               
               
           
           
       
       
           
               
               
           
           
       
   
    
5、master的完整host.xml=============================================
 [jboss@hadoop1 configuration]$ cat host.xml


<!-- A simple configuration for a Host Controller that only acts as the master
 domain controller and does not itself directly control any servers. --&gt

 
  
   
    
     
     
    
   
   
    
     
     
    
    
     
    
   
  
  
   
    
   
   
    
   
  
 

 
  
 

 
  
  
   
  
  
  
   
  
  
   <!-- Used for IIOP sockets in the standard configuration. To secure JacORB
    you need to setup SSL --&gt
    
   
  
 

 
  
   
   
   
    
   
  
 

 
    <!--  定义这个pc服务器（此处指硬件服务器）有几个 server （java进程）
     注意 group属性 ,它引用的就是domain.xml种定义的server-groups
          port-offset 属性，它制定了相对于第一个server监听端口的偏移量。比如server-one是8080
          server-two 就是 8230 （8080+150 ） --&gt
  
   <!-- Remote JPDA debugging for a specific server
    
     --&gt
  
  
   <!-- server-two avoids port conflicts by incrementing the ports in the
    default socket-group declared in the server-group --&gt
   
  
 

 ==========================================
第三部分、slave 配置
1、配置host.xml
   首先给host命名 ，name可以是任何名字
  
2、host controller要访问domain controler，需要一个用户名和密码。用户名就是第一步设置的host name(这里叫slave).
   密码是base64加密的密码，本例是“emFxMXhzdzI9”
               
                    
                    
               
3、修改 指向domain controller(192.168.20.15)
      ${jboss.bind.address:192.168.200.16} 表示如果取不到jboss.bind.address变量值，就以冒号后面做默认值。
4、修改，把127地址修改为实际地址。
5、修改jvms 可选 。根据机器配置与应用情况
6、修改servers 可选，从控制台看，应该可以从界面增加。
   另外不同host controler下面的的server即使同名也不会冲突。
7、删除domain.xml 可选
8、启动
  必须先启动domain controller，否则期待不了
  期待命令domain.sh  (个人感觉很容易误会)                      
host.xml完整版


    <!-- 此处设置的是 host controler 名字，jboss as 7资料说要在domain上建立一个slave用户。只是base64对不同用户密文相同。
       不知道是否必须在在domain建立用户。如前add-usre.sh 对admin和slave产生的secret value="emFxMXhzdzI9"相同 --&gt
   
       
           
               
                     <!-- Replace this with either a base64 password of your own, or use a vault with a vault expression
                     这个值是在domain controller上执行add-user.sh时产生--&gt
                    
                    
               

               
                   
                   
               
           
           
               
                   
                   
               
               
                   
               
           
       
       
           
               
           
       
       
   

   
   
      
   

   
       
          
           
       
       
          
          
       
       
            <!-- Used for IIOP sockets in the standard configuration.
                 To secure JacORB you need to setup SSL --&gt
                
           
       
   

   
          
           
           
             
                 
             
        
       

   
       
       
            <!-- server-two avoids port conflicts by incrementing the ports in
                 the default socket-group declared in the server-group --&gt
           
       
   
  

第四部分、发布应用程序
1、进入domain controller http://192.168.200.15:9990 .
   点右上角“runtime” 进入runtime界面。
   点击左侧树中的manage Deployment .
   选择add 按钮添加war包。
   选择assign 选择服务器组


第五部分、启动日志
domain controller 启动日志
[jboss@hadoop1 bin]$ ./domain.sh
=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /home/jboss/jboss-eap-6.1

  JAVA: java

  JAVA_OPTS: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

=========================================================================

15:02:57,339 INFO  [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1
15:02:57,440 INFO  [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'
[Host Controller] 15:02:57,946 INFO  [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1
[Host Controller] 15:02:58,073 INFO  [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
[Host Controller] 15:02:58,123 INFO  [org.jboss.as] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting
[Host Controller] 15:02:58,585 INFO  [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.7.GA-redhat-1
[Host Controller] 15:02:58,590 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
[Host Controller] 15:02:58,600 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.16.GA-redhat-1
[Host Controller] 15:02:58,609 INFO  [org.jboss.as] (Controller Boot Thread) JBAS010902: Creating http management service using network interface (management) port (9990) securePort (-1)
[Host Controller] 15:02:58,673 INFO  [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 192.168.200.15:9999
[Host Controller] 15:02:59,878 INFO  [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010922: Starting server server-one
15:02:59,930 INFO  [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) JBAS012017: Starting process 'Server:server-one'
[Host Controller] 15:03:01,370 INFO  [org.jboss.as.domain.controller.mgmt] (Remoting "hadoop1:MANAGEMENT" task-4) JBAS010920: Server [Server:server-one] registered using connection [Channel ID 74ed768c (inbound) of Remoting connection 64ed9b24 to /192.168.200.15:57443]
[Host Controller] 15:03:01,440 INFO  [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010922: Starting server server-two
[Host Controller] 15:03:01,467 INFO  [org.jboss.as.host.controller] (server-registration-threads - 1) JBAS010919: Registering server server-one
15:03:01,483 INFO  [org.jboss.as.process.Server:server-two.status] (ProcessController-threads - 3) JBAS012017: Starting process 'Server:server-two'
[Host Controller] 15:03:04,525 INFO  [org.jboss.as.domain] (slave-request-threads - 1) JBAS010918: Registered remote slave host "slave", JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8)
[Host Controller] 15:03:04,541 INFO  [org.jboss.as.domain] (Remoting "hadoop1:MANAGEMENT" task-4) JBAS010925: Unregistered remote slave host "slave"
[Host Controller] 15:03:04,942 INFO  [org.jboss.as.domain.controller.mgmt] (Remoting "hadoop1:MANAGEMENT" task-2) JBAS010920: Server [Server:server-two] registered using connection [Channel ID 08496c34 (inbound) of Remoting connection 147a2aa6 to /192.168.200.15:45572]
[Host Controller] 15:03:04,993 INFO  [org.jboss.as.host.controller] (server-registration-threads - 1) JBAS010919: Registering server server-two
[Host Controller] 15:03:04,998 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://192.168.200.15:9990/management
[Host Controller] 15:03:04,999 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://192.168.200.15:9990
[Host Controller] 15:03:04,999 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) (Host Controller) started in 7485ms - Started 11 of 11 services (0 services are passive or on-demand)
[Host Controller] 15:03:10,757 INFO  [org.jboss.as.domain] (slave-request-threads - 1) JBAS010918: Registered remote slave host "slave", JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8)


host controller启动日志

[jboss@hadoop2 bin]$ ./domain.sh
=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /home/jboss/jboss

  JAVA: java

  JAVA_OPTS: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

=========================================================================

15:03:08,113 INFO  [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1
15:03:08,212 INFO  [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'
[Host Controller] 15:03:08,760 INFO  [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1
[Host Controller] 15:03:08,886 INFO  [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
[Host Controller] 15:03:08,951 INFO  [org.jboss.as] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting
[Host Controller] 15:03:09,397 INFO  [org.xnio] (MSC service thread 1-4) XNIO Version 3.0.7.GA-redhat-1
[Host Controller] 15:03:09,402 INFO  [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
[Host Controller] 15:03:09,420 INFO  [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.2.16.GA-redhat-1
[Host Controller] 15:03:09,492 INFO  [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 192.168.200.16:9999
[Host Controller] 15:03:10,870 INFO  [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010922: Starting server server-three
15:03:10,982 INFO  [org.jboss.as.process.Server:server-three.status] (ProcessController-threads - 3) JBAS012017: Starting process 'Server:server-three'
[Server:server-three] 15:03:12,636 INFO  [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1
[Server:server-three] 15:03:13,109 INFO  [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
[Server:server-three] 15:03:13,315 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting
[Server:server-three] 15:03:13,486 INFO  [org.xnio] (MSC service thread 1-4) XNIO Version 3.0.7.GA-redhat-1
[Server:server-three] 15:03:13,531 INFO  [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
[Server:server-three] 15:03:13,571 INFO  [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.2.16.GA-redhat-1
[Host Controller] 15:03:14,851 INFO  [org.jboss.as.domain.controller.mgmt] (Remoting "hadoop2:MANAGEMENT" task-2) JBAS010920: Server [Server:server-three] registered using connection [Channel ID 561be74d (inbound) of Remoting connection 1e58bdba to /192.168.200.16:42456]
[Host Controller] 15:03:15,026 INFO  [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010922: Starting server server-forth
15:03:15,076 INFO  [org.jboss.as.process.Server:server-forth.status] (ProcessController-threads - 3) JBAS012017: Starting process 'Server:server-forth'
[Host Controller] 15:03:15,106 INFO  [org.jboss.as.host.controller] (server-registration-threads - 1) JBAS010919: Registering server server-three
[Server:server-forth] 15:03:20,297 INFO  [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1
[Server:server-forth] 15:03:23,332 INFO  [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
[Server:server-forth] 15:03:23,733 INFO  [org.jboss.as] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting
[Server:server-forth] 15:03:24,797 INFO  [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.7.GA-redhat-1
[Server:server-forth] 15:03:24,860 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
[Server:server-forth] 15:03:24,963 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.16.GA-redhat-1
[Host Controller] 15:03:28,794 INFO  [org.jboss.as.domain.controller.mgmt] (Remoting "hadoop2:MANAGEMENT" task-2) JBAS010920: Server [Server:server-forth] registered using connection [Channel ID 288d7b04 (inbound) of Remoting connection 5f37f3e1 to /192.168.200.16:44377]
[Host Controller] 15:03:29,736 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) (Host Controller) started in 21451ms - Started 11 of 11 services (0 services are passive or on-demand)
[Host Controller] 15:03:29,880 INFO  [org.jboss.as.host.controller] (server-registration-threads - 1) JBAS010919: Registering server server-forth
[Server:server-forth] 15:03:41,832 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 37) JBAS013171: Activating Security Subsystem
[Server:server-forth] 15:03:41,927 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 33) JBAS015537: Activating WebServices Extension
[Server:server-forth] 15:03:42,031 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 59) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
[Server:server-forth] 15:03:42,048 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 42) JBAS011800: Activating Naming Subsystem
[Server:server-forth] 15:03:42,057 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 60) JBAS016200: Activating ConfigAdmin Subsystem
[Server:server-forth] 15:03:42,061 INFO  [org.jboss.as.jacorb] (ServerService Thread Pool -- 55) JBAS016300: Activating JacORB Subsystem
[Server:server-forth] 15:03:42,129 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 56) JBAS010280: Activating Infinispan subsystem.
[Server:server-forth] 15:03:42,187 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 47) JBAS012605: Activated the following JSF Implementations: [main, 1.2]
[Server:server-forth] 15:03:42,191 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 50) JBAS010260: Activating JGroups subsystem.
[Server:server-forth] 15:03:42,191 INFO  [org.jboss.as.security] (MSC service thread 1-3) JBAS013170: Current PicketBox version=4.0.17.Final-redhat-1
[Server:server-forth] 15:03:42,367 INFO  [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service
[Server:server-forth] 15:03:42,523 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.17.Final-redhat-1)
[Server:server-forth] 15:03:43,548 INFO  [org.jboss.jaxr] (MSC service thread 1-3) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory
[Server:server-forth] 15:03:43,550 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
[Server:server-forth] 15:03:43,746 INFO  [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.1.3.Final-redhat-3
[Server:server-forth] 15:03:43,942 INFO  [org.apache.coyote.http11] (MSC service thread 1-2) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/192.168.200.16:8230
[Server:server-forth] 15:03:43,953 INFO  [org.apache.coyote.ajp] (MSC service thread 1-4) JBWEB003046: Starting Coyote AJP/1.3 on ajp-/192.168.200.16:8159
[Server:server-forth] 15:03:44,138 INFO  [org.apache.coyote.http11] (MSC service thread 1-2) JBWEB003000: Coyote HTTP/1.1 starting on: http-/192.168.200.16:8230
[Server:server-forth] 15:03:44,310 INFO  [org.hornetq.core.server] (MSC service thread 1-4) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=true,backup=false,sharedStore=true,journalDirectory=/home/jboss/jboss/domain/servers/server-forth/data/messagingjournal,bindingsDirectory=/home/jboss/jboss/domain/servers/server-forth/data/messagingbindings,largeMessagesDirectory=/home/jboss/jboss/domain/servers/server-forth/data/messaginglargemessages,pagingDirectory=/home/jboss/jboss/domain/servers/server-forth/data/messagingpaging)
[Server:server-forth] 15:03:44,361 INFO  [org.hornetq.core.server] (MSC service thread 1-4) HQ221006: Waiting to obtain live lock
[Server:server-forth] 15:03:44,675 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 56) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[Server:server-forth] 15:03:44,720 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 56) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[Server:server-forth] 15:03:44,730 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 62) MODCLUSTER000001: Initializing mod_cluster ${project.version}
[Server:server-forth] 15:03:44,779 INFO  [org.hornetq.core.server] (MSC service thread 1-4) HQ221013: Using NIO Journal
[Server:server-forth] 15:03:44,805 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 62) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364
[Server:server-forth] 15:03:45,071 INFO  [org.jboss.as.jacorb] (MSC service thread 1-1) JBAS016330: CORBA ORB Service started
[Server:server-forth] 15:03:45,318 INFO  [org.hornetq.core.server] (MSC service thread 1-4) HQ221034: Waiting to obtain live lock
[Server:server-forth] 15:03:45,319 INFO  [org.hornetq.core.server] (MSC service thread 1-4) HQ221035: Live Server Obtained live lock
[Server:server-forth] 15:03:45,442 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 192.168.200.16:4597
[Server:server-forth] 15:03:45,446 INFO  [org.jboss.as.jacorb] (MSC service thread 1-1) JBAS016328: CORBA Naming Service started
[Server:server-forth] 15:03:45,491 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
[Server:server-forth] 15:03:47,805 INFO  [org.hornetq.core.server] (MSC service thread 1-4) HQ221020: Started Netty Acceptor version 3.6.2.Final-redhat-1-c0d783c 192.168.200.16:5595 for CORE protocol
[Server:server-forth] 15:03:47,869 INFO  [org.hornetq.core.server] (MSC service thread 1-4) HQ221020: Started Netty Acceptor version 3.6.2.Final-redhat-1-c0d783c 192.168.200.16:5605 for CORE protocol
[Server:server-forth] 15:03:47,992 INFO  [org.hornetq.core.server] (MSC service thread 1-4) HQ221007: Server is now live
[Server:server-forth] 15:03:47,993 INFO  [org.hornetq.core.server] (MSC service thread 1-4) HQ221001: HornetQ Server version 2.3.1.Final (Wild Hornet, 123) [90194416-501f-11e3-8db7-bb66fbd27117]
[Server:server-forth] 15:03:48,102 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 62) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
[Server:server-forth] 15:03:48,113 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 63) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
[Server:server-forth] 15:03:48,257 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-3) JBAS010406: Registered connection factory java:/JmsXA
[Server:server-forth] 15:03:48,310 INFO  [org.hornetq.ra] (MSC service thread 1-3) HornetQ resource adaptor started
[Server:server-forth] 15:03:48,310 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatorhornetq-ra
[Server:server-forth] 15:03:48,312 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
[Server:server-forth] 15:03:48,428 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) started in 32000ms - Started 146 of 265 services (118 services are passive or on-demand)

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/15711267/viewspace-776890/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/15711267/viewspace-776890/

congjinzhong3869
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
JBoss 系列四：JBoss7/WildFly中EJB调运示例
Kylin Soong Blog -> ksoong.org
10-05 7167
内容概要 为了有效的利用资源（CPU，内存），我们使用分布式解决方案来满足这一需求，企业JavaBeans（EJB） 3.1通过服务器端的EJB为开发分布式的，事务控制的，安全的，便捷的Java企业应用提供接口。在实际生产环境中我们经常需要EJB调运，JBoss 系列四演示演示两种模式的EJB调运：JBoss服务器之间的EJB调运和Java客户端和JBoss服务器之间的EJB调运，如下图：
Wildfly8 domain模式搭建
caicongyang
08-09 3709
Wildfly8 domain模式搭建
Wildfly部署drools-workbench
kanyun123的博客
07-28 1355
wildfly部署drools-workbench
Jboss 搭建
xxx0028的博客
02-23 521
Jboss是Java EE应用服务器（就像Apache是web服务器一样），专门用来运行Java EE程序的。是一个基于J2EE的开放源代码的应用服务器。 JBoss代码遵循LGPL许可，可以在任何商业应用中免费使用。JBoss是一个管理EJB的容器和服务器，支持EJB 1.1、EJB 2.0和EJB3的规范。但JBoss核心服务不包括支持servlet/JSP的WEB容器，一般与Tomcat或...
通过JMX远程监控JBOSS7.1应用服务器
weixin_34406086的博客
03-25 292
通过JMX可以调试或者监控运行在JVM上的应用程序,使用最多的是JConsole（所有版本JDK都自带JConsole）和VisualVM（可以通过Oracle页面下载，JDK6以上也自带JVisualVM）。 1、在创建JMX监控连接之前，首先需要了解一些JBoss的基本概念： （1）standalone和domain模式： ...
WildFly配置连接GBase 8s
liaosnet的专栏
09-09 435
简介： WildFly，原名 JBoss AS(JBoss Application Server) 或者 JBoss，是一套应用程序服务器，属于开源的企业级 Java 中间件软件，用于实现基于 SOA 架构的 Web 应用和服务。 WildFly 包含一组可独立运行的软件。 GBase 8s（南大通用安全数据库管理系统），是具有完全自主知识产权的数据库产品，产品符合SQL92、ODBC、OLEDB、JDBC、ADO.NET等国际数据库规范和开发接口，参照国际主流数据库产品定义，提供完备的数据存储和数据管理功
jboss-eap-7.2.6-patch
最新发布
09-22
- 备份：在应用补丁前，备份现有的 JBoss EAP 安装，以防万一需要回滚。 - 应用补丁：按照 `patch.xml` 文件中的指示进行操作，这可能包括使用特定的工具（如 `jboss-eap-cli.sh`）或手动替换文件。 - 验证：启动...
jboss EAP部署在Window平台上
09-23
jboss_EAP 部署在Window平台上
jboss-eap-6.4.0.zip
12-26
在 JBoss EAP 6.4 中，以下几个核心知识点值得深入探讨： 1. **模块化架构**：JBoss EAP 6.4 引入了模块化设计，这使得组件之间更加解耦，提升了系统的可维护性和可扩展性。每个服务或库都被封装为一个模块，通过...
dts4+Jboss eap安装.doc
10-25
在IT行业中，构建基于JBoss EAP的DTS SERVER是一项常见的任务，尤其对于企业级应用来说，这样的服务器架构能提供强大的服务管理和数据转换功能。本文将深入讲解如何搭建这样一个系统，主要关注实际操作步骤，跳过...
SpringBoot常见问题
m2_34567的博客
08-25 2866
SpringBoot常见问题 依赖包入失败（有红线） 尝试从spring官网生成新的与原项目相同的依赖关系，导入到IDEA中，问题就没了，可以使用依赖。（网上查阅，可以尝试将依赖删除后，执行maven clean操作之后再将依赖导入，未验证） SpringBoot多环境配置 为了让 SpringBoot 更好的生成配置元数据文件，我们需要添加如下依赖，该依赖只会在编译时调用，所以不用担心会对生产造成影响 <dependency> <groupId>org.springfram
构建一个运行在Azure虚拟机上的MySQL Spring Boot应用程序
cpongo011702
10-22 160
\u0026#xD;关键要点\u0026#xD;\u0026#xD;从GitHub中获取一个简单的Spring Boot Java应用程序。\u0026#xD;\t将应用程序连接到Azure MySQL数据库服务。\u0026#xD;\t在Azure上配置一个运行WildFly的Linux VM。\u0026#xD;\t将示例应用程序部署到WildFly服务器。\u0026#xD;\u0026#x...
JBoss 系列十六：JBoss7/WildFly配置domain模式
Kylin Soong Blog -> ksoong.org
10-13 7041
内容概要 JBoss7/WildFly有两种模式可供选择，即standalone和dimain模式，详细请参照社区文档（链接），本文给出一个简单配置domain模式的步骤。 domain模式配置步骤 本配置涉及到2台机器domain controller（10.66.218.46），host controller（10.66.218.47），本配置修改的文件均为JBOSS_HOME/
使用Spring-Jms监听ActiveMQ时遇到的问题
weixin_33704234的博客
06-04 395
2019独角兽企业重金招聘Python工程师标准>>> ...
OPENWRT-LUCI开发总结-LUCI添加新页面总结
weixin_43883277的博客
08-26 3475
前言 本章节主要从以下四个方面介绍LUCI的启动流程 controller目录的添加 model目录的添加 view目录的添加 官方及参考网址 uhttpd启动流程 1、uhttpd的开机启动脚本为/etc/init.d/uhttpd，配置文件为/etc/config/uhttpd，启动命令如下，其中-h指定web server服务器的根目录是/www/；-x指定CGI URL 路径，默认为...
Redhat中配置Jboss EAP 7
遥远
03-24 882
1. 集群配置 1.1.master server配置 1.1.1.进入 "jboss_home\domain\configuration"，打开host.xml将所有127.0.0.1的地址，换成master server对应的真实IP(否则，无法从远程通过浏览器，访问jboss 管理控制台) 1.1.2. 以domain模式启动master server 1.1.3. 进入...
28、单机wildfly服务器的配置及kie-server+workbench的使用
u013115157的博客
09-09 3331
很多都内容都是见解了别人写的博客，与有雷同，那是正常的。wildfly服务器是基于Jboos的，是一个基于J2EE的开放源代码的应用服务器。 JBoss代码遵循LGPL许可，可以在任何商业应用中免费使用，而不用支付费用。JBoss是一个管理EJB的容器和服务器，支持EJB 1.1、EJB 2.0和EJB3的规范。但JBoss核心服务不包括支持servlet/JSP的WEB容器，一般与Tomcat或...
在wildfly 21中搭建cluster集群
热门推荐
程序那些事
12-29 1万+
wildfly是一个非常强大的工具，我们可以轻松的使用wildfly部署应用程序，更为强大的是，wildfly可以很方便的部署cluster应用。 今天我们通过一个例子来讲解下wildfly如何构建cluster应用。
Windows平台JBOSS EAP6安装与部署详解
3. **安装过程**: - 使用双击或命令行工具 `java-jar jboss-eap-6.0.0-installer.jar` 开始安装。 - 用户需要选择语言环境，确认许可协议，选择安装路径。默认情况下，系统会询问是否创建路径若不存在。 - 创建...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值