Bug 1085915 - (6.2.x) In domain mode, doing a read-only operation with the CLI on a remote HC, sets the remote server in "restart-required" mode
Summary: (6.2.x) In domain mode, doing a read-only operation with the CLI on a remote ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management
Version: 6.2.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Tom Fonteyne
QA Contact: Petr Kremensky
URL:
Whiteboard:
Depends On: 1085913
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-09 15:56 UTC by Tom Fonteyne
Modified: 2017-10-10 00:18 UTC (History)
2 users (show)

Fixed In Version:
Clone Of: 1085913
Environment:
Last Closed: 2014-07-17 05:58:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-3237 0 Major Resolved doing a read-only operation with the CLI sets a server in "restart-required" mode 2016-11-10 04:58:37 UTC

Description Tom Fonteyne 2014-04-09 15:56:29 UTC
+++ This bug was initially created as a clone of Bug #1085913 +++

This BZ is meant to EAP 6.2.x branch


Setup a DC and a remote HC
Have a servergroup "slaves"

    create remote server
    /host=slave10/server-config=i2:add(group=slaves,socket-binding-group=full-ha-sockets)
    create a JVM on it
    /host=slave10/server-config=i2/jvm=default:add()

do a full restart of the domain (reload --host=slave10 is actually enough)
ls -l /host=slave10/server=i2
...
server-state running STRING

cd /host=slave10/server-config=i2/jvm=default
ls-l
....
cd ../../server=i2
ls -l
...
server-state restart-required STRING

If you do not "cd" into the jvm, then the state stays at "running". It is the physically going into the jvm that causes this.

workaround: do not use "cd"

Comment 5 Petr Kremensky 2014-07-17 05:58:16 UTC
This issue is reported against a version which is no longer maintained, which means that it will not receive a fix. As a result we are closing this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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