i'm using an mdb to persist messages to a database. the jbossmq topic the
mdb subscribes to is durable.
after persisting 10s of thousands of messages i find that the start-up of
jboss slows from a few seconds
to well over one minute. i assume this is due to jbossmq checking the jms
database for undelivered messages.
( i can recover the quick start-up if i delete the appropriate .dat files in
$JBOSS/db/jbossmq before restarting jboss.
however, doing this defeats the purpose of durability.) it appears to me
that all messages sent to a durable topic
are kept in the jms database, even if they have been delivered. i guess
when jboss starts, every entry in the db has
to be checked to see if it's been sent, thus slowing things down. if my
surmise is correct, is there some simple
configuration change i can make (other than using nondurable) that will
speed the start up? or will i have to do
some real work? :-)
tia,
bill
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
