nigeldeakin wrote:Thanks again for your response, Nigel. This does, indeed, sound logical. Unfortunately, we need something that must be deployed within a month and available for GF 2.1.1, so it appears that we may have to solve this on our own with an enterprise application (given your comment about session beans and MessageListener). Please do update this thread when the MDB modification is avialable in a release version of GF so we can plan to take advantage of it going forward. Thanks.
Your requirement is a reasonable one, however. A possible enhancement might be as follows: if the MDB cannot be started, it doesn't throw an exception. Instead it logs a warming message and spawns a thread which periodically attempts to start the MDB in the background. Would this meet your needs?