Skip to main content
Ex Libris Knowledge Center

Patron Purge (XML) giving log4j errors and not running

  • Article Type: General
  • Product: Voyager
  • Product Version: 8.2.0
  • Relevant for Installation Type: Dedicated-Direct; Direct; Local; Total Care

Problem Symptoms:
* Ran new Patron Purge (XML) job: PpatronPrg -p2011-12-31
* Job output:
PatronPurge start
Database server: localhost
User name: xxxdb
Audit file: /m1/voyager/xxxdb/rpt/audit.patpurge.20130109.085312
Output file: /m1/voyager/xxxdb/rpt/xml.patpurge.20130109.085312
Exception file path: /m1/voyager/xxxdb/rpt/
Purge date: 2011-12-31
Expire date: null
Running in test mode - no records will be updated
log4j:WARN No appenders could be found for logger (org.hibernate.impl.SessionFactoryImpl).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

* Job does not run

Cause:
Missing line in patronPurge-log4j.properties

Resolution:
1. cd /m1/voyager/xxxdb/ini
2. Edit patronPurge-log4j.properties
3. Locate these lines:
log4j.logger.com.exlibris.voyager=WARN, LOGFILE
log4j.logger.com.endinfosys.voyager=WARN, LOGFILE
4. After lines above, add this line:
log4j.logger.org.hibernate.impl.SessionFactoryImpl=WARN, LOGFILE
5. Save changes.

Category: Batch jobs


  • Article last edited: 10/8/2013