Fix bug where setting validateSignonTimeOut causes the soTimeout to also be set after calling AS400.validateSignon() #216
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
An issue was discovered internally where calling
AS400.setvalidateSignonTimeOut()
and then subsequently callingAS400.validateSignon()
would cause the SocketProperties on that AS400 object to have thesoTimeout
set for future host server connections. This causes an issue when threads are used for communication, as soTimeout and threadsUsed are generally incompatible. This manifested as "Read time out" errors in code that had a long time between requests to the system. Switching thevalidateSignon()
code to copy the socket properties instead of changing the main reference cleared up the issue.