I thought I would close out this discussion. I am using Dbforms 1.1.3pr now and the Tomcat JNDI datasource. Thanks to Shawn's help, I was able to get the logging working. This enabled me to watch the connection closing process. I adjusted the number of maximum connections in Tomcat down to a reasonable number (25) since someone had set it at 200. This resolved my connection issues since now the connections are promptly closing and are available for reuse. Someone else had posted that they were getting the same error in Oracle. Going to 1.1.3 and adjusting my Tomcat connections down appeared to fix the problem for me.
Thanks to all, Roy -----Original Message----- From: shawn [mailto:[EMAIL PROTECTED]] Sent: Friday, January 31, 2003 7:00 PM To: McBrayer, Roy Subject: RE: [dbforms] Maximum number of Oracle Processes Exceeded (150) sorry my fault catalina.out will be if you use jdbc logging (jndi) but since that didn't tell us so much... jakartaConnectionProvider will be logged wherever you specify log4j.appender.logFile.File=log4j_log.txt log4j_log will be the name of your file. Are you on windows? I've had trouble finding it to so went ...File=c:\path\to\mylog.txt Under linux it's putting it in my home folder. or just search for log4j_log.txt On Sat, 2003-02-01 at 09:00, McBrayer, Roy wrote: > I do not have a catalina.out log in the logs directory. And I feel foolish > but I cannot seem to get log4j to output a log file. This is my log4j > properties file > > #begin log4j.props > #IMPORTANT - Watch for trailing whitespaces after each statement!!! > > #log4j.rootCategory=debug, stdout, logFile > #log4j.rootCategory=warn, stdout > #log4j.rootCategory=warn, stdout > log4j.category.org.dbforms=warn > log4j.rootCategory=debug, stdout, logFile > log4j.category.org.dbforms=debug, logFile > > #out to console > log4j.appender.stdout=org.apache.log4j.ConsoleAppender > log4j.appender.stdout.layout=org.apache.log4j.PatternLayout > > # Pattern to output the caller's file name and line number. > log4j.appender.stdout.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n > > #out to file > log4j.appender.logFile=org.apache.log4j.RollingFileAppender > #tomcat uses bin as current directory when writing log > log4j.appender.logFile.File=log4j_log.txt > log4j.appender.logFile.MaxFileSize=3000KB > log4j.appender.logFile.MaxBackupIndex=1 > > # Pattern to output the caller's file name and line number. > log4j.appender.logFile.layout=org.apache.log4j.PatternLayout > log4j.appender.logFile.layout.ConversionPattern=%5p [%t] (%F:%L) - %m%n > > #end log4j.props > > > > > Thanks, > Roy > -----Original Message----- > From: shawn [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 30, 2003 10:01 PM > To: McBrayer, Roy > Subject: RE: [dbforms] Maximum number of Oracle Processes Exceeded (150) > > > By the way, > > The DBCP log I mentioned can be found: > > DBCP uses System.out for these logs, which goes to > > $CATALINA_HOME/logs/catalina.out unless you've used the "swallowOutput" > > attribute on your <Context> element -- in which case, it goes wherever the > > <Logger> for your <Context> element puts it. > > -- shawn <[EMAIL PROTECTED]> ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms
