Caused by: java.sql.SQLException: [FMWGEN][SQLServer JDBC Driver]Object has been closed.
at weblogic.jdbc.sqlserverbase.ddb_.b(Unknown Source)
at weblogic.jdbc.sqlserverbase.ddb_.a(Unknown Source)
at weblogic.jdbc.sqlserverbase.ddb9.b(Unknown Source)
at weblogic.jdbc.sqlserverbase.ddb9.a(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseConnection.getTransactionIsolation(Unknown Source)
at weblogic.jdbc.wrapper.PoolConnection_weblogic_jdbc_sqlserverbase_ddah.getTransactionIsolation(Unknown Source)
at org.springframework.jdbc.datasource.DataSourceUtils.prepareConnectionForTransaction(DataSourceUtils.java:190)
After a quick look inside of the log file I figure out that is Memory Problem of OracleWeblogic so I imagine that driver should be changed by an updated driver made it by a the original vendor in this case we are talking of Microsoft SqlServer 2008 R2, if you following a changing configuration of a driver inside of a weblogic you might get an idea of you was. After a successful artifact update and depending of application I get an error like this:
Reached maximum capacity of pool
So after a shameful explanation of what in the hell I was doing with a Database Connection with my leaders the decision was taken, increase capacity connection inside of oracle weblogic, in future releases I will fix my problem with shared configuration using weblogic.xml and probably using a SqlAdapter created with Oracle Service Bus.
Best regards,
