My Oracle Support Banner

Users Login Under TomEE Receiving 'PooledConnection.clearWarnings Unable To Clear Warnings Connection Will Be Closed' Message (Doc ID 2877915.1)

Last updated on JUNE 23, 2022

Applies to:

Oracle Insurance Policy Administration J2EE - Version 11.3.1.5 and later
Information in this document applies to any platform.

Symptoms

On : 11.3.1.5 version, General

Users are facing connection pooling issues on login and eventually session times out.
Once this starts occurring, the application does not allow any user logins.
The following message appears in the logs:


ERROR
-----------------------
INFO: Filtering request path: login/processLogin
09-Mar-2022 16:03:37.773 WARNING [tomcat-http--15] org.apache.tomcat.jdbc.pool.PooledConnection.clearWarnings Unable to clear Warnings, connection will be closed.
  java.sql.SQLRecoverableException: Closed Connection
  at oracle.jdbc.driver.PhysicalConnection.clearWarnings(PhysicalConnection.java:2573)
  at org.apache.tomcat.jdbc.pool.PooledConnection.clearWarnings(PooledConnection.java:837)
  at org.apache.tomcat.jdbc.pool.ConnectionPool.returnConnection(ConnectionPool.java:977)
  at org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:100)
  at org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
  at org.apache.tomcat.jdbc.pool.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:69)
  at org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
  at org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:81)
  at com.sun.proxy.$Proxy139.close(Unknown Source)
  at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.closeDatasourceConnection(DatabaseAccessor.java:502)




STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Login to the OIPA Web app using the credentials.
2. Once user login, they can perform certain operations and the App works as expected.
3. Wait till the session times out and then try to login again.
4. Once user attempt login again, they encounter an message that the login is not working and the console shows 500 error.
5. The logs shows 'Closed Connection'.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.