Hello Richard,
Am 02.07.2025 um 02:24 schrieb Richard Schoen <richard@xxxxxxxxxxxxxxxxx>:
Make sure to report back here once you resolve your situation.
We haven't found a definitive solution, only workarounds. The flaw seems to be within the IBM ODBC driver itself, but there is no 100% proof.
The dev says, he eventually switched to asynchronous methods for function calls like database access in a C# background thread instead of simply waiting for a reply in that thread and continue processing afterwards.
This change pushed the required hammering upon the ODBC driver to trigger the issue to many orders of magnitude what we expect in normal "production". We aren't sure if this is a causal change of behavior or just correlated. It's still a mystery.
Explanation: The application in question is a C#/.NET/Blazor self-contained web server application with a background thread collecting data via SNMP and saving that into an IBM i database table, and a "foreground" thread for presentation of collected data from the database into a web grid/table.
Not sure if this helps.
:wq! PoC
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
