[jboss-jira] [JBoss JIRA] (WFCORE-1738) Hint when versions are out-of-date pending restart
[
https://issues.jboss.org/browse/WFCORE-1738?page=com.atlassian.jira.plugi...
]
Marek Kopecký commented on WFCORE-1738:
---------------------------------------
Sure.
Command for apply the patch: {{patch apply ../../jboss-eap-7.0.1-patch.zip}}
Command for get version info: version
Example of logs:
{noformat}
[mkopecky@localhost bin]$ ./jboss-cli.sh -c
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny"
JBoss AS product: JBoss EAP 7.0.0.GA
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] patch apply ../../jboss-eap-7.0.1-patch.zip
{
"outcome" : "success",
"response-headers" : {
"operation-requires-restart" : true,
"process-state" : "restart-required"
}
}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny" // TODO
JBoss AS product: JBoss EAP 7.0.0.GA // TODO
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] :reload
{
"outcome" => "success",
"result" => undefined
}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny" // TODO
JBoss AS product: JBoss EAP 7.0.0.GA // TODO
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] :shutdown(restart=true)
{"outcome" => "success"}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.6.Final-redhat-1 "Kenny"
JBoss AS product: JBoss EAP 7.0.1.GA
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /]
{noformat}
Hint when versions are out-of-date pending restart
--------------------------------------------------
Key: WFCORE-1738
URL: https://issues.jboss.org/browse/WFCORE-1738
Project: WildFly Core
Issue Type: Feature Request
Components: CLI, Patching
Reporter: Marek Kopecký
Assignee: Alexey Loubyansky
Priority: Optional
I have a minor usability suggestion. It's merely informational but I think helpful.
When I was in the CLI tool to apply a version update patch (7.0.0 -> 7.0.1), I
wasn't yet aware that I needed to restart the server for it to take effect. So when I
afterward typed "version" to confirm the expected version bumps... well, they
did not. I was specifically looking to confirm a change in both fields "JBoss AS
release" and "JBoss AS product". With that said, it would be useful to add
something to the output indicating the information being displayed will no longer be
true.
Illustrated example. Notice the asterisks:
{code}
JBOSS_HOME: C:\dev\jboss-eap-7
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny"(*)
JBoss AS product: JBoss EAP 7.0.0.GA(*)
JAVA_HOME: c:\java\jdk1.8.0_45
java.version: 1.8.0_45
java.vm.vendor: Oracle Corporation
java.vm.version: 25.45-b02
os.name: Windows 7
os.version: 6.1
(*) Versions subject to change after patch takes effect at restart.
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)