Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1530597 - JDV Server reload/restart channel closed issue
JDV Server reload/restart channel closed issue
Status: CLOSED WONTFIX
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Integration, Documentation, Installer (Show other bugs)
6.4.0
Unspecified Unspecified
urgent Severity urgent
: GA
: 6.4.0
Assigned To: David Le Sage
Jan Stastny
: Documentation
Depends On: 1006246
Blocks:
  Show dependency treegraph
 
Reported: 2018-01-03 07:59 EST by Jan Stastny
Modified: 2018-02-01 03:40 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Sometimes you cannot reload the server using the management interface. This happens when the server is shutdown before it responds to the client, resulting in an IOException. This can also happen during installation, which can result in the installation process failing.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-02-01 03:40:14 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Full stacktrace from server (3.15 KB, text/plain)
2018-01-03 07:59 EST, Jan Stastny
no flags Details
Installer stacktrace (3.31 KB, text/plain)
2018-01-03 08:00 EST, Jan Stastny
no flags Details

  None (edit)
Description Jan Stastny 2018-01-03 07:59:36 EST
Created attachment 1376327 [details]
Full stacktrace from server

Description of problem:
There is an issue when reloading server via management interface. The root issue is that, the server is shutdown before it responds to the client, effectively resulting in IOException complaining 'Channel closed'.

It is reported for EAP in the BZ which is blocking this one.

We encountered the issue in two cases:
1. reloading the server explicitly via cli operation
2. during installation of the server

The use case 2. is more problematic, as it fails the installation.
As noted in the linked BZ, it has not been resolved on the server, but can be solved on client side. This approach might be adopted in the DV installer.

See both full server stacktrace and its appearance in installer logs in the attachements.
Comment 1 Jan Stastny 2018-01-03 08:00 EST
Created attachment 1376328 [details]
Installer stacktrace
Comment 5 David Le Sage 2018-01-08 18:03:27 EST
Added to release note errata as a known issue.

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