Bug 1006246 - Executing a reload operation using the mgmt protocol results in a communication error
Summary: Executing a reload operation using the mgmt protocol results in a communicati...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management
Version: 6.0.0,6.1.0,6.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: TBD EAP 6
Assignee: Brian Stansberry
QA Contact: Petr Kremensky
URL:
Whiteboard:
Depends On:
Blocks: 970482 1530597
TreeView+ depends on / blocked
 
Reported: 2013-09-10 10:01 UTC by Emanuel Muckenhuber
Modified: 2019-08-19 12:49 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:49:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-164 0 Major Closed java.io.IOException Channel closed exception after several reload of server 2019-01-17 08:29:36 UTC

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.


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