[
http://jira.jboss.com/jira/browse/JBMESSAGING-1162?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1162:
--------------------------------------
There is a very clear link between fullSize and the amount of messages loaded at startup -
this is the max. number of messages it will load at startup. This is also documented in
the user guide.
90000 x 1kb = about 90MB of data. If your Oracle is taking 10 mins to load this, then tune
Oracle! Oracle is very tunable.
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