[
https://issues.apache.org/jira/browse/GEODE-7077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927053#comment-16927053
]
Jinmei Liao commented on GEODE-7077:
------------------------------------
This is bug in "create" pdx the 2nd time when there is no server running. This
bug is fixed now. Will put off "update pdx" in a future effort.
> POST pdx can not update the pdx config when a server is running
> ---------------------------------------------------------------
>
> Key: GEODE-7077
> URL: https://issues.apache.org/jira/browse/GEODE-7077
> Project: Geode
> Issue Type: Improvement
> Components: management
> Reporter: Gang Yan
> Assignee: Darrel Schneider
> Priority: Major
>
> For REST API V2 for management,
> I had one locator and one server. I did a post pdx and it worked. I then
> tried doing it again and it failed like so:
> 409 Error: Conflict
> {
> "statusCode": "ENTITY_EXISTS",
> "statusMessage": "Pdx 'PDX' already exists on member(s) server1."
> }
> Note that "409" is not documented in swagger.
> I would expect to be able to update the pdx config with the same type of
> message I get on a create (that if a server is running it needs to be
> restarted).
> If I stopped server1 then the POST worked with a 201:
> {
> "statusCode": "OK",
> "statusMessage": "Successfully updated configuration for cluster.",
> "uri": "/management/experimental/configurations/pdx"
> }
> I think POST pdx create and update should be consistent with each other. They
> should both either force you to stop a running server before you can do the
> op, or they should both support being done when a server is running.
> *TODO*
> # update the method to be put from post, the response will be 200 when
> everything runs well
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
