Win a copy of Java Database Connections & Transactions (e-book only) this week in the JDBC forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Devaka Cooray
  • Knute Snortum
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Bear Bibeault
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Ron McLeod
  • Piet Souris
  • Frits Walraven
  • Ganesh Patekar
  • Tim Holloway
  • salvin francis

Jboss 6.1 Hibernate Warning  RSS feed

Ranch Hand
Posts: 87
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am using JBoss 6.1,When i deploy my application,i get the below warning.

WARN [org.hibernate.ejb.internal.EntityManagerFactoryRegistry] (ServerService Thread Pool -- 65) HHH000436: Entity manager factory name (MY_PERSISTENCE) is already registered. If entity manager will be clustered or passivated, specify a unique value for property 'hibernate.ejb.entitymanager_factory_name

Can some one please help on how to over come this warning.
Thanks in Advance.
Ranch Hand
Posts: 259
Android Angular Framework AngularJS Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I can offer only some thin advice here, since I have been working with Wildfly 8/9 recently. I would try undeploying (or shutting down, deleting your war/ear from the deployment directory, and restarting) Jboss 6. Then look at either your server and/or boot logs, or the jmx-console, to see if you already have something out there called MY_PERSISTENCE). If it is there, you know that something else that either you deployed yourself, or which came with JBoss has an entity manager factory called MY_PERSISTENCE (I don't think it has something called that. Rather java:/ExampleDS is more likely). If that is the case, just rename your entity manager factory name to something else and redeploy it. In fact, I doubt this could be the problem, because I think JBoss even back at '6 had partitioning of the JNDI namespace.

Otherwise, if after undeploying your app, you find there is no MY_PERSISTENCE anywhere, it could mean you are redundantly defining this within your own application. Do you perhaps have your context getting loaded two different ways? Two copies of the configuration file?

Sorry I cannot be more explicit. I hope I have helped.
Get off me! Here, read this tiny ad:
how do I do my own kindle-like thing - without amazon
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!