Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-5457

org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped during server shutdown

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Minor
    • None
    • 10.0.0.CR2
    • Clustering
    • None

    Description

      EAP 7.0.0.DR11
      Scenario: failover-http-session-shutdown-repl-sync, using graceful shutdown

      During server shutdown, perf19 logged this single-line error message few times:

      ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-18,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped

      Right after that the server stopped, see the log: 

      [JBossINF] �[0m�[0m06:40:01,917 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0004: Undertow 1.3.0.CR2 stopping
[JBossINF] �[0m�[0m06:40:01,917 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0208: Stopped subdeployment (runtime-name: clusterbench-ee7-web-passivating.war) in 10472ms
[JBossINF] �[0m�[31m06:40:01,916 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-18,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
[JBossINF] �[0m�[31m06:40:01,921 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-10,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
[JBossINF] �[0m�[31m06:40:01,917 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-20,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
[JBossINF] �[0m�[31m06:40:01,917 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-17,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
[JBossINF] �[0m�[31m06:40:01,917 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-13,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
[JBossINF] �[0m�[31m06:40:01,917 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-1,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
[JBossINF] �[0m�[31m06:40:01,922 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-8,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
[JBossINF] �[0m�[31m06:40:01,922 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-12,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
[JBossINF] �[0m�[0m06:40:01,928 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment clusterbench-ee7.ear (runtime-name: clusterbench-ee7.ear) in 10476ms
[JBossINF] �[0m�[31m06:40:01,917 ERROR [org.jgroups.blocks.RequestCorrelator] (OOB-19,ee,perf19) failed marshalling rsp (CacheNotFoundResponse): org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped
[JBossINF] �[0m�[0m06:40:01,970 INFO  [org.jboss.as] (MSC service thread 1-5) WFLYSRV0050: EAP 7.0.0.Alpha1 (WildFly Core 2.0.0.CR5) stopped in 10521ms
[JBossINF] �[0m
2015/10/02 06:40:02:479 EDT [DEBUG][RMI TCP Connection(12)-10.16.90.52] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Server is down.

      Server log
      http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-session-shutdown-repl-sync-150-sessions/6/console-perf19/

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-1216 org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped during server shutdown

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              rpelisse@redhat.com Romain Pelisse
              mvinkler1@redhat.com Michal Vinkler
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: