Connections not getting released in smartgwt 13.1

[anupprabhu]

I have recently upgraded from smartgwt 6.1 to smartgwt 13.1 but after the upgrade we faced performance issues like the connection pool is getting fully occupied and not releasing the connection. We are using Oracle DB and when we set connection via jndi in server properties then our connection pool in jboss was getting fully utilized and not releasing connections later we changed this config to direct oracle connection then we noticed the issue in oracle db where connections are not getting released. Can you please provide any help on this issue? Getting below exception when all connections are used. Attached the full log as well for reference. Let me know if any further details needed

org.springframework.transaction.CannotCreateTransactionException: Could not open Hibernate Session for transaction; nested exception is org.hibernate.exception.GenericJDBCException: Unable to acquire JDBC Connection
at org.springframework.orm.hibernate5.HibernateTransactionManager.doBegin(HibernateTransactionManager.java:598) ~[spring-orm-5.3.22.jar:5.3.22]
at org.springframework.transaction.support.AbstractPlatformTransactionManager.startT

[Isomorphic]

This would be because of what your colleague did here: https://forums.smartclient.com/node/276026

And was why we warned him not to do this... but it looks like he did it anyway.

Note we deleted his comment in order to prevent other people from believing it was a solution and making the same mistake, so you will need to contact him directly.

Finally, bear in mind that you do not have support, and this would be a good time to at least purchase a batch of hours, if you expect further help.

[anupprabhu]

We are not using the solution given in https://forums.smartclient.com/node/276026 Below is my server properties Let me know if any changes to be done here for Smartgwt 13.1
I never used to get connection pool issue in older version smartgwt 6.1


webRoot: __AUTODETECT__
project.apps: $webRoot/shared/app
gwtModuleName: tfbsew
isomorphicPathRootRelative: $gwtModuleName/sc


sql.defaultDatabase: Oracle
sql.Oracle.driver.name: java:/jdbc/cmsDSLocal
sql.Oracle.database.type: oracle
sql.Oracle.interface.type: jndi


datasourceRoot: $webRoot/WEB-INF/classes/datasources
project.datasources: $datasourceRoot/core,$datasourceRoot/bpm,$datasourceRoot/shared/advanceruling,$datasourceRoot/shared/codemaintenance,$datasourceRoot/shared/tpr
project.ui: $webRoot/shared/ui


RPCManager.enabledBuiltinMethods: *

modulesDir: modules/

addVersionToLoadTags: false



servlet.sendStackTraceToClient: false

sql.useAnsiJoins = false

[Isomorphic]

There's nothing obviously wrong there, but there is no known connection pool issue in SmartGWT 13.1 (it's running in very high volume environments), and the "solution" (deleted) in the linked thread would have done exactly what you're showing here.

So again, we would recommend you purchase some support hours if you would like us to dive into this issue.

[anupprabhu]

We have further diagonsed and printed logs from these Below isomorphic classes, we see few of the db sesions are not getting closed. And i can see the DB queries executed but not closed sometimes in database as well.

com.isomorphic.sql.SQLConnectionManager,com.isomorphic.sql.SQLDriver,com.isomorphic.sql.PoolableSQLConnectionFactory,com.isomorphic.sql.SQLTransaction

Our smartgwt application was running smoothly in prod with 6.1 version for past 6 years but now after the upgrade same application is giving these issues where few connections are not getting closed.

[Isomorphic]

You are not getting any closer to a resolution by just repeatedly asserting that things were fine in an older version.

This is because the most common upgrade issue by far is longstanding usage issues (that is, relying on undocumented behavior) that cause problems in a new version.

Furthermore, there are thousands of SmartGWT 13.x applications deployed out there with no connection leaks or recycling issues, as well as a suite of automated tests verifying there are no connection leaks in a wide variety of situations.

If you were perhaps reporting that your report on your app leaking connections would cause us to search around for a bug, that will not happen because we already know for certain that connections are not leaked when application code follows the docs.

As far as finding a solution to your problem, your options are the same ones that the forums remind you of every time you go to post:

1) create a standalone, ready-to-run test case demonstrating a framework bug

.. or ..

2) purchase Hourly Support so that we can analyze your application and figure out why it leaks connections (whether that's a usage issue, obscure framework bug, or whatever)