[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1162) JBM takes eons to startup with topic persisted messages within db

[Tim Fox (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1162?page=comments#action_12390861 ] 
            
Tim Fox commented on JBMESSAGING-1162:
--------------------------------------

Can you explain in more detail what you mean by "JBM refused to start.." - did it give you an error message? If so please post it.

If you set fullSize, JBM should never try to load more messages than that on startup. It should not force you to change fullSize either. If it does then that is a bug.

Maybe it is this bug http://jira.jboss.org/jira/browse/JBMESSAGING-1139 which I fixed about a month ago and will be in the SP2 release I am doing today?

> 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