JBoss watches 비활성화

JBoss EAP 7.0.x 버전 사용 시에 tail을 사용하여 로그를 확인 할경우 또는 기동시에


ERROR [io.undertow] (MSC service thread 1-8:) UT005024: Could not register resource change listener for caching resource manager, automatic invalidation of cached resource will not work: java.lang.RuntimeException: java.io.IOException: User limit of inotify watches reached
    at org.xnio.nio.WatchServiceFileSystemWatcher.watchPath(WatchServiceFileSystemWatcher.java:183)
    at io.undertow.server.handlers.resource.PathResourceManager.registerResourceChangeListener(PathResourceManager.java:191)
    at org.wildfly.extension.undertow.deployment.ServletResourceManager.registerResourceChangeListener(ServletResourceManager.java:82)
    at io.undertow.server.handlers.resource.CachingResourceManager.<init>(CachingResourceManager.java:64)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:584)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:283)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: User limit of inotify watches reached
    at sun.nio.fs.LinuxWatchService$Poller.implRegister(LinuxWatchService.java:264)
    at sun.nio.fs.AbstractPoller.processRequests(AbstractPoller.java:260)
    at sun.nio.fs.LinuxWatchService$Poller.run(LinuxWatchService.java:329)


라는 메시지를 간혈적으로 보일경우가 있다
위 메시지를 Jboss 설정에서 default로 watches를 사용하고 있는데
이 watches를 비활성 하기 위해서는 JAVA_OPTS를 추가해야 한다.


"$JAVA_OPTS -Dio.undertow.disable-file-system-watcher=true"

Jboss EAP 7.0.0 패치 방법

데모환경

OS version: CentOS Linux Release 7.3

Jboss EAP version: Jboss EAP 7.0.0 GA

Jboss EAP Server Home: /was/jboss/jboss-eap-7.0

Patch Info: 7.0.8 patch

Browser: google chrome

https://access.redhat.com 접속

Jboss version, Patch 정보 확인

Command Line Interface 사용(이하 CLI)

$ ./jboss-cli.sh --controller=127.0.0.1:9990 –connect

[standalone@192.168.56.101:9990 /] patch info  # 버전확인

Version:             7.0.0.GA

Cumulative patch ID: base    

One-off patches:     none    

[standalone@192.168.56.101:9990 /] patch --help # 명령어 옵션 확인

SYNOPSIS

    patch <action> <action_arguments>*

  where <action> can be

    apply           - apply a patch

    history         - display the patching history

    info            - information about the active patches

    rollback        - rollback a patch that has been applied

    inspect         - fetch and print key information from the patch.xml of the specified patch file 

[standalone@192.168.56.101:9990 /] patch apply /installFile/jboss-eap-7.0.8-patch.zip # 명령어 및 패치파일 적용

{

    "outcome" : "success",

    "response-headers" : {

        "operation-requires-restart" : true,

        "process-state" : "restart-required"

    }

}

[standalone@192.168.56.101:9990 /] shutdown --restart=true # 재기동으로 확실하게 적용

[standalone@192.168.56.101:9990 /] patch rollback --reset-configuration=false # 패치 되돌리기

{

    "outcome" : "success",

    "response-headers" : {

        "operation-requires-restart" : true,

        "process-state" : "restart-required"

    }

}

[standalone@192.168.56.101:9990 /] shutdown --restart=true # 재기동으로 확인


JBoss 기동시 맨 아래 버전 정보가 나온다.


01:12:20,849 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) started in 5868ms - Started 267 of 553 services (371 services are lazy, passive or on-demand)