JBoss SOA-P very slow to start after adjusting JMS destination paging parameters

Solution Verified - Updated -

Issue

  • We adjusted the paging parameters (i.e. FullSize, PageSize, DownCacheSize) for some of our JMS destinations to avoid OutOfMemoryErrors when starting the server, but now the server is starting very slowly.After a pause of 5 minutes some errors are thrown and the server boots but our application is crippled because a JMS destination didn't deploy.

Environment

  • JBoss Enterprise SOA Platform (SOA-P)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.