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, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content