Bug 1381195 - Middleware- Unable to Deploy war in EAP server
Summary: Middleware- Unable to Deploy war in EAP server
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: cfme-future
Assignee: Josejulio Martínez
QA Contact: Sunil Kondkar
URL:
Whiteboard: Hawkular
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-03 11:40 UTC by Prachi
Modified: 2019-01-10 15:27 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-10 15:27:08 UTC
Category: ---
Cloudforms Team: Middleware
Target Upstream Version:
mmahoney: needinfo-


Attachments (Terms of Use)
Deployment initiated (165.40 KB, image/png)
2016-10-03 11:40 UTC, Prachi
no flags Details
EAP server log (32.50 KB, text/plain)
2016-10-03 11:42 UTC, Prachi
no flags Details

Description Prachi 2016-10-03 11:40:53 UTC
Created attachment 1206806 [details]
Deployment initiated

Description of problem:

Not able to Deploy war file in EAP server using CFME, EAP server logs is showing Error


Version-Release number of selected component (if applicable): DR4


How reproducible:

Steps to Reproduce:
1. Navigate to Middleware >> servers
2. Click on "Deployments">> Add Deployments
3. Select war file and add

Actual results:

CFME UI shows Deployment initiated, but in Server deployments new war file is not added. 
EAP server logs are showing ERROR:

****************************************
2016-10-03 07:18:34,895 ERROR [org.hawkular.agent.monitor.cmd.FeedCommProcessor] (OkHttp http://prachi-docker-hawkular-service.bc.jonqe.lab.eng.bos.redhat.com:8080/hawkular/command-gateway/feed/db949be9-c5c1-4c29-b28e-d4bb2cc59004) HAWKMONITOR010033: Failed to execute command [?] for server: java.lang.RuntimeException: Cannot deserialize stream with object [org.hawkular.cmdgw.api.DeployApplicationRequest]
	at org.hawkular.cmdgw.api.ApiDeserializer.deserialize(ApiDeserializer.java:153)
	at org.hawkular.agent.monitor.cmd.FeedCommProcessor.onMessage(FeedCommProcessor.java:328)
	at com.squareup.okhttp.internal.ws.RealWebSocket$1.onMessage(RealWebSocket.java:62)
	at com.squareup.okhttp.internal.ws.WebSocketReader.readMessageFrame(WebSocketReader.java:242)
	at com.squareup.okhttp.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:103)
	at com.squareup.okhttp.internal.ws.RealWebSocket.readMessage(RealWebSocket.java:97)
	at com.squareup.okhttp.ws.WebSocketCall.createWebSocket(WebSocketCall.java:153)
	at com.squareup.okhttp.ws.WebSocketCall.access$000(WebSocketCall.java:40)
	at com.squareup.okhttp.ws.WebSocketCall$1.onResponse(WebSocketCall.java:98)
	at com.squareup.okhttp.Call$AsyncCall.execute(Call.java:177)
	at com.squareup.okhttp.internal.NamedRunnable.run(NamedRunnable.java:33)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: Stream cannot be converted to JSON object of type [class org.hawkular.cmdgw.api.DeployApplicationRequest]
	at org.hawkular.bus.common.AbstractMessage.fromJSON(AbstractMessage.java:115)
	at org.hawkular.cmdgw.api.ApiDeserializer.deserialize(ApiDeserializer.java:150)
	... 13 more

****************************************


Expected results: wat file should successfully deployed in EAP as well as shows up in CFME middleware deployments.


Additional info:

Comment 2 Prachi 2016-10-03 11:42:41 UTC
Created attachment 1206807 [details]
EAP server log

Comment 4 Heiko W. Rupp 2016-10-28 09:04:07 UTC
Can this be reproduced with DR7? I see people left and right deploying things.

Comment 6 Heiko W. Rupp 2016-11-04 09:35:49 UTC
Assigning to Ruben, as he is already looking into BZ1390748, which may be related/a dup

Comment 7 Josejulio Martínez 2016-11-04 23:09:01 UTC
I couldn't reproduce this one.

BZ1390748 is specific to EAP in domain mode, thus not related to this one.

EAP output:
*********************************************
17:03:42,944 INFO  [org.hawkular.agent.monitor.cmd.AbstractResourcePathCommand] (OkHttp http://localhost:8080/hawkular/command-gateway/feed/7abf5722-5a2d-4232-92cc-3849a9cd3d73) HAWKMONITOR010065: Received request to perform [Deploy] on a [Application] given by inventory path [/t;hawkular/f;7abf5722-5a2d-4232-92cc-3849a9cd3d73/r;Local~~]
17:03:43,221 INFO  [org.jboss.as.repository] (OkHttp http://localhost:8080/hawkular/command-gateway/feed/7abf5722-5a2d-4232-92cc-3849a9cd3d73) WFLYDR0001: Content added at location /home/josejulio/Aplicaciones/redhat/jboss-eap-7.0/standalone/data/content/ce/d0b39ce5b4a65913143ffc1b67dc7b41f25eaa/content
17:03:43,359 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "cfme_test_ear_middleware.ear" (runtime-name: "cfme_test_ear_middleware.ear")
17:03:43,621 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: "cfme_test_nested_war_middleware.war")
17:03:47,139 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 73) WFLYUT0021: Registered web context: /cfme_test_nested_war_middleware
17:03:47,634 INFO  [org.jboss.as.server] (OkHttp http://localhost:8080/hawkular/command-gateway/feed/7abf5722-5a2d-4232-92cc-3849a9cd3d73) WFLYSRV0010: Deployed "cfme_test_ear_middleware.ear" (runtime-name : "cfme_test_ear_middleware.ear")
*********************************************

Comment 8 Heiko W. Rupp 2016-11-10 08:40:21 UTC
Can you check again please?

Comment 9 Mike Foley 2016-11-15 13:23:08 UTC
From: "Michael Foley" <mfoley>
To: "Prachi Yadav" <pyadav>
Cc: "Heiko W.Rupp" <hrupp>, "jon-qa-list" <jon-qa-list>
Sent: Tuesday, November 15, 2016 8:22:26 AM
Subject: Question on this bug...

Hi,

Question on this bug ...

 https://bugzilla.redhat.com/show_bug.cgi?id=1381195#c7


This is valid in DR8?  This would be a blocker if it still exists ...

Michael

Comment 10 Sunil Kondkar 2016-11-15 15:19:05 UTC
Verified on DR8.

Started EAP7 standalone using quick-start guide (container). Deployed couple of war files. There is no error in EAP7 logs after deploying war files  and the deployed wars are shown enabled in deployment list.

Also verified deploying couple of war files on EAP7 standalone that was started manually. There are no errors in EAP7 logs and war files are listed and enabled in deployment list.

This issue can be closed as does not exist anymore in DR8.

Comment 11 Sunil Kondkar 2016-11-15 15:23:29 UTC
Marking verified


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