uri is not absolute error in API job
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2019 04:15 AM
Hi,
I have some external java executables that make API calls to pull CMDB information.
They worked fine until Madrid upgrade, but now I get an error: java.lang.IllegalArgumentException: URI is not absolute
Has anyone any information about what might have changed in the API implementation ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-04-2019 03:33 AM
Nothing has changed in the API on SNs side - at least I know that we have integrations the query us from Java and have been running since way before Madrid. It looks like your request isn't being sent.
An absolute URI requires a scheme - any chance to log the request URI at the moment it is supposed to be sent?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-04-2019 04:07 AM
Hi Michael,
There is a lot of logging 🙂
The URI produced works perfectly well in a browser.
We are now working on the basis this is a Java issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-04-2019 04:40 AM
So you grab the URI from a log and it works in the browser? That's interesting...
Can you feed the complete URI to your Java code as a literal, so that it doesn't get modified at all before it's passed to whatever class makes the request?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-04-2019 10:03 AM
Hi Michael,
Thank you for replying and confirming nothing has changed.
It was a java issue related to versions and flavours (openJDK, Oracle).. We refactored and have a solution.
John
