[jboss-jira] [JBoss JIRA] (WFCORE-1524) Scanner deployment failing at boot passes readiness/liveness checks

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry moved CLOUD-647 to WFCORE-1524:
------------------------------------------------

           Project: WildFly Core  (was: Cloud Enablement)
               Key: WFCORE-1524  (was: CLOUD-647)
          Workflow: GIT Pull Request workflow   (was: CDW v1)
       Component/s: Deployment Scanner
                    Domain Management
                        (was: EAP7)
    Target Release:   (was: 1.3.1.GA)
     Fix Version/s:     (was: 1.3.1.GA)


> Scanner deployment failing at boot passes readiness/liveness checks
> -------------------------------------------------------------------
>
>                 Key: WFCORE-1524
>                 URL: https://issues.jboss.org/browse/WFCORE-1524
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Deployment Scanner, Domain Management
>         Environment: brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/jboss-eap-7/eap70-openshift:1.3-11
>            Reporter: Marek Schmidt
>
> During larger scale-ups (e.g. from 1 to 6 on nodes under load) deployments sometimes fail with "org.infinispan.util.concurrent.TimeoutException: Replication timeout for foo-1-xxxxx".  
> That by itself is expected with the default timeouts, however, the problem is that such failed deployments pass the default EAP readiness and liveness checks, which results in HTTP 404 responses.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)