[JBoss JIRA] (WFCORE-3609) Fix milliseconds format in configration changes operation date
by ehsavoie Hugonnet (JIRA)
ehsavoie Hugonnet created WFCORE-3609:
-----------------------------------------
Summary: Fix milliseconds format in configration changes operation date
Key: WFCORE-3609
URL: https://issues.jboss.org/browse/WFCORE-3609
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 3.1.0.Final
Reporter: ehsavoie Hugonnet
Assignee: ehsavoie Hugonnet
Priority: Minor
[5:56 PM] Harald Pehl: @here I noticed that the operation-date attribute for /subsystem=core-management/service=configuration-changes:list-changes has sometimes a millisecond part, sometimes not
[5:56 PM] Harald Pehl:
[standalone@localhost:9991 /] /subsystem=core-management/service=configuration-changes:list-changes
{
"outcome" => "success",
"result" => [
{
"operation-date" => "2018-02-14T16:42:09.856Z",
"access-mechanism" => "HTTP",
"remote-address" => "/172.18.0.1",
"outcome" => "success",
"operations" => [{
"blocking" => false,
"operation" => "reload",
"address" => [],
"operation-headers" => {
"access-mechanism" => "HTTP",
"caller-type" => "user"
}
}]
},
{
"operation-date" => "2018-02-14T16:34:20Z",
"access-mechanism" => "HTTP",
"remote-address" => "/172.18.0.1",
"outcome" => "success",
"operations" => [{
"operation" => "composite",
"address" => [],
"steps" => [{
"name" => "statistics-enabled",
"value" => true,
"operation" => "write-attribute",
"address" => [("subsystem" => "undertow")]
}],
"operation-headers" => {
"access-mechanism" => "HTTP",
"caller-type" => "user"
}
}]
}
]
}
[5:56 PM] Harald Pehl: This makes it very hard to parse the date in the client
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3576) deployment is not accessible in runtime when deployed with runtime-name not using .war extension
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3576?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-3576:
------------------------------------------
I have a vague recollection of some other discussion where the question came up of whether it was feasible to detect that no DUP handled a deployment. But I see it wasn't in that wildfly-dev thread, and I don't see it elsewhere in a search of my mail. Maybe it never happened or was some brief chat. Anyway, perhaps that wildfly-dev thread is a good place to check into that.
> deployment is not accessible in runtime when deployed with runtime-name not using .war extension
> ------------------------------------------------------------------------------------------------
>
> Key: WFCORE-3576
> URL: https://issues.jboss.org/browse/WFCORE-3576
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Deployment Scanner, Domain Management
> Affects Versions: 4.0.0.Alpha9
> Reporter: Jan Stourac
> Assignee: Chao Wang
>
> According to the folowing [blog-post|https://developer.jboss.org/thread/221251], when using custom --name or --runtime-name for deployment, the file extension (.war, .jar, .ear,...) need to be included so server can distinguish type of deployment somehow.
> Currently there is no such check - when I try to deploy any .war app using either web-console or CLI with my custom '\-\-runtime-name' and/or '\-\-name' without .war suffix, server does not complain anyhow:
> {code}
> deploy --runtime-name=alice --name=bob /tmp/eve.war
> {code}
> Message in server log:
> {code}
> 17:30:48,469 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "bob" (runtime-name: "alice")
> 17:30:48,499 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0010: Deployed "bob" (runtime-name : "alice")
> {code}
> Although, when I try to access content of the war app via URL, I get only {{404 Not found}} HTTP response. Also I cannot see any deployment content when browsing via CLI:
> {code}
> /deployment=bob/subsystem=undertow/...
> {code}
> Even when I raise logging level to DEBUG, I can see no suspicious messages that deployed app has not been completely deployed.
> If such suffix is required, we need to inform user about it. We need to update description text for '\-\-name' and '\-\-runtime-name' atributes of deploy command in CLI (see {{deploy --help}}). Also when no such suffix is provided (and/or we fail to distinguish type of deployment in a different way) we need to print error message that deploy operation was not completely successful so customer is aware of it right-away.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months