New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to read API metadata since version 24 in containers #3475
Comments
And if you spin up a 23.5 container (using hyperv) with the same username password etc - does it work then? |
Hi @freddydk, The 23.5 works like a charm:
I used the same script as above, with updated artifact URL:
The Output:
|
Any workarounds are welcome also until we get to root cause |
Same result after upgrading to 6.0.15. We're able to reproduce this in multiple environments, since it happens across our team. Browser just keeps loading with blank screen when trying to access metadata. |
Does the browser ask for authentication? |
I can also replicate this issue since moving to 24.0 version and using HyperV. Tried Chrome and Edge, on both I only get white screen that is loading forever without any output. Base app version is v. 24.0.16410.18056. |
Did you try without specifying a license file? |
Yes, same thing. |
I can repro this when using HyperV isolation. |
Thanks for the update Freddy! And we should try getting everyone to Win11 in the meantime. Glad that we came to the Root Cause. |
Just came across this issue as I wanted to create an issue myself right now for the problem that: if you create a bc v24 container in isolation mode hyperv and do not use SSL, you will not receive a response to API calls that return more than 50-60 result sets (tested with a custom table/api and 3 fields).
@freddydk could you update the label on this issue as it says Cannot repro. Perhaps this threshold of 50-60 records will guide us further in the investigation. Choose a table, maybe even a custom table and a custom API, and create 50 records. Send several GET requests to them => success. Fast. Without any problem. Some additional thoughts, remains to be seen if related to this issue:
EDIT: Perhaps it was just an unfortunate coincidence that the number of requests was in this range.
That should be it for now. Really curious what the cause of this strange problem is. |
Thanks @christianbraeunlich - that is indeed a strange bug... |
Since the switch to new BC 24.x containers we're unable to read API metadata that results in a simple timeout error. Same thing works perfectly in older versions of BC. It could be that it's also related to using hyperv now, as with 24 I had to change that.
The script I'm using:
The Output:
I've created the Web Service Access Key:
But the $metadata is giving me either Timeout error or ECONNRESET:
The text was updated successfully, but these errors were encountered: