FusionReactor 4.5.0 extends the OSGi container concept used with FusionReactor 4.0.0 by making many core components OSGi Bundles. Although there is no visible difference to the user (except in FusionReactor -> Plugins -> All Bundles), the increased modularity allows for greater reliability and fault tolerance, and allows us to implement functionality using the latest technology, modularizing the application according to industry best practice.
You may be asked by support to provide a startup bundle dump. This technote illustrates how to go about producing this.
As FusionReactor starts, it assembles a set of OSGi bundles, which together comprise the whole functionality of the system. This assembly is drawn from instance/plugins as well as instance/osgi/env/bundle.
As these bundles are loaded and started, FusionReactor tracks their status. Because the output from this tracking is rather large, it is suppressed by default.
When enabled, three new sections are logged to the container's default log output file (or console, in some cases):
The former two blocks provide full information about each loaded bundle:
To enable the dump, the Java VM option DUMP_BUNDLES must be applied.
For further information on configuring Java options for your J2EE container, please refer to its user guide.
Once enabled, the bundle dump will be output to your containers default log destination. This could be a localhost-*.log (Tomcat) or coldfusion-event.log (CF).
This file should be mailed back to support, along with any other requested information.
|Components:||Plugins + OSGi|
|Last Updated:||16/May/12 3:27 PM|
Comments are closed.