ExtendedException: Type '500' thrown in file 'c:\jws\engine-common-ws\src\server\appmanagement.cpp'

[Huiying]

Hi

ExtendedException: Type '500' thrown in file 'c:\jws\engine-common-ws\src\server\appmanagement.cpp' in function 'CTheServer::GetDataModelMetadataRest_impl' on line '560'. Message: 'Internal Server Error' and additional debug info: 'get metadata'

We have 200-300 above error messages each day from engine services of most nodes. Only 2 newly added nodes don't have that (yet).
Can you give me some hints where to investigate further?

Best regards,
Susan

[Huiying · Accepted solution]

Now AppMetadataAnalyzer has all data. Issue resolved.
Here is summary of this issue.
The error messages appear because AppMetadataAnalyzer tried to retrieve app metadata from rim node where apps were not loadbalanced to.
Solution: remove the rim nodes from AppMetadataAnalyzer's virtual proxy's load balancing nodes list.

Big thank to @rzenere_avvale !!

[rzenere_avvale]

Hey Susan,

great that the errors are not showing anymore. I'm still confused why you had an incremental number of errors, but having solved the issue is still good enough.
Unluckily no, I don't have anymore clues about the 0RAM footprint. I would suggest to try to perform manually the same extraction as Qlik does (you should be able to see in the log file the precise URL that Qlik uses)

Riccardo

[Huiying]

I assume increase in number of error probably because we constantly have new customers & new apps..
What do you mean by 'perform manually the same extraction'?

[rzenere_avvale]

If you export the reload log, you should find a part of the script where a call like this is performed: 

Note: in your log you (probably) won't find anything with win, because it is the prefix of my Windows virtual proxy.

Find the row with one of those apps that have no footprint/... and, from your browser, call the same url.
This way you should be able to obtain the same metadata as Qlik does while reloading.

At this point, I can think to three scenarios:

1. The call returns no metadata (I would expect an error): no reload has been performed for the app (or, but I'm not sure about this one, it has been imported from another environment)
2. The call returns metadata but no info about tables/fields is there: that could be an app that has been reloaded in your environment but at the end of the reload had no data (i.e. an ETL which reads from a source and then stores data in QVD format and drops it from the app)
3. The call returns metadata and you have all the info: this should be fine for App Metadata Analyzer 

Riccardo

[Huiying]

Thank you Riccardo
I'll use this method next time when AppMetadataAnalyzer gives 0 RAM footprint.
Big thank to your help! 🙂

Best regards,
Susan