Article ID: 129301, created on Aug 22, 2016, last review on Sep 19, 2016

  • Applies to:
  • Operations Automation 6.0


  1. OA CP is unavailable, it is impossible to login to the system.

  2. UI calls in /var/log/poa.log fail with the following error:

    java.sql.SQLException: Invalid state, the Connection object is closed.
  3. There is a DBService error preceding the exceptions in poa.log:

    javax.ejb.EJBTransactionRolledbackException: could not extract ResultSet
    Caused by: java.sql.SQLException: I/O Error: Read timed out


As a result of a service restart or an outage of some different kind on the side of MSSQL, PAU ODBC uses the old threads for DB requests without validating the connection, therefore SQL errors are faced. This case has been submitted to the Maintenance Team as internal issue with id POA-101854.


Please contact your Account Manager or Pooled Technical Associates Team ( to trace the status of the issue. In order to avoid similar outages in the future, JBoss configuration should be tuned:

  1. In C:\Program Files (x86)\SWsoft\PEM\jboss-eap-6.2\standalone\configuration\standalone-full.xml file add the following line at the top of <validation>...</validation> section:

    <check-valid-connection-sql>SELECT 2</check-valid-connection-sql>

    Please also note recommendations related to standalone-full.xml customization from the following KB article:

    #123177 Operations Automation (formerly POA 6.0) - Known Issues and limitations

  2. Restart services on MN:

    net stop pem
    net stop pau
    net start pau
    net start pem

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF