Run logic AFTER oc4j started

Question

My J2EE requires a lot of initialization action for data caching and resources preload. Typically, this initialization action takes 5 mins to finish. I execute this action in my servlet's init() function, which is invoked during OC4J. However, in my oc4j, I need to run 5 J2EE applications of this kind. It means my OC4J takes 25 mins to start. It makes my oc4j 'seems to be' failed to start for most of the time.
Apart from servlet's init() and startup class, is there any way I can execute my initialization actions AFTER oc4j startup? It can at least make my oc4j start normally and timely. Thx

Answer 1

There's no inherent functionality in OC4J that can do this for you. I think you need to look at your architecture -- if this was me, I'd be offloading the work to a MDB or something of that manner so it can be executed asynchronously and in parallel. The tricky bit there is to work out how to stop the corresponding applications from being used until there cache initialization is completed, and perhaps also sharing the cache between the worker and the consumer. You could synchronize the application aliveness on a file, or perhaps use an MBean in which an active attribute is checked by the application and updated from the end result of the MDB processing.
-steve-