Bug 1006246

Summary:	Executing a reload operation using the mgmt protocol results in a communication error
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Emanuel Muckenhuber <emuckenh>
Component:	Domain Management	Assignee:	Brian Stansberry <brian.stansberry>
Status:	CLOSED EOL	QA Contact:	Petr Kremensky <pkremens>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.0, 6.1.0, 6.1.1	CC:	brian.stansberry, cdewolf, dandread, istudens, myarboro, ochaloup, vtunka
Target Milestone:	---
Target Release:	TBD EAP 6
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-19 12:49:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	970482, 1530597

Description Emanuel Muckenhuber 2013-09-10 10:01:07 UTC

Description of problem:

Executing a reload operation using the native mgmt API sometimes results in a channel closed error. Upstream already has some better handling for handling this which should be ported back to EAP6.

Comment 1 Ivo Studensky 2013-09-25 14:47:38 UTC

Relevant PR:

https://github.com/jbossas/jboss-eap/pull/464

Comment 5 Petr Kremensky 2013-12-06 11:04:15 UTC

Trying to reproduce this with latest bits I can still run into exception from WFLY-164. 

How to reproduce:
 - get ochaloupka's reproducer from https://github.com/ochaloup/jboss-dmr-test/blob/master
 - update pom.xml to use latest bits 7.3.0.Final-redhat-14
 - start standalone
 - run a few times: mvn install exec:java -Dexec.mainClass="ochaloup.ClientReload"

I can still see the same exception as in WFLY-164

Comment 11 Dimitris Andreadis 2015-02-03 21:03:06 UTC

re-assign Emanuel's assigned bugs to Brian.