René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Exceptions are not propagated properly","articleBody":"If RandomOrgClient roc = RandomOrgClient.GetRandomOrgClient(YOUR_API_KEY_HERE); is executed without an active internet connection, the resulting exception **is not handled** by the surrounding try/catch block.\n\nExecution always stops here:\n\u003cimg width=\"2142\" height=\"1280\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/8d531535-3bc0-4fb7-9daa-2a7e3acadb06\" /\u003e\n\nInstead of getting to the catch clause of my try/catch block:\n\n```\n try\n\t {\n             var client = RandomOrgClient.GetRandomOrgClient(RANDOM_ORG_KEY);\n             var randomNumbers = client.GenerateIntegers(10, 1, 10, true);\n\t }\n\t catch (Exception ex)\n\t {\n\t \t// IT NEVER GETS HERE\n\t }\n\n```\n\nIn other words, exceptions triggered inside ThreadedRequestSending (the \"core\" part of the library) are not propagated back to the caller and they just make the applications crash.\n\nHow to reproduce:\n1) Implement a simple console application containing the code above\n2) Run it WITHOUT being connected to the Internet or just throw an exception from ThreadedRequestSending\n\nThe issue is likely caused by the fact that requested are sent in separate threads (ThreadedRequestSending), but this approach prevents proper handling of exceptions raised by the library. If that is the actual reason for this behaviour, I would suggest to use one of the following approaches to propagate the error back to the caller:\n\n- Ashared data structure (e.g., ConcurrentQueue\u003cException\u003e).\n- Events or callbacks.\n- **Switch to Task and async/await for easier exception propagation.**","author":{"url":"https://github.com/nandaccio","@type":"Person","name":"nandaccio"},"datePublished":"2025-08-22T11:05:30.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/2/JSON-RPC-.NET/issues/2"}