Oracle WebLogic Class Loader Hierarchy

-
The detailed order for WebLogic class loading in top-down hierarchy follows:
  1. System Classloader
    1. WebLogic implementation classes
    2. Classes in the system classpath
    3. PRE_CLASSPATH and EXT_PRE_CLASSPATH
  2. Domain Classloader
    1. classes in the domain directory's lib folder
  3. Application Classloader
    1. Java EE shared libraries referenced in weblogic-application.xml
    2. Modules defined in the application
    3. Libraries from Java EE library
    4. Libraries from /APP-INF/lib
  4. Web Classloader
    1. Java EE shared libraries referenced in weblogic.xml
    2. Classes in WEB-INF/classes
    3. Libraries in WEB-INF/lib
WebLogic 10.3.3 allows for the Application to intercept the the System classloader. This is required for loading alternative versions of application libraries such as the Xerces and Ant. Doing so allows for the lower-level classloader (e.g. Web) to load classes/ libraries before the ones typically loaded by the System classloader.
In order to do this, the FilteringClassLoader mechanism – a classloader that sits between Domain and Application – has to be used. this needs to be specified by the prefer-application-packages or prefer-web-inf XML tags.
If it interests you, the class-loading hierarchy for JBoss can be found here.

Comments

Post a Comment

Popular posts from this blog

Understanding ITIL Service Management the UML way…

-
Image
I originally had a great deal of difficult reconciling the differences amongst ITIL Change Management, Incident Management, and Problem Management. Having researched on the subjects and understanding them better now, I’ve tried to put the concepts together using a UML class diagram to capture my understanding and to keep it imprinted. Similarly, I wanted to differentiate the various categories of changes (Standard, Emergency, Normal) using an easy to understand & self-explanatory manner – a UML Activity Diagram!
Read more

Apache Web Server Troubleshooting

-
How to troubleshoot Apache Web Server? A few standard commands to know by hard: To confirm the modules that are or will be loaded in Apache: apachectl –M [-f <conf filename>] To check the virtual host load pattern: apachectl –S [-f <conf filename>] To test a httpd.conf file: apachectl –t [-f <conf filename>] To maintain the http server: apachectl start|stop|restart To start with a specified configuration file: apachectl –f <conf filename> Create a minimalist httpd.conf. Something like: Listen 80 ServerName myserver.com:80 ServerAdmin admin@myserver.com #ServerRoot " . " ServerRoot " /usr/local/apache2 " User nobody Group nobody #DocumentRoot " ..\wwwroot " DocumentRoot " /home/data/html " ErrorLog " logs/basic_apache.log " LogLevel debug #LoadModule log_config_module modules/mod_log_config.dll LoadModule log_config_module modules/mod_log_config.so <IfModule log_config_module> LogFormat " %h %l
Read more