Sometimes you want to customize logging level for given package in your application (to see tracing details for example). If you’re using commons-logging library the configuration file is called “commons-logging.properties” and it should be places somewhere on classpath.
Then we can configure SimpleLog back-end just declared in simplelog.properties:
You place those two files on classpath, redeploy application and … NOTHING HAPPENS. Those files aren’t visible!
Hibernate is a library that maps database tables to Java objects. Is performance problems arise it’s very easy to add database caching for application using Hibernate (just few options in config file). Hibernate is shipped with EHCache, default cache implementation. It works well and is easy to setup.
Sometimes you have to use another caching library that has no direct support for Hibernate. Here the Hibernate API comes into play. I’ll show you how to plug Websphere’s DistributedMap into Hibernate.
Recently I was asked to integrate WXS (Websphere Extreme Scale, commercial cache implementation from IBM) into existing WPS (Websphere Process Server)-based project to implement read-only non-distributed cache (one independent cache instance per JVM). The idea is to plug cache implementation using 2nd level cache interfaces defined by Hibernate.
I plugged in the objectgrid.jar into hibernate configuration:
WebSphere uses SQL databases for internal managment of MQ queues (Derby database engine under the covers). Sometimes you need to reset their state. Here’s the script that erase and recreate BPEDB database state (tested under WS 6.1.2):
rm -rf $WID_HOME/pf/wps/databases/BPEDB
echo "CONNECT 'jdbc:derby:$WID_HOME/pf/wps/databases/BPEDB;create=true' AS BPEDB;"|\
Sometimes you see that Eclipse stops responding and causes 100% of CPU usage (UI controls not redrawn). The only action can be taken then is to kill eclipse process.
I discovered that it’s caused by big console output option. Test suite with low level (DEBUG) messages are able to kill Eclipse IDE, after setting log level to WARN no such problems are present.
You can also disable Limiting console output. It helped when no verbosity could be changed by logging configuration.