private void loadMessagesClass(){
  try {
    Class.forName(FULL_MESSAGES_CLASS_NAME);
  }
 catch (  ClassNotFoundException e) {
    _log.warn("can't find Messages class",e);
  }
}

private void loadMessagesClass ( ) { try { Class . forName ( FULL_MESSAGES_CLASS_NAME ) ; } catch ( ClassNotFoundException e ) { _log . warn ( "can't find Messages class" , e ) ; } }
there is bug in log4j which will cause deadlock when calling logmanager . resetconfiguration ( ) and application is performing log . error ( msg , e ) , log4j will call e . tostring ( ) method which eventually create new messages instance , logfactory . getlogger ( ) will be called when loading messages first time and try to get lock on ht which probably hold by another thread ( resetconfiguration ) ; before calling logmanager . resetconfiguration ( ) we will load messages class first to avoid race condition .
