From: Brendan D. <br...@cl...> - 2007-04-09 23:00:48
|
Hello, When our applications start up, 2 connections are made to our PostgreSQL database. Any ideas why Wonder apps start up 2 connections? We're seeing a bunch of 'idle in transaction' connection statuses in our Postgres database. It's failing to commit the transaction when the bogus extra connection attempts a selection from pg_namespace and pg_type. Here's what we see in our log files right before the first select: [2007-04-09 15:32:16.986] <WorkerThread3> Didn't find any JNDI data source. DriverManager.initialize: jdbc.drivers = null JDBC DriverManager initialized registerDriver: driver [className=org.postgresql.Driver,org.postgresql.Driver@948ad7] [2007-04-09 15:32:17.001] <WorkerThread3> Using JDBCPlugIn 'com.webobjects.jdbcadaptor.PostgresqlPlugIn' for JDBCAdaptor@5125095 [2007-04-09 15:32:17.002] <WorkerThread3> connecting with dictionary: {username = "postgres"; driver = "org.postgresql.Driver"; password = "<password deleted for log>"; URL = "jdbc:postgresql:// localhost/didev?protocolVersion=3"; } DriverManager.getConnection("jdbc:postgresql://localhost/didev? protocolVersion=3") trying driver [className=org.postgresql.Driver,org.postgresql.Driver@948ad7] getConnection returning driver [className=org.postgresql.Driver,org.postgresql.Driver@948ad7] [2007-04-09 15:32:17.548] <WorkerThread3> fetching JDBC Info with JDBCContext@2733162 [2007-04-09 15:32:17.549] <WorkerThread3> Didn't find any JNDI data source. [2007-04-09 15:32:17.550] <WorkerThread3> connecting with dictionary: {username = "postgres"; driver = "org.postgresql.Driver"; password = "<password deleted for log>"; URL = "jdbc:postgresql:// localhost/didev?protocolVersion=3"; } DriverManager.getConnection("jdbc:postgresql://localhost/didev? protocolVersion=3") trying driver [className=org.postgresql.Driver,org.postgresql.Driver@948ad7] getConnection returning driver [className=org.postgresql.Driver,org.postgresql.Driver@948ad7] We have seen these 2 connections with a very simple brand new application that has only 1 model. It happens ONLY when we use Project Wonder. The same application extending from WOApplication and WOSession does not encounter the 2 connections. Does anyone know why this might happen in Wonder applications? Does it happen for anyone else? Thanks, ____________________________________________________________________ Brendan Duddridge | CTO | 403-277-5591 x24 | br...@cl... ClickSpace Interactive Inc. Suite L100, 239 - 10th Ave. SE Calgary, AB T2G 0V9 http://www.clickspace.com |