Most of you might already worked on this. Anyone who has not got chance to work on it and a note to myself on the step by step Apache Derby datasource configuration in Weblogic.
Thursday, October 24, 2013
Tuesday, July 23, 2013
Flush Weblogic Cache
Can't see the newly developed changes after the deployment of the build to Weblogic Server. This is because Weblogic Caches the application so that when you access the applications it can load faster every second attempt after the deployment. The only way to get new changes to be visible is to get rid of old one's. How is that done? Answer: Flush the Weblogic Cache on all Weblogic nodes where Applications is deployed to. Usually clearing the Weblogic cache results in resolving some unknown problems too.
Tuesday, September 20, 2011
How to Prevent the 'WLS_DIAGNOSTICSxxxxxx.DAT' file from Growing Too Large
The Archive component of the WebLogic Diagnostic Framework (WLDF) captures and persists all data events, log records, and metrics collected by WLDF from server instances and applications running on them. You can configure WLDF to archive diagnostic data to a file store or a Java Database Connectivity (JDBC) data source. If you choose to archive diagnostic data to a file store, this file would stored in <DOMAIN_NAME>/servers/<SERVER_NAME>/data/store/diagnostics.
Under some conditions, these archived files may grow bigger and bigger and can not be removed automatically if you have not done special configuration. e.g., if JDBC connection profiling is enabled, etc.
Under some conditions, these archived files may grow bigger and bigger and can not be removed automatically if you have not done special configuration. e.g., if JDBC connection profiling is enabled, etc.
Subscribe to:
Posts (Atom)