본문 바로가기

WAS/JBoss&WildFly

[jboss 8.1] patch

728x90

기본 엔진은 당연하게도 patch가 걸려있지 않다.

로그에 적혀있듯, JBoss EAP 8.1이란 것을 금방 알아차릴 수 있다.

2026-04-09 15:28:42,569 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
2026-04-09 15:28:42,577 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://192.168.56.101:9990/management
2026-04-09 15:28:42,578 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://192.168.56.101:9990
2026-04-09 15:28:42,584 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 8.1 (WildFly Core 27.1.0.Final-redhat-00010) started in 11263ms - Started 329 of 738 services (498 services are lazy, passive or on-demand) - Server configuration file in use: standalone-ha.xml

 

JBoss EAP 8 이후부터 패치 방법이 달라졌는데,

이게 제일 하기 쉽길래 이거부터 해봤다.

※ 패치 시, JBoss 엔진 경로와 instance 별 configruration 경로에서 해당되는 standalone-*.xmlCOPY 떠두자. 

1. jboss-cli 실행
EAP_HOME/bin/jboss-cli.sh 혹은
INSTANCE_HOME/bin/jboss-cli.sh

2. 패치파일을 통해서 update 진행(offline 방식)
installer update --maven-repo-files=<An absolute or a relative path pointing to the local archive file that contains a maven repository>

e.g)
installer update --maven-repo-files=/sw/files/jboss-eap-8.1.4-maven-repository.zip

~~~

Would you like to proceed with preparing this update? [y/N]:y
The new installation is being prepared ...

The candidate server has been generated. To apply it, restart the server with 'shutdown --perform-installation' command.

 

 

 

3. 재기동
shutdown --perform-installation

[standalone@192.168.56.101:9990 /] shutdown --perform-installation
[137.102s][info][gc] GC(3) Pause Young (Normal) (G1 Evacuation Pause) 67M->23M(1024M) 14.326ms
The JBoss CLI session will be closed automatically to allow the server be updated. Once the server has been restarted, you can relaunch the JBoss CLI session.


[server.log 상황]
2026-04-09 15:32:45,685 INFO  [org.wildfly.channel.maven.VersionResolverFactory] (management-handler-thread - 1) Resolving channel metadata from Maven artifact org.jboss.eap.channels:eap-8.1:1.4.0.GA-redhat-00005
2026-04-09 15:32:45,685 INFO  [org.wildfly.channel.maven.VersionResolverFactory] (management-handler-thread - 1) Resolving channel metadata from Maven artifact org.jboss.eap.channels:eap-8.1:1.4.0.GA-redhat-00005
2026-04-09 15:32:45,929 INFO  [org.wildfly.prospero] (management-handler-thread - 1) PRSP000013: Found 410 updates
2026-04-09 15:32:45,929 INFO  [org.wildfly.prospero] (management-handler-thread - 1) PRSP000013: Found 410 updates
2026-04-09 15:32:50,149 INFO  [org.wildfly.prospero] (management-handler-thread - 1) PRSP000022: Listing subscribed channels
2026-04-09 15:32:50,149 INFO  [org.wildfly.prospero] (management-handler-thread - 1) PRSP000022: Listing subscribed channels
2026-04-09 15:32:50,250 INFO  [org.wildfly.prospero] (management-handler-thread - 1) PRSP000012: Checking available updates
2026-04-09 15:32:50,250 INFO  [org.wildfly.prospero] (management-handler-thread - 1) PRSP000012: Checking available updates
2026-04-09 15:32:50,260 INFO  [org.wildfly.channel.maven.VersionResolverFactory] (management-handler-thread - 1) Resolving channel metadata from Maven artifact org.jboss.eap.channels:eap-8.1:1.4.0.GA-redhat-00005
2026-04-09 15:32:50,260 INFO  [org.wildfly.channel.maven.VersionResolverFactory] (management-handler-thread - 1) Resolving channel metadata from Maven artifact org.jboss.eap.channels:eap-8.1:1.4.0.GA-redhat-00005
2026-04-09 15:32:50,453 INFO  [org.wildfly.prospero] (management-handler-thread - 1) PRSP000013: Found 410 updates
2026-04-09 15:32:50,453 INFO  [org.wildfly.prospero] (management-handler-thread - 1) PRSP000013: Found 410 updates
2026-04-09 15:32:50,456 INFO  [org.wildfly.prospero] (management-handler-thread - 1) PRSP000010: Building update candidate for /sw/jboss-eap-8.1
2026-04-09 15:32:50,456 INFO  [org.wildfly.prospero] (management-handler-thread - 1) PRSP000010: Building update candidate for /sw/jboss-eap-8.1

~~~

 

재기동 하는 사이에 나오는 server.log

 

재기동이 완료되면 8.1.$version 이 로그에 나오게 된다.(현재 환경은 8.1.4 패치를 걸고 난 뒤의 로그)
2026-04-09 15:34:54,328 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://192.168.56.101:9990
2026-04-09 15:34:54,350 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 8.1 Update 4.0 (WildFly Core 27.1.4.Final-redhat-00002) started in 10984ms - Started 329 of 738 services (498 services are lazy, passive or on-demand) - Server configuration file in use: standalone-ha.xml

 

패치 파일 크기가 300mb정도이지만, 패치 적용후의 디렉토리 용량은 약 3MB 증가했다.

[app@test11 sw]$ df -kh

[패치 전]
Filesystem             Size  Used Avail Use% Mounted on
devtmpfs               4.0M     0  4.0M   0% /dev
tmpfs                  1.8G     0  1.8G   0% /dev/shm
tmpfs                  732M   18M  714M   3% /run
/dev/mapper/rhel-root   17G   11G  6.6G  62% /
/dev/sda1              960M  491M  470M  52% /boot
tmpfs                  366M   56K  366M   1% /run/user/42
tmpfs                  366M   36K  366M   1% /run/user/1000

======
[패치 후]
Filesystem             Size  Used Avail Use% Mounted on
devtmpfs               4.0M     0  4.0M   0% /dev
tmpfs                  1.8G     0  1.8G   0% /dev/shm
tmpfs                  732M   18M  714M   3% /run
/dev/mapper/rhel-root   17G   11G  6.3G  64% /
/dev/sda1              960M  491M  470M  52% /boot
tmpfs                  366M   56K  366M   1% /run/user/42
tmpfs                  366M   36K  366M   1% /run/user/1000

[app@test11 sw]$ du -sh *
12M	domains
680K	domains_81
288M	jboss810.tar ## 빠른 원복을 위한 엔진 압축
291M	jboss-eap-8.1 ## 패치 적용된 엔진