We are using XA resource to access a SQLServer Database using ODBC (ESODBCXA)
When a network failure occurs or something happens on the Database side that invalidate DB connection, that connection on MF side becomes invalid.
Even though everything is back to normal (network and database) the SEP's XA ODBC connection (on the MF side) is still corrupt and when we try to access the application from TN3270 we get a "CASSP0010S Syncpoint failure - resource state unpredictable".
When in that situation we need to go in ESMAC, first disable then re enable the XA Adapter and everything is back to normal.
I would like to know if there is a way to make the XA Adapter try to reset itself when such a situation occurs.
I tried to resolve the issue with the following settings but was unsuccessful:
ES_XA_RECONNECT
ES_XA_????_NB_RETRIES=nnnn (where ???? defines the XA ID)
How can I automate a connection test to prevent such an issue from happening?
In many JDBC connection pools there is a connection validation feature, does Micro Focus has something like that out of the box?
e.g.
Connection validation. Some databases close open connections quite aggressively if they detect they're not used or a connection can be lost because of a network glitch. The pool can then execute a validation query every time the application borrows a connection. If the validation query fails, the pool assumes it's dead and creates a new one. This is all transparent for the application, which doesn't have to worry about dead or invalid connections.
#EnterpriseServer
