I have an app that is using mdbs. The mdbs process messages and return a response, ultimately through networking protocols. They must response within a finite amount of time, which they do - but not on the first call, since this seems to be when the mdb is first created. Is there a way of preloadng the mdbs on app server start up and keeping them in memory regardless of usage? is this what @ActiveConfig minPoolSize=x will do?
Setting @ActiveConfigParam minPoolSize to something greater than one seems to make the problem worse, as of course more beans need to be created when first invoked. Keeping this to the default of 1 seems to be the best option at the moment. I'll take a look at the message queue specs to see if that is where I need to be.