If

log4j.category.org.hibernate=LEVEL (old version)
or
log4j.logger.org.hibernate=LEVEL (new version)

doesn't work for you and logging is limited only by the root logger`s log level, then have a look at the way you configure log4j.

you should use 'logger = Logger.getLogger(ClassName);'
where className can either be a string(class name) or the class which actually logs the messages,
logging will work even if you pass an empty String, bit since log4j wont know from which package it is receiving the messages the categorized logging wont work.

People using log4j for a long time will recognize that this is the very basic of log4j, but this is a place where people may make mistakes since usually we have a seperate class for configuring the log4j and they may hardcode the loggername to something they like instead of passing the classname as a parameter.

Inorder to see the log4j confguration messages (the internal log4j debug messages) ,

if you use log4j xml:

<log4j :configuration debug="true"></log4j>

if you use log4j properties:
Log4j.debug=true

Adobe`s creative suite seems to have a problem recognising Type1 (.pfm) Fonts.

the workaround is to copy the .pfm file along with the associated .pfb file to

"C:\Program Files\Common Files\Adobe\Fonts"

restart your program and it should work.