Thanks for the answer. I've read these instructions in documentation but the Derby instance i use is embedded in ActiveMQ, not in my own application, and i don't wont modify the source code! :)
My questions are: - can i override any ActiveMQ Derby properties to force default checkpoint (after 10MB of logs)? - why ActiveMQ shoud enable log archiving mode? Many thanks! Knut Anders Hatlen wrote: > > Fuzzo <[EMAIL PROTECTED]> writes: > >> Hi all! >> >> I looked for stange options in configuration but the only one regarding >> Derby is: >> derby.storage.fileSyncTransactionLog=true >> >> I think this doesn't modify default 10MB log limit for checkpoint. > > I think you're right. > > Just to make sure that you don't have log archiving mode enabled, you > could issue this statement: > > CALL SYSCS_UTIL.SYSCS_DISABLE_LOG_ARCHIVE_MODE(1) > >> From friday to now, the log directory size is 2.5GB: if i can't force >> derby >> to checkpoint, i'll switch to another db... :( > > You can force Derby to checkpoint by issuing > > CALL SYSCS_UTIL.SYSCS_CHECKPOINT_DATABASE() > > -- > Knut Anders > > -- View this message in context: http://www.nabble.com/Embedded-Derby-and-.dat-files-tp19574483p19607997.html Sent from the Apache Derby Users mailing list archive at Nabble.com.
