Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EclipseLink » No Persistence provider for EntityManager named default
No Persistence provider for EntityManager named default [message #1008590] Wed, 13 February 2013 08:45 Go to next message
stefano gufi is currently offline stefano gufi
Messages: 4
Registered: February 2013
Junior Member
Hy all,

during the migration of Oracle UIM 7.1.2 based on Kodo to 7.2 based on Eclipse link we get the error below in the code of Web Service in Java Language.

We also change the JPa provider from KODO to EclipseLink via WebLogic, but the error is the same.

Let me know if i have to share more details.

Thanks in advance

####<Feb 8, 2013 12:01:51 PM CET> <Notice> <Stdout> <CRPAS04> <UIM_MS1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <89a4783586755966:-ad58bad:13cb975a5f0:-8000-0000000000000171> <1360321311797> <BEA-000000> <2013-02-08 12:01:51,780 ERROR [<anonymous>] [ExtensionRuleMediator] [INV-180011] Failed to retrieve the extension point: No Persistence provider for EntityManager named default: The following providers:
org.eclipse.persistence.jpa.PersistenceProvider
kodo.persistence.PersistenceProviderImpl
org.apache.openjpa.persistence.PersistenceProviderImpl
Returned null to createEntityManagerFactory.
.
javax.persistence.PersistenceException: No Persistence provider for EntityManager named default: The following providers:
org.eclipse.persistence.jpa.PersistenceProvider
kodo.persistence.PersistenceProviderImpl
org.apache.openjpa.persistence.PersistenceProviderImpl
Returned null to createEntityManagerFactory.
..
..
####<Feb 8, 2013 12:01:52 PM CET> <Notice> <Stdout> <CRPAS04> <UIM_MS1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <89a4783586755966:-ad58bad:13cb975a5f0:-8000-000000000000017d> <1360321312226> <BEA-000000> <2013-02-08 12:01:52,226 ERROR [<anonymous>] [ServiceAdapter] Exception raised while commiting. Error: Unexpected exception in beforeCompletion: sync=org.eclipse.persistence.transaction.JTASynchronizationListener@56561df3

Internal Exception: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (UIM_USER.SYS_C0013549) violated
Re: No Persistence provider for EntityManager named default [message #1008708 is a reply to message #1008590] Wed, 13 February 2013 16:34 Go to previous messageGo to next message
Chris Delahunt is currently offline Chris Delahunt
Messages: 1034
Registered: July 2009
Senior Member
There are 2 errors. The first saying there isn't a provider for a 'default' persistence unit. Do you have a persistence.xml with a persistence unit named 'default'? More information such as the stack trace and configuration would be needed to debug this one further if it causes an issue with running the app - it is logged under the 'Notice' log level, so it might not be an issue.

The second indicates a persistence unit is successfully being used with a transaction, but that changes within the transaction violate a unique constraint. This would require looking into the application code to debug further.

Best Regards,
Chris
Re: No Persistence provider for EntityManager named default [message #1009228 is a reply to message #1008708] Thu, 14 February 2013 18:00 Go to previous messageGo to next message
stefano gufi is currently offline stefano gufi
Messages: 4
Registered: February 2013
Junior Member
thanks vm for the feed, regarding the error, it could be related to a DB issue?

Thanks in advance
Stefano
Re: No Persistence provider for EntityManager named default [message #1010872 is a reply to message #1009228] Mon, 18 February 2013 11:32 Go to previous messageGo to next message
stefano gufi is currently offline stefano gufi
Messages: 4
Registered: February 2013
Junior Member
This's the error after have made this change

Adding uim-entities.jar in class path and persistence.xml of uim-entities.jar has following entry

<persistence-unit name="default" transaction-type="JTA">
<provider>
org.eclipse.persistence.jpa.PersistenceProvider
</provider>


####<Feb 18, 2013 11:33:44 AM CET> <Notice> <Stdout> <CRPAS04> <UIM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <89a4783586755966:713c92fe:13cec26ce29:-8000-0000000000005a01> <1361183624484> <BEA-000000> <2013-02-18 11:33:44,483 ERROR [<anonymous>] [ExtensionRuleMediator] [INV-180011] Failed to retrieve the extension point: No Persistence provider for EntityManager named default: The following providers:
org.eclipse.persistence.jpa.PersistenceProvider
kodo.persistence.PersistenceProviderImpl
org.apache.openjpa.persistence.PersistenceProviderImpl
Returned null to createEntityManagerFactory.
.
javax.persistence.PersistenceException: No Persistence provider for EntityManager named default: The following providers:
org.eclipse.persistence.jpa.PersistenceProvider
kodo.persistence.PersistenceProviderImpl
org.apache.openjpa.persistence.PersistenceProviderImpl
Returned null to createEntityManagerFactory.
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:154)
at oracle.communications.platform.persistence.impl.PersistentBaseImpl.getPersistenceManagerFactory(PersistentBaseImpl.java:311)


Error Codes
---------------------------------------------------
Unexpected exception in beforeCompletion: sync=org.eclipse.persistence.transaction.JTASynchronizationListener@143d424c Exception [EclipseLink-5011] (Eclipse Persistence Services - 2.1.3.v20110304-r9073); org.eclipse.persistence.exceptions.OptimisticLockEx


any suggestions?

Thanks in advance.
Re: No Persistence provider for EntityManager named default [message #1011425 is a reply to message #1010872] Tue, 19 February 2013 14:54 Go to previous message
Chris Delahunt is currently offline Chris Delahunt
Messages: 1034
Registered: July 2009
Senior Member
You might want to take the first message to a WebLogic or UIM forum or support, because as I mentioned, it is showing up only as a notice not an error and there is no indication why it is occuring. Unless you are deploying a persistence unit named 'default', and are unable to deploy your application and use the persistence unit.

The second error is similar to the second error in the first post. This time, instead of a database constraint causing the transaction to fail, it is an optimistic lock exception. It shows that a persistence unit is deployed and working. The problem is an entity within the transaction is stale, and the exception is thrown to prevent overwriting with stale data. You need the full exception stack trace and to find out what the application is doing within the transaction.

Best Regards,
Chris
Previous Topic:No Persistence Services when called from rcp application
Next Topic:DBWS Error on Deployment
Goto Forum:
  


Current Time: Sat Oct 25 17:38:37 GMT 2014

Powered by FUDForum. Page generated in 0.02688 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software