From: Brendan D. <br...@cl...> - 2007-04-10 05:46:46
|
Ooops.. Seems there was a spelling mistake in the property: "DriveIt.removeJdbc2Info=false" worked. No more extra connections at app startup. 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 On Apr 9, 2007, at 10:21 PM, Brendan Duddridge wrote: > Hi Mike, > > This parameter made no difference. I added > DriveIt.removeJdb2Info=false to my Properties file. > > However, if I comment out the defaultModelGroup() method on > ERXExtensions, then the 2nd connection does not occur. > > Is there any reason that I would have to have this? What would be > the ramifications if I comment that out? > > We're running out of process resources in our production app right > now ("fork: Resource temporarily unavailable") > > 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 > > On Apr 9, 2007, at 5:50 PM, Mike Schrag wrote: > >> It's possible this second connection is because jdbc2Info is, by >> default, removed, though it should not be left open. I did a >> bunch of work w/ PG and Wonder, actually, to make sure it closed >> up lingering connections. Are you using a recent build (recent >> being within the last month or so)? You can test the jdbc2Info >> theory by setting YourModelName.removeJdb2Info=false . for the >> models in question. >> >> ms >> >> On Apr 9, 2007, at 7:00 PM, Brendan Duddridge wrote: >> >>> 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 >>> >>> -------------------------------------------------------------------- >>> ----- >>> Take Surveys. Earn Cash. Influence the Future of IT >>> Join SourceForge.net's Techsay panel and you'll get the chance to >>> share your >>> opinions on IT & business topics through brief surveys-and earn cash >>> http://www.techsay.com/default.php? >>> page=join.php&p=sourceforge&CID=DEVDEV______________________________ >>> _________________ >>> Wonder-disc mailing list >>> Won...@li... >>> https://lists.sourceforge.net/lists/listinfo/wonder-disc >> >> --------------------------------------------------------------------- >> ---- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to >> share your >> opinions on IT & business topics through brief surveys-and earn cash >> http://www.techsay.com/default.php? >> page=join.php&p=sourceforge&CID=DEVDEV_______________________________ >> ________________ >> Wonder-disc mailing list >> Won...@li... >> https://lists.sourceforge.net/lists/listinfo/wonder-disc > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV________________________________ > _______________ > Wonder-disc mailing list > Won...@li... > https://lists.sourceforge.net/lists/listinfo/wonder-disc |