[
https://issues.jboss.org/browse/WFCORE-1524?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-1524:
------------------------------------------
From an IRC chat with Rob Cernich:
{code}
[11:17am] rcernich: bstansberry: quick question, we're seeing the cli return
deployment-info of failed for a deployment, but there's a .deployed file in the
deployments directory (eap7)
[11:17am] bstansberry: rcernich: hi rob
[11:17am] bstansberry: rcernich: that doesn’t sound right
[11:17am] rcernich: bstansberry: infinispan fails to start (times out) and thus the
deployment fails (sort of)
[11:18am] rcernich: bstansberry: the log includes "Deployed "ROOT.war"
(runtime-name: "ROOT.war")
[11:19am] bstansberry: rcernich: this is all during boot, right?
[11:19am] rcernich: bstansberry: yes
[11:19am] rcernich: bstansberry: here's a link to our issue:
https://issues.jboss.org/browse/CLOUD-615
[11:19am] rcernich: the log is attached
[11:20am] bstansberry: rcernich: ok, I *suspect* this is related to how failures are
handled during boot
[11:21am] rcernich: bstansberry: the deployment seems to fail, as eap is returning
404's for the app url's
[11:22am] bstansberry: rcernich: right; the problem AIUI is there is no .failed file,
right?
[11:22am] rcernich: bstansberry: correct (and you could say the entry in the log is
misleading as well)
[11:23am] bstansberry: rcernich: I’m going to clone that JIRA into WFCORE
{code}
Note Rob's comment about the logging, which is valid in addition to the issue with the
deployment marker file.
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
Assignee: ehsavoie Hugonnet
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)