[logback-user] Number of logs

Ceki Gulcu listid at qos.ch
Tue Sep 23 20:09:54 CEST 2008

Hi Greg,

Thanks for letting us know. However, I am troubled by the fact that 
DriverManagerConnectionSource fails after a few thousand events. While it is 
known that getting connections from a driver manager is slow, it should not fail.

May I ask you to create a jira issue describing the problem as observed 
initially. You can just refer to this discussion. Please let me know if that is 
too much trouble.

Greg Flex wrote:
> ok guys,
> I figured this out. It works beatifully now!
> All I had to do is download (per instructions on the logback website) 
> the c3po pooling library
> and modify the appender's xml file to:
> <appender name="DB" class="ch.qos.logback.classic.db.DBAppender">
>     <connectionSource 
> class="ch.qos.logback.core.db.DataSourceConnectionSource">
>       <dataSource class="com.mchange.v2.c3p0.ComboPooledDataSource">
>          <driverClass>com.mysql.jdbc.Driver</driverClass>
>           <jdbcUrl>jdbc:mysql://localhost:3306/Greg</jdbcUrl>
>          <user>greg</user>
>          <password>greg</password>
>       </dataSource>
>     </connectionSource>
>   </appender>
> In my case the database name is: Greg, password and username: greg
> It works great and it is in fact very fast now. I just loaded it with 
> 50,000 records without any problems whatsoever.
> I guess is safe to say  "read the documentation first man...!"  :-)
> Cheers,
> Greg 
> On Tue, Sep 23, 2008 at 9:38 AM, Greg Flex <greg.flex at gmail.com 
> <mailto:greg.flex at gmail.com>> wrote:
>     Ok no problem.
>     I'm running the program and the database on just one computer.
>     It's all local and no one is connecting to it....
>     It's a Xeon 2.66 GHz machine with 4 cores and 3GB of ram.
>     I'm running Windows XP. (the newest service pack)
>     I'm looking at the Task Manager right now and I see that over 2GB of
>     memory is available.
>     I just ran my program again but this time I've reduced the
>     Thread.sleep to just 10ms.
>     Instead of 40,000 records just about 8,000 got written.
>     This means 10-ms is too fast and MySQL can't handle it or something.
>     I'm not sure but from the documentation on line looks like the
>     connection pooling is the way out...
>     I don't know and I guess I don't understand that well the notion of
>     "connection pooling" so I don't know
>     how to set it up/create one.
>     Any suggestions?
>     Thanks a lot
>     Greg.
>     On Tue, Sep 23, 2008 at 9:06 AM, Thorbjørn Ravn Andersen
>     <ravn at runjva.com <mailto:ravn at runjva.com>> wrote:
>         Greg Flex skrev:
>          > I didn't "touch" the configuration of MySQL at all. I assume
>         it's the
>          > normal/standard configuration that comes with it.....
>          > I ran the program again for some time last night. I wrote one
>         log.xxx
>          > then paused the thread for about 100ms then wrote another log.xxx
>          > I managed to write 39,000 logs to MySQL without any problems.
>         It looks
>          > to me then that the "speed" has something to do here.
>          > If writting too fast (too many records at once) to the
>         database (both
>          > MySQL and HSQLDB) they simply "choke"....
>          > I don't know however if this is the problem; just my
>         observations.....
>          >  Do you think this might cause it?
>          > Greg.
>         I am not thinking of the configuration of the database software
>         as such
>         but of the configuration of the computer which runs the database
>         software.
>         I suspect that you have less physical memory available to the
>         database
>         than they think they can use, hence the operating system starts
>         swapping
>         which kills performance.
>         Can you please describe your setup in detail so we can replicate the
>         scenario?  I.e. number of computers involved, connections
>         between them,
>         network performance, memory assigned, operating systems used, etc.
>         /Thorbjørn
>         _______________________________________________
>         Logback-user mailing list
>         Logback-user at qos.ch
>         http://qos.ch/mailman/listinfo/logback-user
> ------------------------------------------------------------------------
> _______________________________________________
> Logback-user mailing list
> Logback-user at qos.ch
> http://qos.ch/mailman/listinfo/logback-user

Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.

More information about the Logback-user mailing list