The good news is that my test program described in another thread
("OutOfMemoryErrors again") runs greatly with the latest ActiveMQ
snapshot: I ran 10,000,000 short messages through a topic backed by a
kaha persistence manager without any OutOfMemoryErrors.
However, I noticed that after the application terminated, kaha left
quite large files in its data directory (see the file list below). I'd
assume that after reading all messages from a topic and closing the JMS
connection properly, kaha would clean up the used space and leave at
maximum a few files containing a few bytes only.
total 1650665
drwx------ 2 klute users 408 Jan 29 16:21 .
drwx------ 5 klute users 152 Jan 29 15:35 ..
-rw------- 1 klute users 762 Jan 29 15:32 data-kaha-1
-rw------- 1 klute users 30000104 Jan 29 16:18 data-topic-acks-14
-rw------- 1 klute users 48629101 Jan 29 16:18 data-topic-data-39
-rw------- 1 klute users 49999955 Jan 29 15:33 data-topic-subs-1
-rw------- 1 klute users 30000315 Jan 29 16:18 data-topic-subs-25
-rw------- 1 klute users 357 Jan 29 15:32 index-kaha
-rw------- 1 klute users 509991075 Jan 29 16:22 index-topic-acks
-rw------- 1 klute users 509991075 Jan 29 16:22 index-topic-data
-rw------- 1 klute users 509991177 Jan 29 16:22 index-topic-subs
-rw------- 1 klute users 51 Jan 29 15:32 index-transactions
Best regards
Rainer Klute
Rainer Klute IT-Consulting GmbH
Dipl.-Inform.
Rainer Klute E-Mail: [EMAIL PROTECTED]
Körner Grund 24 Telefon: +49 172 2324824
D-44143 Dortmund Telefax: +49 231 5349423
OpenPGP fingerprint: E4E4386515EE0BED5C162FBB5343461584B5A42E
signature.asc
Description: OpenPGP digital signature
