[
https://issues.apache.org/jira/browse/LENS-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300004#comment-15300004
]
Hudson commented on LENS-1155:
------------------------------
SUCCESS: Integrated in Lens-Commit-Java8 #169 (See
[https://builds.apache.org/job/Lens-Commit-Java8/169/])
LENS-1155 : Seeing INTERNAL_SERVER_ERROR for JDBC queries due to
(sushilmohanty: rev 5c25e68fe71670df6c72d3b8dc08fcbcad6011c4)
* lens-driver-jdbc/src/main/resources/jdbcdriver-default.xml
*
lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/MaxJDBCConnectionCheckConstraintFactory.java
* lens-server-api/src/main/java/org/apache/lens/server/api/util/LensUtil.java
* lens-driver-jdbc/src/test/java/org/apache/lens/driver/jdbc/TestJdbcDriver.java
* lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/JDBCDriver.java
*
lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/MaxJDBCConnectionCheckConstraint.java
> Seeing INTERNAL_SERVER_ERROR for JDBC queries due to connection unavailability
> ------------------------------------------------------------------------------
>
> Key: LENS-1155
> URL: https://issues.apache.org/jira/browse/LENS-1155
> Project: Apache Lens
> Issue Type: Bug
> Components: driver-jdbc
> Reporter: Sushil Mohanty
> Assignee: Sushil Mohanty
> Fix For: 2.6
>
> Attachments: LENS-1155-1.patch
>
>
> When users that are issuing InMemory Queries, the connection is released back
> to pool only after result set is read completely or after query is purged.
> For InMemory Queries (not persisted by lens server), the query state is
> changed to SUCCESSFUL even before connection is released.
> This causes connection pool to throw error for new queries whenever JDBC
> driver is running at almost full load.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
