This content has been marked as final. Show 2 replies
Hi, the problem happens pratically once or two per minute while the application is in use... when the application is not used, no error happens.
So it happens very often... I thought it could be a problem with a proxy/firewall in the middle, but according to the guys in charge of this, nothing has changed on his side.
I've read things about a possible bug in the nativeIO implementation, would it be safe to deactivate nativeIO to see if this bug arise with pure java socket ?
Also this problem only occurs in our production environment, we have 4 others environment used for testing/training/integration and this error does not occur there.
Thanks for any help,