dbTalk Databases Forums  

[BUGS] BUG #2060: Issue with Data base connection

mailing.database.pgsql-bugs mailing.database.pgsql-bugs


Discuss [BUGS] BUG #2060: Issue with Data base connection in the mailing.database.pgsql-bugs forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Manideep Kalisetty
 
Posts: n/a

Default [BUGS] BUG #2060: Issue with Data base connection - 11-21-2005 , 08:32 AM







The following bug has been logged online:

Bug reference: 2060
Logged by: Manideep Kalisetty
Email address: mani7deep (AT) yahoo (DOT) com
PostgreSQL version: 7.2.2
Operating system: Windows and Linux
Description: Issue with Data base connection
Details:

I am using postgresql-8.1dev-402.jdbc3.jar JDBC driver and websphere
application server. Even though I am successfully closing connections, the
error message I am receivng is "Backend start-up failed: FATAL 1: Sorry,
too many clients already". Please refer to the Exception report below:


[11/21/05 10:28:54:836 IST] 50b9631a SystemErr R
org.postgresql.util.PSQLException: Backend start-up failed: FATAL 1: Sorry,
too many clients already
..
[11/21/05 10:28:54:836 IST] 50b9631a SystemErr R at
org.postgresql.core.v2.ConnectionFactoryImpl.readS tartupMessages(ConnectionF
actoryImpl.java(Compiled Code))
[11/21/05 10:28:54:836 IST] 50b9631a SystemErr R at
org.postgresql.core.v2.ConnectionFactoryImpl.openC onnectionImpl(ConnectionFa
ctoryImpl.java(Compiled Code))
[11/21/05 10:28:54:836 IST] 50b9631a SystemErr R at
org.postgresql.core.ConnectionFactory.openConnecti on(ConnectionFactory.java(
Compiled Code))
[11/21/05 10:28:54:836 IST] 50b9631a SystemErr R at
org.postgresql.jdbc2.AbstractJdbc2Connection.<init >(AbstractJdbc2Connection.
java(Compiled Code))
[11/21/05 10:28:54:836 IST] 50b9631a SystemErr R at
org.postgresql.jdbc3.AbstractJdbc3Connection.<init >(AbstractJdbc3Connection.
java(Inlined Compiled Code))
[11/21/05 10:28:54:836 IST] 50b9631a SystemErr R at
org.postgresql.jdbc3.Jdbc3Connection.<init>(Jdbc3C onnection.java(Inlined
Compiled Code))
[11/21/05 10:28:54:836 IST] 50b9631a SystemErr R at
org.postgresql.Driver.makeConnection(Driver.java(I nlined Compiled Code))
[11/21/05 10:28:54:836 IST] 50b9631a SystemErr R at
org.postgresql.Driver.connect(Driver.java(Compiled Code))
[11/21/05 10:28:54:836 IST] 50b9631a SystemErr R at
java.sql.DriverManager.getConnection(DriverManager .java(Compiled Code))
[11/21/05 10:28:54:836 IST] 50b9631a SystemErr R at
java.sql.DriverManager.getConnection(DriverManager .java(Inlined Compiled
Code))
[11/21/05 10:28:54:836 IST] 50b9631a SystemErr R at
kanbay.dao.DBAccess.getConnection(DBAccess.java(Co mpiled Code))
[11/21/05 10:28:54:836 IST] 50b9631a SystemErr R at
kanbay.dao.ContributorsDAO.getContributorsOfTheMon th(ContributorsDAO.java:11
9)
[11/21/05 10:28:54:836 IST] 50b9631a SystemErr R at
kanbay.com.GenericServlet.doPost(GenericServlet.ja va:124)
[11/21/05 10:28:54:836 IST] 50b9631a SystemErr R at
kanbay.com.GenericServlet.doGet(GenericServlet.jav a:48)
[11/21/05 10:28:54:846 IST] 50b9631a SystemErr R at
javax.servlet.http.HttpServlet.service(HttpServlet .java:740)
[11/21/05 10:28:54:846 IST] 50b9631a SystemErr R at
javax.servlet.http.HttpServlet.service(HttpServlet .java(Compiled Code))
[11/21/05 10:28:54:846 IST] 50b9631a SystemErr R at
com.ibm.ws.webcontainer.servlet.StrictServletInsta nce.doService(StrictServle
tInstance.java(Compiled Code))
[11/21/05 10:28:54:846 IST] 50b9631a SystemErr R at
com.ibm.ws.webcontainer.servlet.StrictLifecycleSer vlet._service(StrictLifecy
cleServlet.java(Compiled Code))
[11/21/05 10:28:54:846 IST] 50b9631a SystemErr R at
com.ibm.ws.webcontainer.servlet.IdleServletState.s ervice(StrictLifecycleServ
let.java:313)
[11/21/05 10:28:54:846 IST] 50b9631a SystemErr R at
com.ibm.ws.webcontainer.servlet.StrictLifecycleSer vlet.service(StrictLifecyc
leServlet.java(Inlined Compiled Code))
[11/21/05 10:28:54:846 IST] 50b9631a SystemErr R at
com.ibm.ws.webcontainer.servlet.ServletInstance.se rvice(ServletInstance.java
(Compiled Code))
[11/21/05 10:28:54:846 IST] 50b9631a SystemErr R at
com.ibm.ws.webcontainer.servlet.ValidServletRefere nceState.dispatch(ValidSer
vletReferenceState.java(Compiled Code))
[11/21/05 10:28:54:846 IST] 50b9631a SystemErr R at
com.ibm.ws.webcontainer.servlet.ServletInstanceRef erence.dispatch(ServletIns
tanceReference.java(Inlined Compiled Code))
[11/21/05 10:28:54:846 IST] 50b9631a SystemErr R at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispat cher.handleWebAppDispatch(
WebAppRequestDispatcher.java(Compiled Code))
[11/21/05 10:28:54:846 IST] 50b9631a SystemErr R at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispat cher.dispatch(WebAppReques
tDispatcher.java(Compiled Code))
[11/21/05 10:28:54:867 IST] 50b9631a SystemErr R at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispat cher.forward(WebAppRequest
Dispatcher.java:200)
[11/21/05 10:28:54:867 IST] 50b9631a SystemErr R at
com.ibm.ws.webcontainer.srt.WebAppInvoker.doForwar d(WebAppInvoker.java:119)
[11/21/05 10:28:54:867 IST] 50b9631a SystemErr R at
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleIn vocationHook(WebAppInvoker
..java:276)
[11/21/05 10:28:54:867 IST] 50b9631a SystemErr R at
com.ibm.ws.webcontainer.cache.invocation.CachedInv ocation.handleInvocation(C
achedInvocation.java:71)
[11/21/05 10:28:54:867 IST] 50b9631a SystemErr R at
com.ibm.ws.webcontainer.cache.invocation.Cacheable InvocationContext.invoke(C
acheableInvocationContext.java:116)
[11/21/05 10:28:54:867 IST] 50b9631a SystemErr R at
com.ibm.ws.webcontainer.srp.ServletRequestProcesso r.dispatchByURI(ServletReq
uestProcessor.java:186)
[11/21/05 10:28:54:867 IST] 50b9631a SystemErr R at
com.ibm.ws.webcontainer.oselistener.OSEListenerDis patcher.service(OSEListene
r.java:334)
[11/21/05 10:28:54:867 IST] 50b9631a SystemErr R at
com.ibm.ws.webcontainer.http.HttpConnection.handle Request(HttpConnection.jav
a:56)
[11/21/05 10:28:54:867 IST] 50b9631a SystemErr R at
com.ibm.ws.http.HttpConnection.readAndHandleReques t(HttpConnection.java:618)

[11/21/05 10:28:54:867 IST] 50b9631a SystemErr R at
com.ibm.ws.http.HttpConnection.run(HttpConnection. java:443)
[11/21/05 10:28:54:867 IST] 50b9631a SystemErr R at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:672)

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Reply With Quote
  #2  
Old   
Kris Jurka
 
Posts: n/a

Default Re: [BUGS] BUG #2060: Issue with Data base connection - 11-21-2005 , 06:40 PM








On Mon, 21 Nov 2005, Manideep Kalisetty wrote:

Quote:
Bug reference: 2060
Email address: mani7deep (AT) yahoo (DOT) com
PostgreSQL version: 7.2.2
Description: Issue with Data base connection
Details:

I am using postgresql-8.1dev-402.jdbc3.jar JDBC driver and websphere
application server. Even though I am successfully closing connections, the
error message I am receivng is "Backend start-up failed: FATAL 1: Sorry,
too many clients already". Please refer to the Exception report below:

Well, something is leaving connections open. Checking the results of
SELECT * FROM pg_stat_activity; will tell you what database and username
they are connected to which may help. While this code doesn't appear to
be using a connection pool, perhaps you have another application that is
using a pool that is configured to open too many connections? Still, the
most likely cause is a coding error failing to close connections.

Kris Jurka

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match


Reply With Quote
  #3  
Old   
Kris Jurka
 
Posts: n/a

Default Re: [BUGS] BUG #2060: Issue with Data base connection - 11-23-2005 , 01:44 PM



This is a multi-part message in MIME format.
--------------020004030600060108030308
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

kalisetty manideep wrote:
Quote:
[Backend reports "too many open connections"]

But I am 100% sure that its not the issue with the
code.

Do you know any Postgresql - JDBC driver, which is not
from Postgresql development group. I think JDBC driver
is not closing the connection even though I am closing
the connection.
I have no reason to believe that and you certainly haven't shown that.

Quote:
Please refer to the DBACCESS file attached.

All this shows is the Connection being opened, not closed.

I've implemented an idea I got from rupa in #postgresql a while ago
about a way of logging leaked connections. I've added some code to the
Connection's finalize() method that prints some logging information if
the Connection was not closed. This is enabled by using the new
logUnclosedConnections URL parameter.

See the attached code for an example. I've put up a new jar that
contains this here: http://www.ejurka.com/pgsql/jars/km

--------------020004030600060108030308
Content-Type: text/x-java;
name="OpenConn.java"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="OpenConn.java"

import java.sql.*;

public class OpenConn {

public static void main(String args[]) throws Exception {
Class.forName("org.postgresql.Driver");
leakConnection();
System.gc();
}

private static void leakConnection() throws Exception {
Connection conn = DriverManager.getConnection("jdbcostgresql://localhost:5810/jurka?logUnclosedConnections=true","jurka","");
}

}


--------------020004030600060108030308
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0


---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

--------------020004030600060108030308--


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.