BPEL: Adding a custom logger (such as com.xxx.yyy)

Some customers, and recently folks on the OTN BPEL forum reported that a newly added custom logger (at domain level) gets removed when a log level of a standard BPEL logger is changed.

This is a known issue, as we check during update just for loggers that contain the domain name like default.collaxa.cube

A workaround for now is to put the logger entry on the system level - add it to log4j-config.xml which can be found in $BPEL_HOME\integration\orabpel\system\config

I have filed bug 5161925 on this.

Having questions? send your feedback on adding a custom logger here