Eclipse Community Forums: EclipseLink » A non-read-only mapping must be defined for the sequence number field

Home » Eclipse Projects » EclipseLink » A non-read-only mapping must be defined for the sequence number field(sequencing problem)

A non-read-only mapping must be defined for the sequence number field [message #991351]

Tue, 18 December 2012 11:29

Eclipse User

I have used Eclipselink for years, currently working on 3 projects that use it. Recently I migrated to a 64-bit windows 7 machine, installed Juno and updated to Eclipselink 2.4.1. Now every project tells me when I try to run it that a non-read ony mapping is needed for the sequence field. This did not happen before, it happens now even if I go back to previous versions of eclipselink, and happens even if I am using native sequencing. Both the sessions.xml and project.xml are configured for native-sequence, and every field on my entities that maps to a primary key, native sequence column is NOT flagged as read-only. Yet the exception is thrown for EVERY entity.

I have tried running java 6 and java 7, same problem. I am at my wits end.

. [message #991354 is a reply to message #991351]

Tue, 18 December 2012 11:54

Eclipse User

No Message Body

[Updated on: Tue, 18 December 2012 16:35] by Moderator

Re: . [message #991525 is a reply to message #991354]

Wed, 19 December 2012 11:38

Eclipse User

Please include the exception and stack. Also try enabling logging on finest, there could be another error further up that is causing the issue.

What version are you upgrading from?

Re: [message #1014924 is a reply to message #991525]

Tue, 26 February 2013 15:04

Eclipse User

Hi

I have the same problem. When I deploy EclipseLink project using Class - everything is OK. When I deploy it using xml I have this type of exception on every descriptor.
I use Native sequencing on Oracle platform.

Thanks

Local Exception Stack: 
Exception [EclipseLink-41] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DescriptorException
Exception Description: A non-read-only mapping must be defined for the sequence number field.
Descriptor: RelationalDescriptor(com.iengine.ie.backend.entities.model.Contact --> [DatabaseTable(CONTACT)])
	at org.eclipse.persistence.exceptions.DescriptorException.mappingForSequenceNumberField(DescriptorException.java:928)
	at org.eclipse.persistence.internal.descriptors.ObjectBuilder.validate(ObjectBuilder.java:3715)
	at org.eclipse.persistence.descriptors.ClassDescriptor.selfValidationAfterInitialization(ClassDescriptor.java:3876)
	at org.eclipse.persistence.descriptors.ClassDescriptor.validateAfterInitialization(ClassDescriptor.java:5688)
	at org.eclipse.persistence.descriptors.ClassDescriptor.postInitialize(ClassDescriptor.java:3547)
	at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.initializeDescriptors(DatabaseSessionImpl.java:526)
	at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.initializeDescriptors(DatabaseSessionImpl.java:476)
	at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.initializeDescriptors(DatabaseSessionImpl.java:435)
	at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.postConnectDatasource(DatabaseSessionImpl.java:676)
	at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.login(DatabaseSessionImpl.java:634)
	at com.iengine.ie.infrastruct.persistence.PersistenceManager.<init>(PersistenceManager.java:233)
	at com.iengine.ie.infrastruct.persistence.PersistenceManager.getInstance(PersistenceManager.java:284)
	at com.iengine.ie.infrastruct.persistence.PersistenceManager.getInstance(PersistenceManager.java:297)
	at com.iengine.ie.infrastruct.persistence.IESession.acquireSession(IESession.java:730)
	at com.iengine.ie.backend.eventmanagement.session.EventHandlerBean.getActions(EventHandlerBean.java:89)
	at com.iengine.ie.backend.eventmanagement.session.EventHandlerBean.onMessage(EventHandlerBean.java:305)
	at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:585)
	at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:488)
	at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:385)
	at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
	at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
	at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)
	at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
	at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
	at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
	at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
	at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

Re: [message #1015428 is a reply to message #1014924]

Thu, 28 February 2013 09:46

Eclipse User

Can you provide the log information and the versions this worked on as well as how you migrated the project file? It might also help to make a simple test case that only uses a single simple entity and see if that gets the problem, so that you can post it here or use to file a bug.

Best Regards,
Chris

Previous Topic:	JPA-RS problem: java.lang.ClassCastException: java.util.ArrayList cannot be cast...
Next Topic:	Group by statement is not rendered with criteria api

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 10:53:59 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter