Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-16301

Intermittent IllegalStateException during server stop from org.wildfly.extension.microprofile.[metrics|health].http-context service

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • None
    • 7.3.0.CD15
    • None
    • None
    • Hide

      I have created a reproducer repro.sh for this issue:

      1. download and extract EAP
      2. cd to its home directory
      3. copy repro.sh script there
      4. execute: bash repro.sh
      5. wait until during one of the iteration the exception occurs (when I tried on my machine, it took from 2 till 20 iterations to hit this)
      Show
      I have created a reproducer repro.sh for this issue: download and extract EAP cd to its home directory copy repro.sh script there execute: bash repro.sh wait until during one of the iteration the exception occurs (when I tried on my machine, it took from 2 till 20 iterations to hit this)

    Description

      During execution of one ouf our internal testsuites, I can see intermittent following IllegalStateException during the server stop:

      20:44:27,526 WARN  [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000004: Failure during stop of service org.wildfly.extension.microprofile.metrics.http-context: java.lang.IllegalStateException
      	at org.jboss.as.domain.http.server.ManagementHttpServer.removeContext(ManagementHttpServer.java:234)
      	at org.jboss.as.server.mgmt.UndertowHttpManagementService$1.removeContext(UndertowHttpManagementService.java:144)
      	at org.wildfly.extension.microprofile.metrics.MetricsContextService.stop(MetricsContextService.java:130)
      	at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1794)
      	at org.jboss.msc.service.ServiceControllerImpl$StopTask.execute(ServiceControllerImpl.java:1763)
      	at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
      	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
      	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
      	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
      	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1364)
      	at java.lang.Thread.run(Thread.java:748)
      

      longer output is attached in repro_log.txt.

      Apart from the previous one, I can sometimes see also following one (although not so frequently):

      16:28:10,365 WARN  [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000004: Failure during stop of service org.wildfly.extension.microprofile.health.http-context: java.lang.IllegalStateException
      	at org.jboss.as.domain.http.server.ManagementHttpServer.removeContext(ManagementHttpServer.java:234)
      	at org.jboss.as.server.mgmt.UndertowHttpManagementService$1.removeContext(UndertowHttpManagementService.java:144)
      	at org.wildfly.extension.microprofile.health.HealthContextService.stop(HealthContextService.java:80)
      	at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1794)
      	at org.jboss.msc.service.ServiceControllerImpl$StopTask.execute(ServiceControllerImpl.java:1763)
      	at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
      	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
      	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
      	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
      	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1364)
      	at java.lang.Thread.run(Thread.java:748)
      

      These exceptions occur randomly after the server is terminated via CTRL+C (SIGINT) signal. Before the termination, there happened some configuration changes in elytron subsystem - although I am not sure whether it is related anyhow. See repro.sh to check what is going on and to try it by yourself.

      I know this is a long shot, although, recently there was reported WFLY-11603 and also there is reported WFLY-11387 which looks similar.

      NOTE: with recent build of WildFly upstream 7ed935975189dca0068c3d0a0af71611df26f277, I was not able to reproduce the issue anymore. Due to the nature of the issue, I cannot say whether it was actually fixed or whether the conditions simply changed and race-condition is just less frequent now.

      Attachments

        1. repro_log.txt
          12 kB
        2. repro.sh
          2 kB

        Issue Links

          Activity

            People

              jmesnil1@redhat.com Jeff Mesnil
              jstourac@redhat.com Jan Stourac
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: