AFAIK The connections did not closed until restart JDBC Interpreter.
so https://github.com/apache/zeppelin/pull/1396 use ConnectionPool for
control sessions.

2016-10-19 2:43 GMT+09:00 Benjamin Kim <bbuil...@gmail.com>:

> We are using Zeppelin 0.6.0 as a self-service for our clients to query our
> PostgreSQL databases. We are noticing that the connections are not closing
> after each one of them are done. What is the normal operating procedure to
> have these connections close when idle? Our scope for the JDBC interpreter
> is “shared”, which I thought would make 1 connection for all notebooks. It
> would seem that I am wrong. Anyone have any ideas on what would help?
> Thanks,
> Ben

Reply via email to