Closed Jef-VDD closed 4 months ago
Hi @Jef-VDD, this is the DNS Client caching that happens "everywhere" implicitly. There is caching inside the Java Runtime, there is multiple caching on OS level (depending on the OS the application is running on) and there is caching on the DNS Server your application is using. I think the maximum TTL is one hour, so it takes no longer then 1h until the cache is refreshed.
hth
Thanks for the quick response! I'm happy to have the confirmation that there is no caching by the peppol-smp-client. I'll have to further at what level we are doing our DNS caching.
Hello @phax,
I have a question about caching in the peppol-smp-client SMPClientReadOnly. I noticed that when I do a getServiceGroup lookup before registration (returning 404) that after registration I still get the 404 during lookup after saving the ServiceGroup for about 15 minutes even if the ServiceGroup is able to be found by other applications (for example the helger participant information tool). If we do a lookup with the helger participant information tool before registration it looks like the same caching is happening here.
However I am not able to find any caching being done in the smp-client (only caching I could find was InetAddressCachePolicy and we use default 30s).
Does the SML itself do any caching on our requests meaning there is no solution for this issue or am I missing some caching implementation?
Kind regards and thanks in advance!
Some informational stacktraces:
Cached lookup
No Caching