In our shop, we have java applications running in WebSphere talking to CONNX to retreieve data from Adabas. The java application is configured (in WebSphere) to validate their DB connection before sending commands to the CONNX JDBC Server. Connection pooling is used in WebSphere.
The problem happens when WebSphere is recycled and that may not recycle the DB connection pool that WebSphere maintains.
When that happens, the application receives a “STATEMENT NOT ACTIVE” error with its Adabas call and I always see a rsp 009 subcode 66 in the CONNX JDBC Server log.
It seems that when the connection pool associated to WebSphere is not refreshed then the application results in using connection that no longer have a corresponding UQE in Adabas. The connection is still deemed as validate on the app server side.
Can you describe who issues the OP command and with connection pooling on the app server, who checks to make sure a UQE still existed in Adabas and makes the decision on when OP needs to be reissued? If reissued is needed, would I see a rsp 009 subcode 66 in the JDBC server log? Should the front end see any error?
We have connectionpooling turned off on the CONNX JDBC and the ACE side. We have REISSUEOP=1 set in both CONNX JDBC and ACE parms.
I appreciate any comment or suggestion from you.
Many thanks in advance.