You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lens.apache.org by "Sushil Mohanty (JIRA)" <ji...@apache.org> on 2016/05/25 09:41:12 UTC
[jira] [Commented] (LENS-1155) Seeing INTERNAL_SERVER_ERROR for
JDBC queries due to connection unavailability
[ https://issues.apache.org/jira/browse/LENS-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299755#comment-15299755 ]
Sushil Mohanty commented on LENS-1155:
--------------------------------------
review at : https://reviews.apache.org/r/47820/
> 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
>
>
> 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)