I've come across this error a few different times. The causes were as follows:
I had a duplicate mapping in my hibernate configuration (check config file/code)
Two threads were attempting to build the HibernateSessionFactory object at the same time. A synchronized lock on the initialization code fixed this.
An attempt to build the HibernateSessionFactory failed, but is being called again. The Hibernate Configuration object didn't get cleared out, so the entities are being processed again.
You have two entity classes being mapped to the same file. Hibernate will choke on this as well.