When we call borrowObject & testOnBorrow flag is enabled, the library is making two isConnected() calls - once in activateObject & again in validateObject. As each of these isConnected() calls send NOOP operations, SMTP Servers are overwhelmed with number of NOOP operations they receive and flagging the client as 'possible SMTP attack(er)'. We send several millions of emails everyday and two NOOP commands on every borrow operation is causing issues. Also a we noticed degraded performance as explained here on java mail code base
The way we are getting around this is to set testOnBorrow flag to false and relay on validating connection in activateObject method.
Should we consider modifying activteObject method not to call isConnected() method?
When we call borrowObject & testOnBorrow flag is enabled, the library is making two isConnected() calls - once in activateObject & again in validateObject. As each of these isConnected() calls send NOOP operations, SMTP Servers are overwhelmed with number of NOOP operations they receive and flagging the client as 'possible SMTP attack(er)'. We send several millions of emails everyday and two NOOP commands on every borrow operation is causing issues. Also a we noticed degraded performance as explained here on java mail code base
The way we are getting around this is to set testOnBorrow flag to false and relay on validating connection in activateObject method.
Should we consider modifying activteObject method not to call isConnected() method?