[
http://jira.jboss.com/jira/browse/JBMESSAGING-1162?page=comments#action_1... ]
Gabriele Garuglieri commented on JBMESSAGING-1162:
--------------------------------------------------
Hi Tim,
the messages are about 1kb each but i don't think this is the problem.
We experimented a bit with FullSize attribute and it looks there's a law that tie the
attribute value with the number of persisted messages, but we didn't find it
documented. We tried to extrapolate the values but we would like to be sure the relation
remains linear in the entire domain.
(i'm sorry i don't have the time to check it myself in the code right now)
Even if it should not be the normal operating condition we must be able to account, given
some particular conditions, for a db that could contain for short time tenth of million
messages without substantial performance penalty during usage and system restart. We can
lower the FullSize value for a single topic/queue but the db will contain several of them
so the cumulative effect at restart will be the same.
Anyway i wonder why we should condition the JBM startup and hence Jboss startup to the
memory load of the messages. IMO the system should be up and running in the faster way
possible and then delay the load once an application may need to access the topic/queue.
I think it is more tolerable a slow start for the single application than for the whole
system, even if i think that with the right parallelism the memory load could be executed
while the applications are already accessing the messages so without too much delay.
I don't know what experience you have of large accounts but i can assure you that if i
would deliver this configuration in production, with a test that shows a freeze of 10
minutes during startup i'd receive thumb down from our I/T people.
Thank you, Gabriele
JBM takes eons to startup with topic persisted messages within db
-----------------------------------------------------------------
Key: JBMESSAGING-1162
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-1162
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core Persistence
Affects Versions: 1.4.0.SP1
Environment: Java 1.5.0_14
JBoss 4.2.2
Solaris 10, AMD Opteron biprocessor machine
Reporter: Gabriele Garuglieri
Assigned To: Tim Fox
Priority: Critical
The problem is reproduced as follows:
1-Start server
2-start a producer that inserts persisted messages (we tried 90.000 messages) in
TestTopic topic with default configuration where there are some consumers subscribed but
not active
3-stop producer and orderly shutdown the server
4-start server
During server startup JBM executes a select to load the persisted messages id's then
executes 180 selects loading 500 messages at time.
With 90.000 messages those 180 selects takes about 10 minutes. The DBMS is Oracle 10g
with dedicated instance on a separate machine with no more than 1% cpu load during test
and physical db on a very fast NAS.
While JBM is executing those selects, obviously the server startup hangs until the load
is finished.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira