Sorry about the confusion. When I typed in the set timeout 500 I inadvertently left off the ms. We are using 500ms as the value passed for the -expire argument.
With that information corrected our questions are still the same and any help you can give is greatly appreciated.
I have test cases where I set the -expire to 50ms and the expiration occurs as expected decoupling the target system from ours. The ssl error case is one that we cannot seem to manually reproduce and I am now wondering if the problem is rooted in the ssl connect failed problem. Is there a chance that the expiration timeout is not in affect while the ssl connection is being made? The symptoms we are seeing appear like the ssl connection has to be made before the timeout can cause a release of the call and return of control when the timeout is reached. Is this a possible issue and what can be done to fix it?
Thanks again for all of your help,
-Tony Kirkham
