Bug 1327093 - [GSS](6.4.z) Deployment issue after restart in JBoss EAP 6.4
Summary: [GSS](6.4.z) Deployment issue after restart in JBoss EAP 6.4
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.9
Assignee: Radovan Netuka
QA Contact: Martin Simka
URL:
Whiteboard:
Depends On:
Blocks: eap649-payload
TreeView+ depends on / blocked
 
Reported: 2016-04-14 09:35 UTC by Paramvir jindal
Modified: 2019-11-14 07:47 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-17 12:56:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-4985 0 Critical Resolved Deployment issue after restart in JBoss EAP 2018-11-12 17:33:30 UTC
Red Hat Issue Tracker WFCORE-64 0 Major Resolved Filesystem deployment scanner deployment failure removes unrelated deployments 2018-11-12 17:33:30 UTC
Red Hat Knowledge Base (Solution) 2261451 0 None None None 2016-05-23 18:21:03 UTC

Description Paramvir jindal 2016-04-14 09:35:54 UTC
Description of problem:

Because of one failed deployment (via copying the physical file into /deployments folder which should fail) other successfully deployed application (via CLI) is also getting undeployed in EAP 6.4.6 unlike EAP 6.3 where things are working fine.


Version-Release number of selected component (if applicable):
JBoss EAP 6.4

How reproducible:
Every time

Steps to Reproduce:
1. Start a EAP 6.4.x instance and then connect to the CLI
2. Deploy an working application via CLI.
3. Deploy a faulty application (deployment should fail may be because of missing dependency or something) by copying the application in "deployment" directory.
4. Restart the server.

Actual results:

Other successful deployments also got Undeployed because of one faulty deployment.

14:48:58,930 INFO  [org.jboss.web] (ServerService Thread Pool -- 30) JBAS018224: Unregister web context: /ClusterWebApp
14:48:58,932 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66) JBAS010282: Stopped default-host/ClusterWebAppfailing cache from web container
14:48:58,941 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment ClusterWebAppfailing.war (runtime-name: ClusterWebAppfailing.war) in 15ms
14:48:58,946 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 30) JBAS010282: Stopped default-host/ClusterWebApp cache from web container
14:48:58,953 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015877: Stopped deployment ClusterWebApp.war (runtime-name: ClusterWebApp.war) in 25ms
14:48:58,957 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 30) JBAS010282: Stopped local-web cache from web container
14:48:59,089 INFO  [org.jboss.as.repository] (DeploymentScanner-threads - 2) JBAS014901: Content removed from location /home/pjindal/Start/EAP_used/EAP6.4.0/jboss-eap-6.4/standalone/data/content/cb/16a87d23644fb166000b4b739ef12257b77326/content
14:48:59,090 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "ClusterWebApp.war" (runtime-name: "ClusterWebApp.war")
14:48:59,090 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "ClusterWebAppfailing.war" (runtime-name: "ClusterWebAppfailing.war")
 

Expected results:

Other successful Deployments should not be affected by one failed Deployment.


Additional info:

Comment 5 Jiří Bílek 2016-06-22 07:27:42 UTC
Verified with EAP 6.4.9.CP.CR1

Comment 6 Petr Penicka 2017-01-17 12:56:19 UTC
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.


Note You need to log in before you can comment on or make changes to this bug.