the slow start up is probably due to the 'millions of messages' being loaded in to memory at startup.
The 'createTablesOnStartup' attribute only calls a few sql statments so changing this is unlikely to make any difference.
The 'UsingBatchUpdates' is for updates only so again thi sshouldn't make any difference to the start up time.
We have millions of messages which are pending to be delivered from the JBoss messaging server.
Did you try playing with paging?
Thanks for the handful replies.
we have also configured paging parameters for our JBoss Messaging Server in Prod Environment for our older version of JBM
Values set for FullSize, PageSize, and DownCacheSize are 500,250 and 250 respectively.
Before setting these values, we used to often get OutOfMemory Exception in our Prod Environment.After setting these values, we never get OutOfMemory exception..Pls suggest whether the values set is optimal or less aggressive for JBM at prod environment which currently handles millions and millions of messages.
Any suggestion or solution to overcome the increased startup time !!!!.
Kindly shed some light on the possible alternative way to overcome as early as possible
Really I would appreciate it...
Don't restart? Why not set the params really low (50,25,25) and see where that gets you...
OK i will consider ur option(changing those paging values) also.
In the meantime we have tested a scenario...We did not change any Paging parameters value for this test.
With our Prod Environment setup, it took around 20 to 30 minutes for the JBM to get started.We also observed that while starting up,all those DDL and DML statements specified in the XXX-persistence-service.xml were getting executed and also we have noted some updates/indexes mentioned in xml file were being recreated for all those millions and million of messages.
If we have make that flag false, server starts up pretty fast...
So my question wud be .....
Once the initial set of tables are created, can this flag be set to false ? Will it affect the consistency or any other data when the server is restarted(normal shutdown or abnormal shutdown)...
Kindly provide ur valuable suggestion ....
If you've already created your tables then set createTablesOnStartup to false, since they're already there!
That's what it's for.