You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by GitBox <gi...@apache.org> on 2023/01/17 17:43:39 UTC

[GitHub] [commons-pool] reda-alaoui commented on pull request #209: NullPointerException can occur in GenericObjectPool#use

reda-alaoui commented on PR #209:
URL: https://github.com/apache/commons-pool/pull/209#issuecomment-1385794431

   Hello @kinow ,
   
   It happened via commons-dbcp.
   Here is a part of the stacktrace:
   ```java
   Caused by: java.lang.NullPointerException: Cannot invoke "org.apache.commons.pool2.PooledObject.use()" because "wrapper" is null
                   at org.apache.commons.pool2.impl.GenericObjectPool.use(GenericObjectPool.java:1299)
                   at org.apache.commons.pool2.proxy.BaseProxyHandler.doInvoke(BaseProxyHandler.java:77)
                   at org.apache.commons.pool2.proxy.JdkProxyHandler.invoke(JdkProxyHandler.java:50)
                   at jdk.proxy8/jdk.proxy8.$Proxy1669.commit(Unknown Source)
                   at org.apache.commons.dbcp2.DelegatingConnection.commit(DelegatingConnection.java:191)
                   at jdk.internal.reflect.GeneratedMethodAccessor702.invoke(Unknown Source)
                   at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
                   at java.base/java.lang.reflect.Method.invoke(Method.java:568)
                   at net.ttddyy.dsproxy.proxy.ConnectionProxyLogic.performQueryExecutionListener(ConnectionProxyLogic.java:112)
                   at net.ttddyy.dsproxy.proxy.ConnectionProxyLogic.access$000(ConnectionProxyLogic.java:25)
                   at net.ttddyy.dsproxy.proxy.ConnectionProxyLogic$1.execute(ConnectionProxyLogic.java:50)
                   at net.ttddyy.dsproxy.listener.MethodExecutionListenerUtils.invoke(MethodExecutionListenerUtils.java:41)
                   at net.ttddyy.dsproxy.proxy.ConnectionProxyLogic.invoke(ConnectionProxyLogic.java:47)
                   at net.ttddyy.dsproxy.proxy.jdk.ConnectionInvocationHandler.invoke(ConnectionInvocationHandler.java:25)
                   at jdk.proxy8/jdk.proxy8.$Proxy1670.commit(Unknown Source)
                   at jdk.internal.reflect.GeneratedMethodAccessor702.invoke(Unknown Source)
                   at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
                   at java.base/java.lang.reflect.Method.invoke(Method.java:568)
                   at org.springframework.jdbc.datasource.LazyConnectionDataSourceProxy$LazyConnectionInvocationHandler.invoke(LazyConnectionDataSourceProxy.java:378)
                   at jdk.proxy8/jdk.proxy8.$Proxy2199.commit(Unknown Source)
                   at jdk.internal.reflect.GeneratedMethodAccessor702.invoke(Unknown Source)
                   at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
                   at java.base/java.lang.reflect.Method.invoke(Method.java:568)
                   at org.springframework.jdbc.datasource.TransactionAwareDataSourceProxy$TransactionAwareInvocationHandler.invoke(TransactionAwareDataSourceProxy.java:238)
                   at jdk.proxy8/jdk.proxy8.$Proxy2199.commit(Unknown Source)
                   at org.hibernate.resource.jdbc.internal.AbstractLogicalConnectionImplementor.commit(AbstractLogicalConnectionImplementor.java:86)
                   at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl$TransactionDriverControlImpl.commit(JdbcResourceL
   ocalTransactionCoordinatorImpl.java:282)
   ```
   
   > and preferably update the PR with a unit test to reproduce the exception, please?
   
   I don't know how to reproduce the full issue, sorry. Do you want a very basic unit test that will check the case where pool is empty for example?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@commons.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org