SOFTware is HARD

So many timeout settings… it’s ridiculous!

With respect to the Weblogic server, there are several runtime states that are interesting. In addition, certain events/ commands lead to the transitions to other known states. I attempted to capture the state transitions and events into a UML state diagram for easy reference. States in brown are end-states while those in yellow are transitional.

The detailed order for WebLogic class loading in top-down hierarchy follows: System Classloader WebLogic implementation classes Classes in the system classpath PRE_CLASSPATH and EXT_PRE_CLASSPATH Domain Classloader classes in the domain directory's lib folder Application Classloader Java EE shared libraries referenced in weblogic-application.xml Modules defined in the application Libraries from Java EE library Libraries from /APP-INF/lib Web Classloader Java EE shared libraries referenced in weblogic.xml Classes in WEB-INF/classes 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 classloa...

Step 1: You need to create a new Execute Queue (e.g. CriticalAppQueue) Click the name of the server instance where you will add the execute queue. Select the Monitoring —> General tab. Click the Monitor All Active Queues text link to display the execute queues that the selected server uses. Click the Configure Execute Queue text link to display the execute queues that you can modify. Click the Configure a New Execute Queue link. On the Execute Queue Configuration tab modify the following attributes or accept the system defaults: Queue Length : Always leave the Queue Length at the default value of 65536 entries. The Queue Length specifies the maximum number of simultaneous requests that the server can hold in the queue. The default of 65536 requests represents a very large number of requests; outstanding requests in the queue should rarely, if ever reach this maximum value. If the maximum Queue Length is reached, WebLogic Server automatically doubles the size of the queue to...