Running Prime 3.0.2 with the latest device pack. Able to poke around the APIs and gather basic information, however, when trying to use groups/UserDefinedGroups as described in the API documentation, received the following error:
Request: https://PRIME/webacs/api/v1/op/groups/userDefinedGroups
<?xml version="1.0" ?>
<errorDocument>
<httpResponseCode>500</httpResponseCode>
<httpMethod>GET</httpMethod>
<exception>java.lang.NullPointerException</exception>
<uriPath>op/groups/userDefinedGroups</uriPath>
<queryParams>{}</queryParams>
</errorDocument>
saw one reference that even though some attributes are marked as optional, at least one is required so ried the following, as well:
Request: https://PRIME/webacs/api/v1/op/groups/userDefinedGroups?.groupType=NETWORK_DEVICE
<?xml version="1.0" ?>
<errorDocument>
<httpResponseCode>500</httpResponseCode>
<httpMethod>GET</httpMethod>
<message>com.cisco.xmp.web.PresentationException: Unrecognized control query-param groupType with value NETWORK_DEVICE.-PRS-108</message>
<exception>com.cisco.xmp.web.XMPWebApplicationException: com.cisco.xmp.web.PresentationException: Unrecognized control query-param groupType with value NETWORK_DEVICE.-PRS-108</exception>
<uriPath>op/groups/userDefinedGroups</uriPath>
<queryParams>{.groupType=[NETWORK_DEVICE]}</queryParams>
</errorDocument>
Request: https://PRIME/webacs/api/v1/op/groups/userDefinedGroups?.noAlarms=true
<?xml version="1.0" ?>
<errorDocument>
<httpResponseCode>500</httpResponseCode>
<httpMethod>GET</httpMethod>
<message>com.cisco.xmp.web.PresentationException: Unrecognized control query-param noAlarms with value true.-PRS-108</message>
<exception>com.cisco.xmp.web.XMPWebApplicationException: com.cisco.xmp.web.PresentationException: Unrecognized control query-param noAlarms with value true.-PRS-108</exception>
<uriPath>op/groups/userDefinedGroups</uriPath>
<queryParams>{.noAlarms=[true]}</queryParams>
</errorDocument>
Trying to create location groups based on site codes contained in device hostnames (200+) .
The groupType and noAlarms parameters for these resources are not preceded with a ".", so that's why you're receiving the last two errors. As far as the first error, we did see one issue where this service would return a 500 NullPointerException error, but we root caused that issue and fixed it all during the development of 3.0.0. I'm not familiar with what might be causing this 500 error you are seeing now.
Has this behavior just started happening recently.. After applying a patch.
If you're still seeing this behavior can you please do the following: (1) login to the UI (with administrative) privileges and go to Administration > Logging; (2) reproduce the 500 error; (3) download the logs just after reproducing the issue; (4) contact me via email (my address is in my profile) and we can setup a secure exchange of the log bundle.
Tried without the "." (https://PRIME/webacs/api/v1/op/groups/userDefinedGroups?noAlarms=true) and it did got the information expecting. This is a viable workaround as the the alarm status is not important for this task. However, if you leave off the "?noAlarms=true" still get a 500.
Comments
0 comments
Please sign in to leave a comment.