06 - Installing JBoss EAP 6.3, creating isolated servers, applying/rollback Jboss patches, upgrading/rollback JDK & working with heap memory resizing.
Contents
1. Step-1 is to create
environment for JBoss EAP by installing JDK.
2. Step-2 is to
install Jboss EAP 6.3.0 & create two isolated setup in same host.
3. Step-3 is to add
management user for JMX.
4. Step-4 is to start
JBoss EAP servers in isolated or standalone mode.
5. Step-5 is to change
management port from localhost IP to public IP and drifting JBOSSeap63SERVER2
port by value 100 using port-offset parameter.
6. Step-6 is to access
management JMX console & deploying sample WAR using copy to deployment
location method.
7. Step-7 is to apply
cumulative EAP patch [cp], partial rollback [cp], and full rollback [cp] &
reapply latest patch [cp], applying one-off patch using zip file method.
8. Step-8 is to
connect remote server using jboss-cli on remorting JMX port & applying
patches.
9. Step-9 is to
upgrade java JDK in existing Jboss EAP setup, rollback JDK to earlier using
quickest & easiest method.
10. Step-10 is to work
on Max & Min heap memory size & understanding PermSize.
a. Output#1
b. Output#2
c. Output#3
d. Output#4
1.
Step-1
is to create environment for JBoss EAP by installing JDK.
Reference site - http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
I have downloaded jre-8u91-linux-i586.rpm
& uploaded to my test machin.
[root@serv1 ~]# rpm -ivh
/tmp/jre-8u91-linux-i586.rpm
Preparing... ###########################################
[100%]
1:jre1.8.0_91
########################################### [100%]
Unpacking JAR files...
plugin.jar...
javaws.jar...
deploy.jar...
rt.jar...
jsse.jar...
charsets.jar...
localedata.jar...
jfxrt.jar...
[root@serv1 ~]# which java
/usr/bin/java
[root@serv1 ~]#
[jbossadm@serv1 ~]$ ls -lrth /usr/bin/java
lrwxrwxrwx. 1 root root 22 Jul 9 2016
/usr/bin/java -> /etc/alternatives/java
[jbossadm@serv1 ~]$ ls -lrth /etc/alternatives/java
lrwxrwxrwx. 1 root root 30 Jul
9 2016 /etc/alternatives/java
-> /usr/java/jre1.8.0_91/bin/java
[jbossadm@serv1 ~]$
[jbossadm@serv1 ~]$ java -version
java version "1.8.0_91"
Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
Java HotSpot(TM) Client VM (build 25.91-b14, mixed mode, sharing)
[jbossadm@serv1 ~]$
Where "b" means
"build"
Example -
Java™ SE Development Kit 8, Update 121
(JDK 8u121)
The full version string for this
update release is 1.8.0_121-b13 (where "b" means "build").
The version number is 8u121.
From JRE 1.6.0_03 and later updates on
the JRE 6 codeline
From JRE 1.7.0_10 and later updates on
the JRE 7 codeline
From JRE 1.8.0_25 and later updates on
the JRE 8 codeline
<~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~>
2.
Step-2
is to install Jboss EAP 6.3.0 & create two isolated setup in same host.
Download the base version
jboss-eap-6.3.0.zip from RH or other source site.
[jbossadm@serv1 jboss]$ unzip jboss-eap-6.3.0.zip
[jbossadm@serv1 jboss]$ mv -v jboss-eap-6.3 JBOSSeap63SERVER1
[jbossadm@serv1 jboss]$ cp -prv JBOSSeap63SERVER1 JBOSSeap63SERVER2
<~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~>
3.
Step-3
is to add management user for JMX.
Accept the default user type -
Management User.
Accept the default realm -
ManagementRealm
Enter the username and password of
your choice. I use admin/Admin@123
[jbossadm@serv1 bin]$ /jboss/JBOSSeap63SERVER1/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.
Using realm 'ManagementRealm' as discovered from the existing
property files.
Username : admin
The username 'admin' is easy to guess
Are you sure you want to add user 'admin' yes/no? yes
Password requirements are listed below. To modify these
restrictions edit the add-user.properties configuration file.
- The password must not be
one of the following restricted values {root, admin, administrator}
- The password must contain
at least 8 characters, 1 alphabetic character(s), 1 digit(s), 1
non-alphanumeric symbol(s)
- The password must be
different from the username
Password : *********
Re-enter Password : *********
What groups do you want this user to belong to? (Please enter a
comma separated list, or leave blank for none)[
]:
About to add user 'admin' for realm 'ManagementRealm'
Is this correct yes/no? yes
Added user 'admin' to file
'/jboss/JBOSSeap63SERVER1/standalone/configuration/mgmt-users.properties'
Added user 'admin' to file
'/jboss/JBOSSeap63SERVER1/domain/configuration/mgmt-users.properties'
Added user 'admin' with groups
to file
'/jboss/JBOSSeap63SERVER1/standalone/configuration/mgmt-groups.properties'
Added user 'admin' with groups
to file
'/jboss/JBOSSeap63SERVER1/domain/configuration/mgmt-groups.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? no
[jbossadm@serv1 bin]$
[jbossadm@serv1 bin]$ grep -v "#" /jboss/JBOSSeap63SERVER1/standalone/configuration/mgmt-users.properties
admin=aa2eb421dc2f5ea2c5a8cd0df941d452
[jbossadm@serv1 bin]$ grep -v "#"
/jboss/JBOSSeap63SERVER1/domain/configuration/mgmt-users.properties
admin=aa2eb421dc2f5ea2c5a8cd0df941d452
[jbossadm@serv1 bin]$ grep -v "#" /jboss/JBOSSeap63SERVER1/standalone/configuration/mgmt-groups.properties
admin=
[jbossadm@serv1 bin]$ grep -v "#"
/jboss/JBOSSeap63SERVER1/domain/configuration/mgmt-groups.properties
admin=
[jbossadm@serv1 bin]$
Now, we have to do the same for
JBOSSeap63SERVER2, so instead of adding user using CLI, I do copy properties files to from
JBOSSeap63SERVER1 to JBOSSeap63SERVER2
*as System Admin first & most important
is to backup original files :)
Backup -
[jbossadm@serv1 bin]$ cp -pv
/jboss/JBOSSeap63SERVER2/standalone/configuration/mgmt-users.properties
/jboss/JBOSSeap63SERVER2/standalone/configuration/mgmt-users.properties.BKP.26Mar2017
`/jboss/JBOSSeap63SERVER2/standalone/configuration/mgmt-users.properties'
-> `/jboss/JBOSSeap63SERVER2/standalone/configuration/mgmt-users.properties.BKP.26Mar2017'
[jbossadm@serv1 bin]$
[jbossadm@serv1 bin]$ cp -pv
/jboss/JBOSSeap63SERVER2/domain/configuration/mgmt-users.properties
/jboss/JBOSSeap63SERVER2/domain/configuration/mgmt-users.properties.BKP.26Mar2017
`/jboss/JBOSSeap63SERVER2/domain/configuration/mgmt-users.properties'
-> `/jboss/JBOSSeap63SERVER2/domain/configuration/mgmt-users.properties.BKP.26Mar2017'
[jbossadm@serv1 bin]$
[jbossadm@serv1 bin]$ cp -pv
/jboss/JBOSSeap63SERVER2/standalone/configuration/mgmt-groups.properties
/jboss/JBOSSeap63SERVER2/standalone/configuration/mgmt-groups.properties.BKP.26Mar2017
`/jboss/JBOSSeap63SERVER2/standalone/configuration/mgmt-groups.properties'
-> `/jboss/JBOSSeap63SERVER2/standalone/configuration/mgmt-groups.properties.BKP.26Mar2017'
[jbossadm@serv1 bin]$
[jbossadm@serv1 bin]$ cp -pv
/jboss/JBOSSeap63SERVER2/domain/configuration/mgmt-groups.properties
/jboss/JBOSSeap63SERVER2/domain/configuration/mgmt-groups.properties.BKP.26Mar2017
`/jboss/JBOSSeap63SERVER2/domain/configuration/mgmt-groups.properties'
->
`/jboss/JBOSSeap63SERVER2/domain/configuration/mgmt-groups.properties.BKP.26Mar2017'
[jbossadm@serv1 bin]$
Copying from JBOSSeap63SERVER1 to JBOSSeap63SERVER2-
[jbossadm@serv1 bin]$ cp -pv
/jboss/JBOSSeap63SERVER1/standalone/configuration/mgmt-users.properties
/jboss/JBOSSeap63SERVER2/standalone/configuration/mgmt-users.properties
`/jboss/JBOSSeap63SERVER1/standalone/configuration/mgmt-users.properties'
-> `/jboss/JBOSSeap63SERVER2/standalone/configuration/mgmt-users.properties'
[jbossadm@serv1 bin]$
[jbossadm@serv1 bin]$ cp -pv
/jboss/JBOSSeap63SERVER1/domain/configuration/mgmt-users.properties
/jboss/JBOSSeap63SERVER2/domain/configuration/mgmt-users.properties
`/jboss/JBOSSeap63SERVER1/domain/configuration/mgmt-users.properties'
-> `/jboss/JBOSSeap63SERVER2/domain/configuration/mgmt-users.properties'
[jbossadm@serv1 bin]$
[jbossadm@serv1 bin]$ cp -pv /jboss/JBOSSeap63SERVER1/standalone/configuration/mgmt-groups.properties
/jboss/JBOSSeap63SERVER2/standalone/configuration/mgmt-groups.properties
`/jboss/JBOSSeap63SERVER1/standalone/configuration/mgmt-groups.properties'
->
`/jboss/JBOSSeap63SERVER2/standalone/configuration/mgmt-groups.properties'
[jbossadm@serv1 bin]$
[jbossadm@serv1 bin]$ cp -pv
/jboss/JBOSSeap63SERVER1/domain/configuration/mgmt-groups.properties
/jboss/JBOSSeap63SERVER2/domain/configuration/mgmt-groups.properties
`/jboss/JBOSSeap63SERVER1/domain/configuration/mgmt-groups.properties'
-> `/jboss/JBOSSeap63SERVER2/domain/configuration/mgmt-groups.properties'
[jbossadm@serv1 bin]$
<~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~>
4.
Step-4
is to start JBoss EAP servers in isolated or standalone mode.
[jbossadm@serv1 jboss]$ /jboss/JBOSSeap63SERVER1/bin/standalone.sh -Djboss.node.name=server1 -b
0.0.0.0 &
[1] 1888
[jbossadm@serv1 jboss]$
[jbossadm@serv1 jboss]$ /jboss/JBOSSeap63SERVER2/bin/standalone.sh -Djboss.node.name=server2 -b
0.0.0.0 -Djboss.socket.binding.port-offset=100 &
[2] 2041
[jbossadm@serv1 jboss]$
Please note to add “&” at end
command to run it in background so that you can prompted to next line & you
can do rest of work or logout without impacting running instance. Strongly
recommend also to use “nohup” for better process management.
[jbossadm@serv1 jboss]$ netstat -tunap | grep 1959
(Not all processes could be identified, non-owned process info
will not be shown, you would
have to be root to see it all.)
tcp
0 0 127.0.0.1:9999 0.0.0.0:* LISTEN 1959/java
tcp
0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 1959/java
tcp
0 0 0.0.0.0:4447 0.0.0.0:* LISTEN 1959/java
tcp
0 0 127.0.0.1:9990 0.0.0.0:* LISTEN 1959/java
[jbossadm@serv1 jboss]$ netstat -tunap | grep 2115
(Not all processes could be identified, non-owned process info
will not be shown, you would
have to be root to see it all.)
tcp
0 0 127.0.0.1:10099 0.0.0.0:* LISTEN 2115/java
tcp
0 0 0.0.0.0:8180 0.0.0.0:* LISTEN 2115/java
tcp
0 0 0.0.0.0:4547 0.0.0.0:* LISTEN 2115/java
tcp
0 0 127.0.0.1:10090 0.0.0.0:* LISTEN 2115/java
[jbossadm@serv1 jboss]$
<~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~>
5.
Step-5
is to change management port from localhost IP to public IP and drifting JBOSSeap63SERVER2
port by value 100 using port-offset parameter.
In above example management port is
listened on local host so you cannot access them over intranet/internet
remotely. So need to change mgmt port listen on IP.
[jbossadm@serv1 jboss]$ cp -pv /jboss/JBOSSeap63SERVER1/standalone/configuration/standalone.xml /jboss/JBOSSeap63SERVER1/standalone/configuration/standalone.xml.BKP.26Mar2017
`/jboss/JBOSSeap63SERVER1/standalone/configuration/standalone.xml'
-> `/jboss/JBOSSeap63SERVER1/standalone/configuration/standalone.xml.BKP.26Mar2017'
[jbossadm@serv1 jboss]$
Edit the
`/jboss/JBOSSeap63SERVER1/standalone/configuration/standalone.xml' & change -
<interface
name="management">
<inet-address
value="${jboss.bind.address.management:127.0.0.1}"/>
</interface>
<interface
name="public">
<inet-address
value="${jboss.bind.address:127.0.0.1}"/>
</interface>
to
<interface
name="management">
<inet-address
value="${jboss.bind.address.management:0.0.0.0}"/>
</interface>
<interface
name="public">
<inet-address
value="${jboss.bind.address:0.0.0.0}"/>
</interface>
[jbossadm@serv1 jboss]$ diff
/jboss/JBOSSeap63SERVER1/standalone/configuration/standalone.xml.BKP.26Mar2017
/jboss/JBOSSeap63SERVER1/standalone/configuration/standalone.xml
311c311
<
<inet-address
value="${jboss.bind.address.management:127.0.0.1}"/>
---
> <inet-address
value="${jboss.bind.address.management:0.0.0.0}"/>
314c314
<
<inet-address value="${jboss.bind.address:127.0.0.1}"/>
---
>
<inet-address value="${jboss.bind.address:0.0.0.0}"/>
339c339
< </server>
\ No newline at end of file
---
> </server>
[jbossadm@serv1 jboss]$
[jbossadm@serv1 jboss]$ diff
/jboss/JBOSSeap63SERVER2/standalone/configuration/standalone.xml.BKP.26Mar2017
/jboss/JBOSSeap63SERVER2/standalone/configuration/standalone.xml
311c311
<
<inet-address value="${jboss.bind.address.management:127.0.0.1}"/>
---
>
<inet-address
value="${jboss.bind.address.management:0.0.0.0}"/>
314c314
<
<inet-address value="${jboss.bind.address:127.0.0.1}"/>
---
>
<inet-address value="${jboss.bind.address:0.0.0.0}"/>
339c339
< </server>
\ No newline at end of file
---
> </server>
[jbossadm@serv1 jboss]$
For JBOSSeap63SERVER2 we are using
"-Djboss.socket.binding.port-offset=100" which mean ports will added
with 100 to its original values. Example 8080 will become 8180. So we are going
to make permanent entry in configuration file. Above we had used off-set while
starting JBOSSeap63SERVER2 server. Hence we are going to make configuration
entries so that no need to add offset parameter while starting & ease start
command.
Edit the following –
[jbossadm@serv1 jboss]$ grep offset
/jboss/JBOSSeap63SERVER2/standalone/configuration/standalone.xml
<socket-binding-group
name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
[jbossadm@serv1 jboss]$
To –
[jbossadm@serv1 jboss]$ grep offset
/jboss/JBOSSeap63SERVER2/standalone/configuration/standalone.xml
<socket-binding-group
name="standard-sockets" default-interface="public"
port-offset="${jboss.socket.binding.port-offset:100}">
[jbossadm@serv1 jboss]$
<~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~>
6.
Step-6
is to access management JMX console & deploying sample WAR using copy to
deployment location method.
Accessing the console using
ID/password admin/Admin@123
http://192.168.100.10:9990/console
http://192.168.100.10:10090/console
Download sample Sri Ngen LAB SAMPLE
WAR from - http://ngen-sri.blogspot.in/2017/04/sri-ngen-lab-sample-war-for-cluster.html
[jbossadm@serv1 SriClusterTest]$ cp Sricluster-testEAP6v1.1.war
/jboss/JBOSSeap63SERVER2/standalone/deployments/
[jbossadm@serv1 SriClusterTest]$ 22:50:46,090
INFO [org.jboss.as.server.deployment]
(MSC service thread 1-2) JBAS015876: Starting deployment of
"Sricluster-testEAP6v1.1.war" (runtime-name: "Sricluster-testEAP6v1.1.war")
22:50:46,367 INFO
[org.infinispan.factories.TransactionManagerFactory] (ServerService
Thread Pool -- 99) ISPN000161: Using a batchMode transaction manager
22:50:46,421 INFO
[org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool --
99) ISPN000031: MBeans were successfully registered to the platform MBean
server.
22:50:46,423 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 99)
JBAS010281: Started default-host/Sricluster-testEAP6v1.1 cache from web container
22:50:46,427 INFO
[org.jboss.web] (ServerService Thread Pool -- 95) JBAS018210: Register
web context: /Sricluster-testEAP6v1.1
22:50:46,567 INFO
[org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559:
Deployed "Sricluster-testEAP6v1.1.war" (runtime-name :
"Sricluster-testEAP6v1.1.war")
[jbossadm@serv1 SriClusterTest]$
[jbossadm@serv1 SriClusterTest]$ cp Sricluster-testEAP6v1.1.war
/jboss/JBOSSeap63SERVER1/standalone/deployments/
[jbossadm@serv1 SriClusterTest]$
[jbossadm@serv1 SriClusterTest]$ 22:51:54,604
INFO [org.jboss.as.server.deployment]
(MSC service thread 1-1) JBAS015876: Starting deployment of
"Sricluster-testEAP6v1.1.war" (runtime-name:
"Sricluster-testEAP6v1.1.war")
22:51:54,799 INFO
[org.infinispan.factories.TransactionManagerFactory] (ServerService
Thread Pool -- 68) ISPN000161: Using a batchMode transaction manager
22:51:54,838 INFO
[org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool --
68) ISPN000031: MBeans were successfully registered to the platform MBean
server.
22:51:54,850 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 68)
JBAS010281: Started default-host/Sricluster-testEAP6v1.1 cache from web
container
22:51:54,853 INFO
[org.jboss.web] (ServerService Thread Pool -- 70) JBAS018210: Register
web context: /Sricluster-testEAP6v1.1
22:51:55,074 INFO
[org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559:
Deployed "Sricluster-testEAP6v1.1.war" (runtime-name :
"Sricluster-testEAP6v1.1.war")
[jbossadm@serv1 SriClusterTest]$
Now you can access the application
using the ULRS.
http://192.168.100.10:8080/Sricluster-testEAP6v1.1/sessionTest.jsp
<~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~>
7. Step-7 is to apply
cumulative EAP patch [cp], partial rollback [cp], and full rollback [cp] &
reapply latest patch [cp], applying one-off patch using zip file method.
One-off patches [Asynchronous updates] - always applied at the top of a base
version or a cumulative patch can be empty if no one-off patches have been
applied. One-off patches which are released outside the normal update cycle of
the existing product. These may include security patches, as well as other
one-off patches provided by Red Hat Global Support Services (GSS) to fix
specific issues.
Cumulative patches (cp) [Planned updates] - stack of applied cumulative patches can
be empty if no cumulative patches have been applied. These include cumulative
patches, as well as micro, minor or major upgrades of an existing product.
Cumulative patches include all previously developed asynchronous updates for
that version of the product.
Base version - the base version of this EAP installation always present
Deciding whether a patch is released
as part of a planned update or an asynchronous update depends on the severity
of the issue being fixed. An issue of low impact is typically deferred, and is
resolved in the next cumulative patch or minor release of the affected product.
Issues of moderate or higher impact are typically addressed in order of
importance as an asynchronous update to the affected product, and contain a fix
for only a specific issue.
Cumulative and security patches for
JBoss products are distributed in two forms: zip (for all products) and RPM
(for a subset of products).
A JBoss product installation must
always only be updated using one patch method: either zip or RPM patches.
The stack is ordered by the date at
which the patch has been applied, the most recent applied patch is at the top.
This is a correct representation if a
CP invalidates one-off patches. eg to patch with a new CP, we must first
rollback all the applied one-off patches (whether it's part of the patch
procedure or an user intervention is to be determined).
“jboss-cli” connect on remorting-jmx native
management interface port (default=9999) for standalone & in domain mode first
server=4447, port-offset=xxxx next server.
[jbossadm@serv1 bin]$ sh jboss-cli.sh
You are disconnected at the moment. Type 'connect' to connect to
the server or 'help' for the list of supported commands.
[disconnected /]
[disconnected /] connect
The controller is not available at localhost:9999:
java.net.ConnectException: JBAS012174: Could not connect to
remote://localhost:9999. The connection failed: JBAS012174: Could not connect
to remote://localhost:9999. The connection failed: Connection refused
[disconnected /] exit
There are various methods to check,
best way is to find from server log by looking for following output.
By default,
all JBoss EAP log entries are written to the server.log file. The location of
this file depends on your operating mode.
Standalone
server: EAP_HOME/standalone/log/server.log
Managed
domain: EAP_HOME/domain/servers/SERVER_NAME/log/server.log
During bootup, JBoss EAP logs
information about the Java environment and the startup of each service. This
log can be useful when troubleshooting. By default, all log entries are written
to the server log.
13:39:34,701 INFO
[org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening
on 0.0.0.0:4447
13:39:34,706 INFO
[org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening
on 0.0.0.0:9999
[jbossadm@serv1 bin]$ netstat -tunap
(Not all processes could be identified, non-owned process info
will not be shown, you would
have to be root to see it all.)
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp
0 0 0.0.0.0:9999 0.0.0.0:* LISTEN 1855/java
tcp
0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 1855/java
tcp
0 0 0.0.0.0:22 0.0.0.0:* LISTEN -
tcp
0 0 127.0.0.1:25 0.0.0.0:* LISTEN -
tcp
0 0 0.0.0.0:4447 0.0.0.0:* LISTEN 1855/java
tcp
0 0 0.0.0.0:9990 0.0.0.0:* LISTEN 1855/java
tcp 0 0 192.168.100.10:22 192.168.100.1:1638 ESTABLISHED -
tcp 0 0 192.168.100.10:22 192.168.100.1:1624 ESTABLISHED -
tcp 0 0 :::22 :::* LISTEN -
[jbossadm@serv1 bin]$
[jbossadm@serv1 bin]$ sh jboss-cli.sh
You are disconnected at the moment. Type 'connect' to connect to
the server or 'help' for the list of supported commands.
[disconnected /] connect
[standalone@localhost:9999 /]
Checking current patch details &
patch level by using “patch info” & “patch history”
[standalone@localhost:9999 /] patch info
{
"outcome" :
"success",
"result" : {
"cumulative-patch-id" : "base",
"patches" :
[],
"version" :
"6.3.0.GA",
"addon" :
null,
"layer" :
{"base" : {
"cumulative-patch-id" : "base",
"patches" : []
}}
}
}
[standalone@localhost:9999 /]
[standalone@localhost:9999 /] patch history
{
"outcome" :
"success",
"result" : []
}
[standalone@localhost:9999 /]
Applying latest EAP 6.3
cumulative patch - jboss-eap-6.3.3-patch.zip
[standalone@localhost:9999 /] patch apply /jboss/jboss-eap-6.3.3-patch.zip
{
"outcome" :
"success",
"response-headers" : {
"operation-requires-restart"
: true,
"process-state" : "restart-required"
}
}
[standalone@localhost:9999 /]
[standalone@localhost:9999 /] patch history
{
"outcome" :
"success",
"result" : [
{
"patch-id" : "jboss-eap-6.3.3.CP",
"type"
: "cumulative",
"applied-at" : "4/8/17 1:51 PM"
},
{
"patch-id" : "jboss-eap-6.3.2.CP",
"type"
: "cumulative",
"applied-at" : "4/8/17 1:51 PM"
},
{
"patch-id" : "jboss-eap-6.3.1.CP",
"type"
: "cumulative",
"applied-at" : "4/8/17 1:46 PM"
}
],
"response-headers" : {"process-state" :
"restart-required"}
}
[standalone@localhost:9999 /]
[standalone@localhost:9999 /] patch info
{
"outcome" :
"success",
"result" : {
"cumulative-patch-id" : "jboss-eap-6.3.3.CP",
"patches" :
[],
"version" :
"6.3.3.GA",
"addon" :
null,
"layer" :
{"base" : {
"cumulative-patch-id" :
"layer-base-jboss-eap-6.3.3.CP",
"patches" : []
}}
},
"response-headers" : {"process-state" :
"restart-required"}
}
[standalone@localhost:9999 /]
For the patching service, the patch command leaves the server in a restart-required state, the CLI warns me that a restart is required {"process-state" => "restart-required"}. This message will be cleared after server is restarted.
Restart JBoss using the CLI.
[standalone@localhost:9999 /] shutdown
--restart=true
[standalone@localhost:9999 /] patch info
{
"outcome" :
"success",
"result" : {
"cumulative-patch-id" : "jboss-eap-6.3.3.CP",
"patches" :
[],
"version" :
"6.3.3.GA",
"addon" :
null,
"layer" :
{"base" : {
"cumulative-patch-id" :
"layer-base-jboss-eap-6.3.3.CP",
"patches" : []
}}
}
}
[standalone@localhost:9999 /] patch history
{
"outcome" :
"success",
"result" : [
{
"patch-id" : "jboss-eap-6.3.3.CP",
"type"
: "cumulative",
"applied-at" : "4/8/17 2:13 PM"
},
{
"patch-id" :
"jboss-eap-6.3.2.CP",
"type"
: "cumulative",
"applied-at" : "4/8/17 2:12 PM"
},
{
"patch-id" : "jboss-eap-6.3.1.CP",
"type"
: "cumulative",
"applied-at" : "4/8/17 2:12 PM"
}
]
}
[standalone@localhost:9999 /]
Now rolling back patch one step
downward i.e. jboss-eap-6.3.2.CP
[standalone@localhost:9999 /] patch rollback jboss-eap-6.3.3.CP
Required argument '--reset-configuration' is missing.
[standalone@localhost:9999 /]
*Caution when specifying the value of
the Reset Configuration option:
If set to TRUE, the patch rollback
process will also rollback the JBoss EAP 6 server configuration files to their
pre-patch state. Any changes that were made to the JBoss EAP 6 server
configuration files after the patch was applied will be lost.
If set to FALSE, the server
configuration files will not be rolled back. In this situation, it is possible
that the server will not start after the rollback, as the patch may have
altered configurations, such as namespaces, which may no longer be valid and
have to be fixed manually.
[standalone@localhost:9999 /] patch rollback jboss-eap-6.3.3.CP --reset-configuration=true
14:03:00,052 WARN
[org.jboss.as.patching] (management-handler-thread - 5) JBAS016801:
Cannot invalidate
/jboss/JBOSSeap63SERVER1/modules/system/layers/base/.overlays/layer-base-jboss-eap-6.3.2.CP/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring-jar/resteasy-spring-2.3.8.SP3-redhat-2.jar
{
"outcome" :
"success",
"response-headers" : {
"operation-requires-restart" : true,
"process-state" : "restart-required"
}
}
[standalone@localhost:9999 /]
[standalone@localhost:9999 /] patch history
{
"outcome" :
"success",
"result" : [
{
"patch-id" : "jboss-eap-6.3.2.CP",
"type"
: "cumulative",
"applied-at" : "4/8/17 1:51 PM"
},
{
"patch-id" : "jboss-eap-6.3.1.CP",
"type"
: "cumulative",
"applied-at" : "4/8/17 1:46 PM"
}
],
"response-headers" : {"process-state" :
"restart-required"}
}
[standalone@localhost:9999 /]
[standalone@localhost:9999 /] shutdown --restart=true
Now again you can reapplied latest CP
using command “patch apply
/jboss/jboss-eap-6.3.3-patch.zip”.
Applying one-off patch, latest EAP 6.3
one-off patch is “BZ-1281964.zip” (Security advisor CVE-2015-7501 Apache commons-Remote
code execution during deserialisation)
I renamed zip to “SecurityAdvisor_CVE-2015-7501ApacheCommons-RemoteCodeExecutionDuringDeserialisation-BZ-1281964.zip”
for better understanding while patch pickup.
[standalone@localhost:9999 /] patch apply /jboss/SecurityAdvisor_CVE-2015-7501ApacheCommons-RemoteCodeExecutionDuringDeserialisation-BZ-1281964.zip
{
"outcome" :
"success",
"response-headers" : {
"operation-requires-restart" : true,
"process-state" : "restart-required"
}
}
[standalone@localhost:9999 /]
[standalone@localhost:9999 /] shutdown --restart=true
[standalone@localhost:9999 /] patch info
{
"outcome" :
"success",
"result" : {
"cumulative-patch-id" : "jboss-eap-6.3.3.CP",
"patches" :
["eap-633-bz1281964"],
"version" :
"6.3.3.GA",
"addon" :
null,
"layer" :
{"base" : {
"cumulative-patch-id" :
"layer-base-jboss-eap-6.3.3.CP",
"patches" :
["BZ1281964"]
}}
}
}
[standalone@localhost:9999 /]
[standalone@localhost:9999 /] patch history
{
"outcome" :
"success",
"result" : [
{
"patch-id" : "eap-633-bz1281964",
"type"
: "one-off",
"applied-at" : "4/8/17 2:15 PM"
},
{
"patch-id" : "jboss-eap-6.3.3.CP",
"type"
: "cumulative",
"applied-at" : "4/8/17 2:13 PM"
},
{
"patch-id" : "jboss-eap-6.3.2.CP",
"type"
: "cumulative",
"applied-at" : "4/8/17 2:12 PM"
},
{
"patch-id" : "jboss-eap-6.3.1.CP",
"type"
: "cumulative",
"applied-at" : "4/8/17 2:12 PM"
}
]
}
[standalone@localhost:9999 /]
[jbossadm@serv1 JBOSSeap63SERVER1]$ cat /jboss/JBOSSeap63SERVER1/version.txt
Red Hat JBoss Enterprise Application Platform - Version 6.3.3.GA
[jbossadm@serv1 JBOSSeap63SERVER1]$
<~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~>
8. Step-8 is to connect
remote server using jboss-cli on remorting JMX port & applying patches.
[jbossadm@serv1 bin]$ pwd
/jboss/JBOSSeap63SERVER1/bin
[jbossadm@serv1
bin]$
JBOSSeap63SERVER2 Remorting JMX
is 9999+100(off-set) = 10099
[jbossadm@serv1
bin]$ ./jboss-cli.sh --connect
--controller=serv1:10099
[standalone@serv1:10099
/] patch info
{
"outcome" :
"success",
"result" : {
"cumulative-patch-id" : "base",
"patches" :
[],
"version" :
"6.3.0.GA",
"addon" :
null,
"layer" :
{"base" : {
"cumulative-patch-id" : "base",
"patches" : []
}}
}
}
[standalone@serv1:10099
/]
[standalone@serv1:10099
/] patch apply /jboss/jboss-eap-6.3.3-patch.zip
{
"outcome" :
"success",
"response-headers" : {
"operation-requires-restart" : true,
"process-state" : "restart-required"
}
}
[standalone@serv1:10099
/]
[standalone@serv1:10099
/] patch info
{
"outcome" : "success",
"result" : {
"cumulative-patch-id" : "jboss-eap-6.3.3.CP",
"patches" :
[],
"version" :
"6.3.3.GA",
"addon" :
null,
"layer" :
{"base" : {
"cumulative-patch-id" : "layer-base-jboss-eap-6.3.3.CP",
"patches" : []
}}
},
"response-headers" : {"process-state" :
"restart-required"}
}
[standalone@serv1:10099
/]
[standalone@serv1:10099
/] patch history
{
"outcome" :
"success",
"result" : [
{
"patch-id"
: "jboss-eap-6.3.3.CP",
"type"
: "cumulative",
"applied-at" : "4/8/17 2:47 PM"
},
{
"patch-id" : "jboss-eap-6.3.2.CP",
"type"
: "cumulative",
"applied-at" : "4/8/17 2:46 PM"
},
{
"patch-id" : "jboss-eap-6.3.1.CP",
"type"
: "cumulative",
"applied-at" : "4/8/17 2:46 PM"
}
],
"response-headers" : {"process-state" :
"restart-required"}
}
[standalone@serv1:10099
/]
[standalone@serv1:10099
/] shutdown --restart=true
[standalone@serv1:10099
/] patch apply
/jboss/SecurityAdvisor_CVE-2015-7501ApacheCommons-RemoteCodeExecutionDuringDeserialisation-BZ-1281964.zip
{
"outcome" :
"success",
"response-headers" : {
"operation-requires-restart" : true,
"process-state" : "restart-required"
}
}
[standalone@serv1:10099
/]
[standalone@serv1:10099
/] shutdown --restart=true
[disconnected /] connect
[standalone@serv1:10099 /]
[standalone@serv1:10099 /] patch info
{
"outcome" :
"success",
"result" : {
"cumulative-patch-id" : "jboss-eap-6.3.3.CP",
"patches" :
["eap-633-bz1281964"],
"version" :
"6.3.3.GA",
"addon" :
null,
"layer" : {"base"
: {
"cumulative-patch-id" :
"layer-base-jboss-eap-6.3.3.CP",
"patches" : ["BZ1281964"]
}}
}
}
[standalone@serv1:10099 /]
[standalone@serv1:10099 /] patch history
{
"outcome" :
"success",
"result" : [
{
"patch-id" : "eap-633-bz1281964",
"type"
: "one-off",
"applied-at" : "4/8/17 3:04 PM"
},
{
"patch-id" : "jboss-eap-6.3.3.CP",
"type"
: "cumulative",
"applied-at"
: "4/8/17 2:47 PM"
},
{
"patch-id" : "jboss-eap-6.3.2.CP",
"type"
: "cumulative",
"applied-at" : "4/8/17 2:46 PM"
},
{
"patch-id" : "jboss-eap-6.3.1.CP",
"type"
: "cumulative",
"applied-at" : "4/8/17 2:46 PM"
}
]
}
[standalone@serv1:10099
/]
[jbossadm@serv1 JBOSSeap63SERVER1]$ cat /jboss/JBOSSeap63SERVER2/version.txt
Red Hat JBoss Enterprise Application Platform - Version 6.3.3.GA
[jbossadm@serv1 JBOSSeap63SERVER1]$
<~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~>
9. Step-9 is to upgrade java
JDK in existing Jboss EAP setup, rollback JDK to earlier using quickest &
easiest method.
Stop all Jboss EAP servers in server.
Make sure no java processes are running.
Latest JDK is 8U121 as on 8th Apr
2017. Java SE 8u121 includes important
security fixes.
Downloaded latest jdk-8u121-linux-i586.rpm
from oracle site.
[root@serv1 jboss]# rpm -ivh jdk-8u121-linux-i586.rpm
Preparing...
########################################### [100%]
1:jdk1.8.0_121
########################################### [100%]
Unpacking JAR files...
tools.jar...
plugin.jar...
javaws.jar...
deploy.jar...
rt.jar...
jsse.jar...
charsets.jar...
localedata.jar...
[root@serv1 jboss]#
[jbossadm@serv1 ~]$ java -version
java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) Client VM (build 25.121-b13, mixed mode, sharing)
[jbossadm@serv1 ~]$
[jbossadm@serv1 ~]$ ls -lrth /usr/bin/java
lrwxrwxrwx. 1 root root 22 Apr
8 16:00 /usr/bin/java -> /etc/alternatives/java
[jbossadm@serv1 ~]$ ls -lrth /etc/alternatives/java
lrwxrwxrwx. 1 root root 35 Apr
8 16:00 /etc/alternatives/java -> /usr/java/jdk1.8.0_121/jre/bin/java
[jbossadm@serv1 ~]$ ls -lrth /usr/java/jdk1.8.0_121/jre/bin/java
-rwxr-xr-x. 1 root root 5.6K Dec 13 05:56 /usr/java/jdk1.8.0_121/jre/bin/java
[jbossadm@serv1 ~]$
Simplest & easy way to rollback
java is to change soft links of “/etc/alternatives/java” to earlier version of java.
From:-
/etc/alternatives/java ->
/usr/java/jdk1.8.0_121/jre/bin/java
To :-
/etc/alternatives/java -> /usr/java/jre1.8.0_91/bin/java
<~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~>
10.
Step-10
is to work on Max & Min heap memory size & understanding PermSize.
The Enterprise Web Platform ships with
default values for initial and maximum heap allocations by the JVM. These
values are:
-Xms1303m:
Initial heap size, set in megabytes
-Xmx1303m:
Maximum heap size, set in megabytes
While using JAVA 8 or above version
you will be observer error “Java HotSpot(TM) Server VM warning: ignoring
option MaxPermSize=256m; support was removed in 8.0” in server log as Java 8, both the
permgen space and this setting are depreciated. Such messages can be easily
ignorable.
The permanent
space is where the classes, methods, internalized strings, and similar objects
used by the VM are stored and never deallocated (hence the name).
Permanent
Generation: The Permanent Generation is where class files are kept. These are
the result of compiled classes and jsp pages. If this space is full, it triggers
a Full Garbage Collection. If the Full Garbage Collection cannot clean out old
unreferenced classes and there is no room left to expand the Permanent Space,
an OutofMemory error (OOME) is thrown and the JVM will crash.
The permanent
generation does not have a noticeable impact on garbage collector performance
for most applications. However, some applications dynamically generate and load
many classes; for example, some implementations of JavaServer Pages (JSP)
pages. These applications may need a larger permanent generation to hold the
additional classes. If so, the maximum permanent generation size can be
increased with the command-line option -XX:MaxPermSize=.
Starting with
Java 8, both the permgen space and this setting are gone. The memory model used
for loaded classes and methods is different and isn't limited (with default
settings). You should not see this error any more.
The reason why
you get this message in Java 8 is because Permgen has been replaced by
Metaspace to address some of PermGen's drawbacks (as you were able to see for
yourself, one of those drawbacks is that it had a fixed size).
Just remove the -XX:MaxPermSize=256m parameter from config file to over
errors in server log.
Changing Max heap size to 256mb &
Min heap size to 128mb.
[jbossadm@serv1 bin]$ cp -pv /jboss/JBOSSeap63SERVER1/bin/standalone.conf
/jboss/JBOSSeap63SERVER1/bin/standalone.conf.SRIbkp.08Apr2017
`/jboss/JBOSSeap63SERVER1/bin/standalone.conf'
-> `/jboss/JBOSSeap63SERVER1/bin/standalone.conf.SRIbkp.08Apr2017'
[jbossadm@serv1 bin]$
[jbossadm@serv1 bin]$ vi /jboss/JBOSSeap63SERVER1/bin/standalone.conf
[jbossadm@serv1 bin]$
[jbossadm@serv1 bin]$ diff /jboss/JBOSSeap63SERVER1/bin/standalone.conf
/jboss/JBOSSeap63SERVER1/bin/standalone.conf.SRIbkp.08Apr2017
50c50
< JAVA_OPTS="-Xms128m -Xmx256m
-XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true"
---
>
JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MaxPermSize=256m
-Djava.net.preferIPv4Stack=true"
[jbossadm@serv1 bin]$
[jbossadm@serv1 bin]$ ps -ef| grep standalone
jbossadm
2247 1690 0 15:00 pts/0 00:00:00 /bin/sh
/jboss/JBOSSeap63SERVER1/bin/standalone.sh -Djboss.node.name=server1 -b 0.0.0.0
jbossadm
2318 2247 55 15:00 pts/0 00:00:27 java -D[Standalone] -server
-verbose:gc -Xloggc:/jboss/JBOSSeap63SERVER1/standalone/log/gc.log
-XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -Xms128m -Xmx256m -XX:MaxPermSize=256m
-Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman
-Djava.awt.headless=true -Djboss.modules.policy-permissions=true
-Dorg.jboss.boot.log.file=/jboss/JBOSSeap63SERVER1/standalone/log/server.log
-Dlogging.configuration=file:/jboss/JBOSSeap63SERVER1/standalone/configuration/logging.properties
-jar /jboss/JBOSSeap63SERVER1/jboss-modules.jar -mp
/jboss/JBOSSeap63SERVER1/modules -jaxpmodule javax.xml.jaxp-provider
org.jboss.as.standalone -Djboss.home.dir=/jboss/JBOSSeap63SERVER1
-Djboss.server.base.dir=/jboss/JBOSSeap63SERVER1/standalone -Djboss.node.name=server1
-b 0.0.0.0
jbossadm
2425 1690 0 15:01 pts/0 00:00:00 grep standalone
[jbossadm@serv1 bin]$
[jbossadm@serv1 bin]$ cp -pv /jboss/JBOSSeap63SERVER2/bin/standalone.conf
/jboss/JBOSSeap63SERVER2/bin/standalone.conf.SRIbkp.08Apr2017
`/jboss/JBOSSeap63SERVER2/bin/standalone.conf'
-> `/jboss/JBOSSeap63SERVER2/bin/standalone.conf.SRIbkp.08Apr2017'
[jbossadm@serv1 bin]$
[jbossadm@serv1 bin]$ vi /jboss/JBOSSeap63SERVER2/bin/standalone.conf
[jbossadm@serv1 bin]$ diff /jboss/JBOSSeap63SERVER2/bin/standalone.conf
/jboss/JBOSSeap63SERVER2/bin/standalone.conf.SRIbkp.08Apr2017
50c50
<
JAVA_OPTS="-Xms128m -Xmx256m -XX:MaxPermSize=256m
-Djava.net.preferIPv4Stack=true"
---
>
JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true"
[jbossadm@serv1 bin]$
<~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~>
Appendix.
Appendix.
a.
Output#1
[jbossadm@serv1 jboss]$ /jboss/JBOSSeap63SERVER1/bin/standalone.sh
-Djboss.node.name=server1 -b 0.0.0.0 &
[1] 1888
[jbossadm@serv1 jboss]$
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME:
/jboss/JBOSSeap63SERVER1
JAVA: java
JAVA_OPTS: -server -verbose:gc
-Xloggc:"/jboss/JBOSSeap63SERVER1/standalone/log/gc.log"
-XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading
-Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
-Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
-Djboss.modules.policy-permissions=true
=========================================================================
Java HotSpot(TM) Server VM warning: ignoring option
MaxPermSize=256m; support was removed in 8.0
[jbossadm@serv1 jboss]$ 23:07:43,397
INFO [org.jboss.modules] (main) JBoss
Modules version 1.3.3.Final-redhat-1
23:07:45,375 INFO
[org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1
23:07:46,322 INFO
[org.jboss.as] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.3.0.GA
(AS 7.4.0.Final-redhat-19) starting
23:08:03,115 INFO [org.xnio]
(MSC service thread 1-2) XNIO Version 3.0.10.GA-redhat-1
23:08:03,231 INFO
[org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http
management service using socket-binding (management-http)
23:08:03,278 INFO
[org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version
3.0.10.GA-redhat-1
23:08:03,941 INFO
[org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version
(unknown)
23:08:04,128 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29)
JBAS010280: Activating Infinispan subsystem.
23:08:04,207 INFO
[org.jboss.as.naming] (ServerService Thread Pool -- 37) JBAS011800:
Activating Naming Subsystem
23:08:04,222 WARN
[org.jboss.as.txn] (ServerService Thread Pool -- 44) JBAS010153: Node
identifier property is set to the default value. Please make sure it is unique.
23:08:04,226 INFO
[org.jboss.as.security] (ServerService Thread Pool -- 42) JBAS013171:
Activating Security Subsystem
23:08:04,385 INFO
[org.jboss.as.webservices] (ServerService Thread Pool -- 46) JBAS015537:
Activating WebServices Extension
23:08:04,433 INFO
[org.jboss.as.jsf] (ServerService Thread Pool -- 35) JBAS012605:
Activated the following JSF Implementations: [main, 1.2]
23:08:05,480 INFO
[org.jboss.as.security] (MSC service thread 1-1) JBAS013170: Current
PicketBox version=4.0.19.SP8-redhat-1
23:08:05,960 INFO
[org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408:
Starting JCA Subsystem (IronJacamar 1.0.26.Final-redhat-1)
23:08:06,170 INFO
[org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting
Naming Service
23:08:06,263 INFO
[org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool
-- 25) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version
1.3)
23:08:06,538 INFO
[org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound
mail session [java:jboss/mail/Default]
23:08:10,301 INFO
[org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1)
JBWEB003001: Coyote HTTP/1.1 initializing on : http-/0.0.0.0:8080
23:08:10,382 INFO
[org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1)
JBWEB003000: Coyote HTTP/1.1 starting on: http-/0.0.0.0:8080
23:08:11,546 INFO
[org.jboss.as.server.deployment.scanner] (MSC service thread 1-1)
JBAS015012: Started FileSystemDeploymentService for directory
/jboss/JBOSSeap63SERVER1/standalone/deployments
23:08:12,239 INFO
[org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052:
Starting JBoss Web Services - Stack CXF Server 4.3.0.Final-redhat-3
23:08:12,906 INFO
[org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening
on 127.0.0.1:9999
23:08:12,926 INFO
[org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening
on 0.0.0.0:4447
23:08:13,280 INFO
[org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2)
JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
23:08:16,745 INFO
[org.jboss.as] (Controller Boot Thread) JBAS015961: Http management
interface listening on http://127.0.0.1:9990/management
23:08:16,747 INFO
[org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console
listening on http://127.0.0.1:9990
23:08:16,751 INFO
[org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.3.0.GA
(AS 7.4.0.Final-redhat-19) started in 36591ms - Started 151 of 189 services (56
services are lazy, passive or on-demand)
[jbossadm@serv1 jboss]$
[jbossadm@serv1 jboss]$ /jboss/JBOSSeap63SERVER2/bin/standalone.sh
-Djboss.node.name=server2 -b 0.0.0.0 -Djboss.socket.binding.port-offset=100
&
[2] 2041
[jbossadm@serv1 jboss]$
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME:
/jboss/JBOSSeap63SERVER2
JAVA: java
JAVA_OPTS: -server -verbose:gc
-Xloggc:"/jboss/JBOSSeap63SERVER2/standalone/log/gc.log"
-XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading
-Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
-Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
-Djboss.modules.policy-permissions=true
=========================================================================
Java HotSpot(TM) Server VM warning: ignoring option MaxPermSize=256m;
support was removed in 8.0
23:08:51,177 INFO
[org.jboss.modules] (main) JBoss Modules version 1.3.3.Final-redhat-1
23:08:53,140 INFO
[org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1
23:08:54,202 INFO
[org.jboss.as] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.3.0.GA
(AS 7.4.0.Final-redhat-19) starting
23:09:09,360 INFO [org.xnio]
(MSC service thread 1-2) XNIO Version 3.0.10.GA-redhat-1
23:09:09,426 INFO
[org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http
management service using socket-binding (management-http)
23:09:09,467 INFO
[org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version
3.0.10.GA-redhat-1
23:09:10,644 INFO
[org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version
(unknown)
23:09:11,014 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29)
JBAS010280: Activating Infinispan subsystem.
23:09:11,056 INFO
[org.jboss.as.naming] (ServerService Thread Pool -- 37) JBAS011800:
Activating Naming Subsystem
23:09:11,109 WARN
[org.jboss.as.txn] (ServerService Thread Pool -- 44) JBAS010153: Node
identifier property is set to the default value. Please make sure it is unique.
23:09:11,131 INFO
[org.jboss.as.security] (ServerService Thread Pool -- 42) JBAS013171:
Activating Security Subsystem
23:09:11,254 INFO
[org.jboss.as.webservices] (ServerService Thread Pool -- 46) JBAS015537:
Activating WebServices Extension
23:09:11,270 INFO
[org.jboss.as.jsf] (ServerService Thread Pool -- 35) JBAS012605: Activated
the following JSF Implementations: [main, 1.2]
23:09:11,858 INFO
[org.jboss.as.security] (MSC service thread 1-2) JBAS013170: Current
PicketBox version=4.0.19.SP8-redhat-1
23:09:12,400 INFO
[org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408:
Starting JCA Subsystem (IronJacamar 1.0.26.Final-redhat-1)
23:09:12,652 INFO
[org.jboss.as.connector.subsystems.datasources] (ServerService Thread
Pool -- 25) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver
(version 1.3)
23:09:12,709 INFO
[org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting
Naming Service
23:09:12,896 INFO
[org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound
mail session [java:jboss/mail/Default]
23:09:15,583 INFO
[org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1)
JBWEB003001: Coyote HTTP/1.1 initializing on : http-/0.0.0.0:8180
23:09:15,649 INFO
[org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1)
JBWEB003000: Coyote HTTP/1.1 starting on: http-/0.0.0.0:8180
23:09:16,612 INFO
[org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052:
Starting JBoss Web Services - Stack CXF Server 4.3.0.Final-redhat-3
23:09:16,776 INFO
[org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012:
Started FileSystemDeploymentService for directory
/jboss/JBOSSeap63SERVER2/standalone/deployments
23:09:16,953 INFO
[org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening
on 127.0.0.1:10099
23:09:16,962 INFO
[org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening
on 0.0.0.0:4547
23:09:17,406 INFO
[org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1)
JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
23:09:18,675 INFO
[org.jboss.as] (Controller Boot Thread) JBAS015961: Http management
interface listening on http://127.0.0.1:10090/management
23:09:18,682 INFO
[org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console
listening on http://127.0.0.1:10090
23:09:18,688 INFO [org.jboss.as]
(Controller Boot Thread) JBAS015874: JBoss EAP 6.3.0.GA (AS
7.4.0.Final-redhat-19) started in 29634ms - Started 151 of 189 services (56
services are lazy, passive or on-demand)
[jbossadm@serv1 jboss]$
b. Output#2
[jbossadm@serv1 jboss]$ /jboss/JBOSSeap63SERVER1/bin/standalone.sh
-Djboss.node.name=server1 -b 0.0.0.0 &
[1] 2253
[jbossadm@serv1 jboss]$
23:39:23,930 INFO
[org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2)
JBWEB003001: Coyote HTTP/1.1 initializing on : http-/0.0.0.0:8080
23:39:24,023 INFO
[org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2)
JBWEB003000: Coyote HTTP/1.1 starting on: http-/0.0.0.0:8080
23:39:25,239 INFO
[org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting
JBoss Web Services - Stack CXF Server 4.3.0.Final-redhat-3
23:39:25,343 INFO
[org.jboss.as.server.deployment.scanner] (MSC service thread 1-2)
JBAS015012: Started FileSystemDeploymentService for directory
/jboss/JBOSSeap63SERVER1/standalone/deployments
23:39:25,535 INFO
[org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening
on 0.0.0.0:4447
23:39:25,575 INFO
[org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening
on 0.0.0.0:9999
23:39:25,987 INFO
[org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1)
JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
23:39:26,337 INFO
[org.jboss.as] (Controller Boot Thread) JBAS015961: Http management
interface listening on http://0.0.0.0:9990/management
23:39:26,340 INFO
[org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console
listening on http://0.0.0.0:9990
23:39:26,345 INFO
[org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.3.0.GA
(AS 7.4.0.Final-redhat-19) started in 16578ms - Started 151 of 189 services (56
services are lazy, passive or on-demand)
[jbossadm@serv1 jboss]$ /jboss/JBOSSeap63SERVER2/bin/standalone.sh -Djboss.node.name=server2 -b
0.0.0.0 &
[2] 2410
[jbossadm@serv1 jboss]$
23:40:26,691 INFO [org.apache.coyote.http11.Http11Protocol]
(MSC service thread 1-2) JBWEB003001: Coyote HTTP/1.1 initializing on :
http-/0.0.0.0:8180
23:40:26,783 INFO
[org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2)
JBWEB003000: Coyote HTTP/1.1 starting on: http-/0.0.0.0:8180
23:40:27,852 INFO
[org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052:
Starting JBoss Web Services - Stack CXF Server 4.3.0.Final-redhat-3
23:40:28,058 INFO
[org.jboss.as.server.deployment.scanner] (MSC service thread 1-2)
JBAS015012: Started FileSystemDeploymentService for directory
/jboss/JBOSSeap63SERVER2/standalone/deployments
23:40:28,221 INFO
[org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening
on 0.0.0.0:10099
23:40:28,233 INFO
[org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening
on 0.0.0.0:4547
23:40:28,573 INFO
[org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2)
JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
23:40:28,883 INFO [org.jboss.as]
(Controller Boot Thread) JBAS015961: Http management interface listening on
http://0.0.0.0:10090/management
23:40:28,884 INFO
[org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console
listening on http://0.0.0.0:10090
23:40:28,891 INFO [org.jboss.as] (Controller Boot Thread)
JBAS015874: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started in 15911ms -
Started 151 of 189 services (56 services are lazy, passive or on-demand)
c.
Output#3
[jbossadm@serv1 bin]$ sh jboss-cli.sh
You are disconnected at the moment. Type 'connect' to connect to
the server or 'help' for the list of supported commands.
[disconnected /]
[disconnected /] help
Usage:
jboss-cli.sh/jboss-cli.bat
[--help] [--version] [--controller=host:port]
[--connect]
[--file=file_path]
[--commands=command_or_operation1,command_or_operation2...]
[--command=command_or_operation]
[--user=username --password=password]
[--no-local-auth]
[--timeout=timeout]
--help (-h) - prints (this) basic description of the
command line utility.
--version - prints the version info of the JBoss
EAP release, JVM and
system environment.
--controller - the default controller host and port to
connect to when
--connect
option (described below) is specified or when the
connect
command is issued w/o the arguments. The default
controller host is localhost
and the port is 9999.
--connect (-c) - instructs the CLI to connect to the
controller on start-up
(to avoid
issuing a separate connect command later).
--gui - GUI built on top of the CLI, the
only difference is that it
brings up
a GUI instead of a command line. In this mode, the
CLI will
automatically connect during start-up. You can
optionally
specify --controller, if necessary.
--file - specifies a path to a file which
contains commands and
operations
(one per line) that should be executed (in a
non-interactive mode). The CLI will terminate the session
immediately
after the last command has been executed or if
some
command or operation failed.
--command - specifies a single command or an
operation that should be
executed
in the CLI session. The CLI will terminate the
session
immediately after the command or the operation has
been
executed. Note: --command argument is optional in a
sense that
any word (or phrase without whitespaces in it)
will be
assumed to be a command (or an operation).
--commands - specifies a comma-separated list (the
list must not contain
whitespaces) of commands and operations that should be
executed in the CLI session. The CLI
session will be
automatically terminated as soon as the last command or
operation
has been executed or after the first error. Note:
--commands
argument is optional in a sense that any
comma-separated list at the end of the argument list will be
assumed to
be the list of commands and operations.
--user - if the controller requires user
authentication, this argument
can be
used to specify the user name as a command line
argument.
If the argument isn't specified and the
authentication is required the user will be prompted to enter
the user
name when the connect command is issued.
Local
authentication is automatically disabled if a user is specified.
--password - specifies the password for
authentication while connecting to
the
controller as a command line argument. If the argument
isn't
specified and the authentication is required the user
will be
prompted to enter the password when the connect
command is
issued.
--no-local-auth - disable
the local authentication mechanism which allows the CLI
to
demonstrate that it is being executed locally to the server
being
managed through an exchange of tokens using the filesystem.
--timeout - specifies home many milliseconds to
wait for a given command
to return.
The value provided must be a positive integer.
Defaults
to 5000 milliseconds when not provided.
For a list of available commands execute
help --commands
The resulting listing may depend on the current context. E.g. some
of the
commands require an established connection to the controller
(standalone or
domain). These commands won't appear in the listing unless the
connection has
been established. Other commands may depend on the availability of
specific
subsystems. E.g. if the messaging subsystem is not available,
messaging-related
commands will not be listed.
Here are some of the most basic supported commands:
cn (or cd) - change the current node path to the
argument;
connect - connect to the server or
domain controller;
deploy - deploy an application;
help (or h) - print this message;
history - print or disable/enable/clear
the history expansion;
ls - list the contents of the
node path;
pwn (or pwd) - prints the current working node;
quit (or q) - quit the command line interface;
undeploy - undeploy an application;
version - prints the version and
environment information.
For a more detailed description of a specific command, execute the
command with
'--help' as the argument.
Tab-completion is supported for the commands, just press the tab
key to start.
Operation requests start with './' or '/' and follow the format:
[node-type=node-name (/node-type=node-name)*] : operation-name
['('[name=value [, name=value]*]')'] [{header (;header)*}]
e.g. /subsystem=web/connector=http:read-attribute(name=protocol)
If the operation request doesn't require a node path then the
request can start
with ':' followed by an operation name and the property list if
necessary ('/:'
and './:' are also possible).
Whitespaces between the separators are insignificant.
If the operation doesn't require arguments then the brackets '()'
are optional.
Tab-completion for operation requests supports node types and
names, operation
names, property names and, in some cases, values.
[disconnected /]
d. Output#4
[standalone@localhost:9999 /] shutdown --restart=true
14:13:54,469 INFO
[org.jboss.web] (ServerService Thread Pool -- 57) JBAS018224: Unregister
web context: /Sricluster-testEAP6
14:13:54,486 INFO
[org.apache.catalina.core] (MSC service thread 1-1) JBWEB001079:
Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/]
has not been started
14:13:54,577 INFO
[org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2)
JBWEB003075: Coyote HTTP/1.1 pausing on: http-/0.0.0.0:8080
14:13:54,579 INFO
[org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2)
JBWEB003077: Coyote HTTP/1.1 stopping on : http-/0.0.0.0:8080
14:13:54,663 INFO
[org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2)
JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS]
14:13:54,735 INFO
[org.jboss.web] (ServerService Thread Pool -- 58) JBAS018224: Unregister
web context: /SriWARV1.0
14:13:54,780 INFO
[org.jboss.web] (ServerService Thread Pool -- 59) JBAS018224: Unregister
web context: /sample
14:13:54,778 INFO
[org.jboss.web] (ServerService Thread Pool -- 60) JBAS018224: Unregister
web context: /Sricluster-testEAP6v1.0
14:13:54,800 INFO
[org.jboss.web] (ServerService Thread Pool -- 61) JBAS018224: Unregister
web context: /Sricluster-testEAP6v1.1
14:13:54,857 INFO
[org.jboss.web] (ServerService Thread Pool -- 62) JBAS018224: Unregister
web context: /cluster-test
14:13:55,053 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 64)
JBAS010282: Stopped default-host/cluster-test cache from web container
14:13:55,064 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66)
JBAS010282: Stopped default-host/Sricluster-testEAP6v1.1 cache from web
container
14:13:55,070 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 60)
JBAS010282: Stopped default-host/Sricluster-testEAP6v1.0 cache from web
container
14:13:55,074 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 58)
JBAS010282: Stopped default-host/Sricluster-testEAP6 cache from web container
14:13:55,407 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877:
Stopped deployment cluster-test.war (runtime-name: cluster-test.war) in 983ms
14:13:55,407 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877:
Stopped deployment Sricluster-testEAP6.war (runtime-name:
Sricluster-testEAP6.war) in 1022ms
14:13:55,418 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877:
Stopped deployment Sricluster-testEAP6v1.0.war (runtime-name:
Sricluster-testEAP6v1.0.war) in 995ms
14:13:55,418 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877:
Stopped deployment Sricluster-testEAP6v1.1.war (runtime-name:
Sricluster-testEAP6v1.1.war) in 1000ms
14:13:55,426 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877:
Stopped deployment sample.war (runtime-name: sample.war) in 1017ms
14:13:55,440 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877:
Stopped deployment SriWARV1.0.war (runtime-name: SriWARV1.0.war) in 1017ms
14:13:55,454 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 72)
JBAS010282: Stopped local-web cache from web container
14:13:55,492 INFO
[org.jboss.as] (MSC service thread 1-1) JBAS015950: JBoss EAP 6.3.0.GA
(AS 7.4.0.Final-redhat-19) stopped in 1053ms
Restarting JBoss...
Java HotSpot(TM) Server VM warning: ignoring option
MaxPermSize=256m; support was removed in 8.0
14:14:00,945 INFO
[org.jboss.modules] (main) JBoss Modules version 1.3.5.Final-redhat-1
14:14:02,393 INFO
[org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1
14:14:02,727 INFO
[org.jboss.as] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.3.3.GA (AS
7.4.3.Final-redhat-2) starting
Failed to establish connection in 6166ms: JBAS012174: Could not
connect to remote://localhost:9999. The connection failed: Connection refused
[disconnected /] 14:14:09,064 INFO
[org.xnio] (MSC service thread 1-1) XNIO Version 3.0.11.GA-redhat-2
14:14:09,099 INFO
[org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http
management service using socket-binding (management-http)
14:14:09,130 INFO
[org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version
3.0.11.GA-redhat-2
14:14:09,618 INFO
[org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version
3.3.4.Final-redhat-1
14:14:09,676 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29)
JBAS010280: Activating Infinispan subsystem.
14:14:09,728 INFO
[org.jboss.as.naming] (ServerService Thread Pool -- 37) JBAS011800:
Activating Naming Subsystem
14:14:09,770 WARN
[org.jboss.as.txn] (ServerService Thread Pool -- 44) JBAS010153: Node
identifier property is set to the default value. Please make sure it is unique.
14:14:09,762 INFO
[org.jboss.as.security] (ServerService Thread Pool -- 42) JBAS013171:
Activating Security Subsystem
14:14:09,878 INFO
[org.jboss.as.webservices] (ServerService Thread Pool -- 46) JBAS015537:
Activating WebServices Extension
14:14:09,933 INFO
[org.jboss.as.jsf] (ServerService Thread Pool -- 35) JBAS012605:
Activated the following JSF Implementations: [main, 1.2]
14:14:10,382 INFO
[org.jboss.as.security] (MSC service thread 1-1) JBAS013170: Current
PicketBox version=4.0.19.SP10-redhat-1
14:14:10,677 INFO
[org.jboss.as.connector.logging] (MSC service thread 1-1) JBAS010408:
Starting JCA Subsystem (IronJacamar 1.0.28.Final-redhat-1)
14:14:10,990 INFO
[org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting
Naming Service
14:14:10,989 INFO
[org.jboss.as.connector.subsystems.datasources] (ServerService Thread
Pool -- 25) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver
(version 1.3)
14:14:11,086 INFO
[org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound
mail session [java:jboss/mail/Default]
14:14:13,247 INFO
[org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2)
JBWEB003001: Coyote HTTP/1.1 initializing on : http-/0.0.0.0:8080
14:14:13,281 INFO
[org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2)
JBWEB003000: Coyote HTTP/1.1 starting on: http-/0.0.0.0:8080
14:14:13,738 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876:
Starting deployment of "Sricluster-testEAP6.war" (runtime-name:
"Sricluster-testEAP6.war")
14:14:13,753 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876:
Starting deployment of "sample.war" (runtime-name:
"sample.war")
14:14:13,754 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876:
Starting deployment of "Sricluster-testEAP6v1.0.war" (runtime-name:
"Sricluster-testEAP6v1.0.war")
14:14:13,763 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876:
Starting deployment of "cluster-test.war" (runtime-name:
"cluster-test.war")
14:14:13,765 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876:
Starting deployment of "SriWARV1.0.war" (runtime-name:
"SriWARV1.0.war")
14:14:13,766 INFO [org.jboss.as.server.deployment]
(MSC service thread 1-2) JBAS015876: Starting deployment of
"Sricluster-testEAP6v1.1.war" (runtime-name:
"Sricluster-testEAP6v1.1.war")
14:14:13,812 INFO
[org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012:
Started FileSystemDeploymentService for directory
/jboss/JBOSSeap63SERVER1/standalone/deployments
14:14:14,347 INFO
[org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052:
Starting JBoss Web Services - Stack CXF Server 4.3.4.Final-redhat-1
14:14:14,817 INFO
[org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening
on 0.0.0.0:4447
14:14:14,823 INFO
[org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening
on 0.0.0.0:9999
14:14:15,182 INFO
[org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1)
JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
14:14:16,708 INFO
[org.jboss.web] (ServerService Thread Pool -- 50) JBAS018210: Register
web context: /SriWARV1.0
14:14:16,849 INFO [org.jboss.web]
(ServerService Thread Pool -- 49) JBAS018210: Register web context: /sample
14:14:17,968 INFO
[org.infinispan.factories.GlobalComponentRegistry] (ServerService Thread
Pool -- 49) ISPN000128: Infinispan version: Infinispan 'Delirium' 5.2.10.Final
14:14:18,155 INFO
[org.infinispan.factories.TransactionManagerFactory] (ServerService
Thread Pool -- 52) ISPN000161: Using a batchMode transaction manager
14:14:18,155 INFO
[org.infinispan.factories.TransactionManagerFactory] (ServerService
Thread Pool -- 51) ISPN000161: Using a batchMode transaction manager
14:14:18,162 INFO
[org.infinispan.factories.TransactionManagerFactory] (ServerService
Thread Pool -- 50) ISPN000161: Using a batchMode transaction manager
14:14:18,163 INFO
[org.infinispan.factories.TransactionManagerFactory] (ServerService
Thread Pool -- 53) ISPN000161: Using a batchMode transaction manager
14:14:18,145 INFO
[org.infinispan.factories.TransactionManagerFactory] (ServerService
Thread Pool -- 48) ISPN000161: Using a batchMode transaction manager
14:14:19,010 INFO
[org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool --
50) ISPN000031: MBeans were successfully registered to the platform MBean
server.
14:14:19,014 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 50)
JBAS010281: Started local-web cache from web container
14:14:19,074 INFO
[org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool --
48) ISPN000031: MBeans were successfully registered to the platform MBean
server.
14:14:19,079 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 48)
JBAS010281: Started default-host/Sricluster-testEAP6 cache from web container
14:14:19,084 INFO
[org.jboss.web] (ServerService Thread Pool -- 49) JBAS018210: Register web
context: /Sricluster-testEAP6
14:14:19,124 INFO
[org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool --
53) ISPN000031: MBeans were successfully registered to the platform MBean
server.
14:14:19,125 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 53)
JBAS010281: Started default-host/Sricluster-testEAP6v1.1 cache from web
container
14:14:19,129 INFO
[org.jboss.web] (ServerService Thread Pool -- 48) JBAS018210: Register
web context: /Sricluster-testEAP6v1.1
14:14:19,135 INFO
[org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool --
51) ISPN000031: MBeans were successfully registered to the platform MBean
server.
14:14:19,135 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 51)
JBAS010281: Started default-host/Sricluster-testEAP6v1.0 cache from web
container
14:14:19,136 INFO
[org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool --
52) ISPN000031: MBeans were successfully registered to the platform MBean
server.
14:14:19,136 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 52)
JBAS010281: Started default-host/cluster-test cache from web container
14:14:19,141 INFO
[org.jboss.web] (ServerService Thread Pool -- 51) JBAS018210: Register
web context: /cluster-test
14:14:19,150 INFO
[org.jboss.web] (ServerService Thread Pool -- 52) JBAS018210: Register
web context: /Sricluster-testEAP6v1.0
14:14:19,458 INFO
[org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559:
Deployed "Sricluster-testEAP6.war" (runtime-name :
"Sricluster-testEAP6.war")
14:14:19,459 INFO
[org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559:
Deployed "Sricluster-testEAP6v1.1.war" (runtime-name :
"Sricluster-testEAP6v1.1.war")
14:14:19,459 INFO
[org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559:
Deployed "cluster-test.war" (runtime-name :
"cluster-test.war")
14:14:19,460 INFO
[org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559:
Deployed "SriWARV1.0.war" (runtime-name : "SriWARV1.0.war")
14:14:19,460 INFO
[org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559:
Deployed "Sricluster-testEAP6v1.0.war" (runtime-name :
"Sricluster-testEAP6v1.0.war")
14:14:19,460 INFO
[org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559:
Deployed "sample.war" (runtime-name : "sample.war")
14:14:19,563 INFO
[org.jboss.as] (Controller Boot Thread) JBAS015961: Http management
interface listening on http://0.0.0.0:9990/management
14:14:19,565 INFO
[org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console
listening on http://0.0.0.0:9990
14:14:19,566 INFO
[org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.3.3.GA
(AS 7.4.3.Final-redhat-2) started in 22570ms - Started 495 of 523 services (87 services
are lazy, passive or on-demand)
[disconnected /]
e.
Output#5
[standalone@localhost:9999 /] shutdown --restart=true
14:16:07,727 INFO
[org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1)
JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS]
14:16:07,741 INFO
[org.apache.catalina.core] (MSC service thread 1-1) JBWEB001079:
Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/]
has not been started
14:16:07,776 INFO
[org.jboss.web] (ServerService Thread Pool -- 55) JBAS018224: Unregister
web context: /sample
14:16:07,794 INFO
[org.jboss.web] (ServerService Thread Pool -- 56) JBAS018224: Unregister
web context: /Sricluster-testEAP6v1.0
14:16:07,828 INFO
[org.jboss.web] (ServerService Thread Pool -- 57) JBAS018224: Unregister
web context: /cluster-test
14:16:07,841 INFO
[org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2)
JBWEB003075: Coyote HTTP/1.1 pausing on: http-/0.0.0.0:8080
14:16:07,842 INFO
[org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2)
JBWEB003077: Coyote HTTP/1.1 stopping on : http-/0.0.0.0:8080
14:16:07,871 INFO
[org.jboss.web] (ServerService Thread Pool -- 58) JBAS018224: Unregister
web context: /SriWARV1.0
14:16:07,881 INFO
[org.jboss.web] (ServerService Thread Pool -- 59) JBAS018224: Unregister
web context: /Sricluster-testEAP6
14:16:07,902 INFO
[org.jboss.web] (ServerService Thread Pool -- 60) JBAS018224: Unregister
web context: /Sricluster-testEAP6v1.1
14:16:08,032 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 76) JBAS010282: Stopped default-host/cluster-test
cache from web container
14:16:08,033 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 77)
JBAS010282: Stopped default-host/Sricluster-testEAP6 cache from web container
14:16:08,059 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 71)
JBAS010282: Stopped default-host/Sricluster-testEAP6v1.1 cache from web
container
14:16:08,082 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 77)
JBAS010282: Stopped default-host/Sricluster-testEAP6v1.0 cache from web
container
14:16:08,137 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877:
Stopped deployment SriWARV1.0.war (runtime-name: SriWARV1.0.war) in 463ms
14:16:08,147 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877:
Stopped deployment Sricluster-testEAP6.war (runtime-name:
Sricluster-testEAP6.war) in 519ms
14:16:08,154 INFO [org.jboss.as.server.deployment]
(MSC service thread 1-1) JBAS015877: Stopped deployment sample.war
(runtime-name: sample.war) in 486ms
14:16:08,166 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877:
Stopped deployment Sricluster-testEAP6v1.0.war (runtime-name:
Sricluster-testEAP6v1.0.war) in 492ms
14:16:08,168 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877:
Stopped deployment Sricluster-testEAP6v1.1.war (runtime-name:
Sricluster-testEAP6v1.1.war) in 500ms
14:16:08,171 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877:
Stopped deployment cluster-test.war (runtime-name: cluster-test.war) in 518ms
14:16:08,176 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 60)
JBAS010282: Stopped local-web cache from web container
14:16:08,203 INFO
[org.jboss.as] (MSC service thread 1-1) JBAS015950: JBoss EAP 6.3.3.GA
(AS 7.4.3.Final-redhat-2) stopped in 520ms
Restarting JBoss...
Java HotSpot(TM) Server VM warning: ignoring option MaxPermSize=256m;
support was removed in 8.0
14:16:09,753 INFO
[org.jboss.modules] (main) JBoss Modules version 1.3.5.Final-redhat-1
14:16:10,523 INFO
[org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1
14:16:10,774 INFO
[org.jboss.as] (MSC service thread 1-2) JBAS015899: JBoss EAP 6.3.3.GA
(AS 7.4.3.Final-redhat-2) starting
Failed to establish connection in 6106ms: JBAS012174: Could not
connect to remote://localhost:9999. The connection failed: Connection refused
[disconnected /] 14:16:16,350 INFO [org.xnio] (MSC service thread 1-2) XNIO
Version 3.0.11.GA-redhat-2
14:16:16,396 INFO
[org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http
management service using socket-binding (management-http)
14:16:16,420 INFO
[org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version
3.0.11.GA-redhat-2
14:16:16,814 INFO
[org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version
3.3.4.Final-redhat-1
14:16:16,966 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29)
JBAS010280: Activating Infinispan subsystem.
14:16:17,024 INFO
[org.jboss.as.naming] (ServerService Thread Pool -- 37) JBAS011800:
Activating Naming Subsystem
14:16:17,083 WARN
[org.jboss.as.txn] (ServerService Thread Pool -- 44) JBAS010153: Node
identifier property is set to the default value. Please make sure it is unique.
14:16:17,205 INFO
[org.jboss.as.security] (ServerService Thread Pool -- 42) JBAS013171:
Activating Security Subsystem
14:16:17,181 INFO
[org.jboss.as.jsf] (ServerService Thread Pool -- 35) JBAS012605:
Activated the following JSF Implementations: [main, 1.2]
14:16:17,232 INFO
[org.jboss.as.webservices] (ServerService Thread Pool -- 46) JBAS015537:
Activating WebServices Extension
14:16:17,514 INFO [org.jboss.as.security]
(MSC service thread 1-2) JBAS013170: Current PicketBox
version=4.0.19.SP10-redhat-1
14:16:17,955 INFO
[org.jboss.as.connector.logging] (MSC service thread 1-1) JBAS010408:
Starting JCA Subsystem (IronJacamar 1.0.28.Final-redhat-1)
14:16:18,217 INFO
[org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting
Naming Service
14:16:18,240 INFO
[org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound
mail session [java:jboss/mail/Default]
14:16:18,271 INFO [org.jboss.as.connector.subsystems.datasources]
(ServerService Thread Pool -- 25) JBAS010403: Deploying JDBC-compliant driver
class org.h2.Driver (version 1.3)
14:16:19,662 INFO
[org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2)
JBWEB003001: Coyote HTTP/1.1 initializing on : http-/0.0.0.0:8080
14:16:19,784 INFO
[org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2)
JBWEB003000: Coyote HTTP/1.1 starting on: http-/0.0.0.0:8080
14:16:20,792 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876:
Starting deployment of "Sricluster-testEAP6v1.0.war" (runtime-name:
"Sricluster-testEAP6v1.0.war")
14:16:20,806 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876:
Starting deployment of "Sricluster-testEAP6v1.1.war" (runtime-name:
"Sricluster-testEAP6v1.1.war")
14:16:20,868 INFO
[org.jboss.as.server.deployment.scanner] (MSC service thread 1-2)
JBAS015012: Started FileSystemDeploymentService for directory
/jboss/JBOSSeap63SERVER1/standalone/deployments
14:16:20,873 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876:
Starting deployment of "sample.war" (runtime-name:
"sample.war")
14:16:20,875 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876:
Starting deployment of "cluster-test.war" (runtime-name:
"cluster-test.war")
14:16:20,880 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876:
Starting deployment of "SriWARV1.0.war" (runtime-name:
"SriWARV1.0.war")
14:16:20,885 INFO [org.jboss.as.server.deployment]
(MSC service thread 1-2) JBAS015876: Starting deployment of
"Sricluster-testEAP6.war" (runtime-name:
"Sricluster-testEAP6.war")
14:16:20,995 INFO
[org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052:
Starting JBoss Web Services - Stack CXF Server 4.3.4.Final-redhat-1
14:16:21,660 INFO
[org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening
on 0.0.0.0:9999
14:16:21,667 INFO
[org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening
on 0.0.0.0:4447
14:16:22,127 INFO
[org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2)
JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
14:16:23,634 INFO
[org.jboss.web] (ServerService Thread Pool -- 51) JBAS018210: Register web
context: /sample
14:16:23,639 INFO
[org.jboss.web] (ServerService Thread Pool -- 49) JBAS018210: Register
web context: /SriWARV1.0
14:16:24,551 INFO
[org.infinispan.factories.GlobalComponentRegistry] (ServerService Thread
Pool -- 49) ISPN000128: Infinispan version: Infinispan 'Delirium' 5.2.10.Final
14:16:24,735 INFO
[org.infinispan.factories.TransactionManagerFactory] (ServerService
Thread Pool -- 52) ISPN000161: Using a batchMode transaction manager
14:16:24,742 INFO
[org.infinispan.factories.TransactionManagerFactory] (ServerService
Thread Pool -- 51) ISPN000161: Using a batchMode transaction manager
14:16:24,743 INFO
[org.infinispan.factories.TransactionManagerFactory] (ServerService
Thread Pool -- 53) ISPN000161: Using a batchMode transaction manager
14:16:24,743 INFO
[org.infinispan.factories.TransactionManagerFactory] (ServerService
Thread Pool -- 48) ISPN000161: Using a batchMode transaction manager
14:16:24,748 INFO
[org.infinispan.factories.TransactionManagerFactory] (ServerService
Thread Pool -- 50) ISPN000161: Using a batchMode transaction manager
14:16:25,480 INFO
[org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool --
48) ISPN000031: MBeans were successfully registered to the platform MBean
server.
14:16:25,477 INFO [org.infinispan.jmx.CacheJmxRegistration]
(ServerService Thread Pool -- 52) ISPN000031: MBeans were successfully
registered to the platform MBean server.
14:16:25,478 INFO
[org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool --
53) ISPN000031: MBeans were successfully registered to the platform MBean
server.
14:16:25,479 INFO
[org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool --
51) ISPN000031: MBeans were successfully registered to the platform MBean
server.
14:16:25,476 INFO
[org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool --
50) ISPN000031: MBeans were successfully registered to the platform MBean
server.
14:16:25,490 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 48)
JBAS010281: Started default-host/Sricluster-testEAP6v1.1 cache from web
container
14:16:25,491 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 50)
JBAS010281: Started default-host/Sricluster-testEAP6 cache from web container
14:16:25,491 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 51)
JBAS010281: Started local-web cache from web container
14:16:25,498 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 53)
JBAS010281: Started default-host/cluster-test cache from web container
14:16:25,504 INFO
[org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 52)
JBAS010281: Started default-host/Sricluster-testEAP6v1.0 cache from web
container
14:16:25,538 INFO
[org.jboss.web] (ServerService Thread Pool -- 53) JBAS018210: Register
web context: /Sricluster-testEAP6
14:16:25,543 INFO
[org.jboss.web] (ServerService Thread Pool -- 48) JBAS018210: Register
web context: /Sricluster-testEAP6v1.1
14:16:25,552 INFO
[org.jboss.web] (ServerService Thread Pool -- 50) JBAS018210: Register
web context: /Sricluster-testEAP6v1.0
14:16:25,553 INFO
[org.jboss.web] (ServerService Thread Pool -- 52) JBAS018210: Register
web context: /cluster-test
14:16:25,913 INFO
[org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559:
Deployed "Sricluster-testEAP6.war" (runtime-name :
"Sricluster-testEAP6.war")
14:16:25,914 INFO
[org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559:
Deployed "Sricluster-testEAP6v1.1.war" (runtime-name : "Sricluster-testEAP6v1.1.war")
14:16:25,914 INFO
[org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559:
Deployed "cluster-test.war" (runtime-name :
"cluster-test.war")
14:16:25,915 INFO
[org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559:
Deployed "SriWARV1.0.war" (runtime-name : "SriWARV1.0.war")
14:16:25,920 INFO
[org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559:
Deployed "Sricluster-testEAP6v1.0.war" (runtime-name :
"Sricluster-testEAP6v1.0.war")
14:16:25,921 INFO
[org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559:
Deployed "sample.war" (runtime-name : "sample.war")
14:16:26,005 INFO
[org.jboss.as] (Controller Boot Thread) JBAS015961: Http management
interface listening on http://0.0.0.0:9990/management
14:16:26,005 INFO
[org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console
listening on http://0.0.0.0:9990
14:16:26,012 INFO
[org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.3.3.GA
(AS 7.4.3.Final-redhat-2) started in 17513ms - Started 495 of 523 services (87
services are lazy, passive or on-demand)
[disconnected /] connect
Hello Sir,
ReplyDeleteCan you please explain... why below error getting while connecting to CLI.
[jbossadm@localhost bin]$ ./jboss-cli.sh
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /] connect
The controller is not available at localhost:9999: java.net.ConnectException: JBAS012174: Could not connect to remote://localhost:9999. The connection failed: JBAS012174: Could not connect to remote://localhost:9999. The connection failed: Connection refused
[disconnected /]
[disconnected /]
i got above error... but after some time it resolved automatically.