Skip to Main Content

Java Development Tools

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

JDeveloper 12.2.1 gives error when I run the app. (Failure occurred in the execution of deployment r

Azhar AltafFeb 10 2017 — edited Feb 20 2017

JDelveloper 12.2.1 is throwing the following deployment exception when I tried to run app.

Please help me to resolve this exception.

####<Feb 10, 2017, 8:39:10,890 AM PKT> <Info> <Deployer> <adiscmd> <DefaultServer> <[ACTIVE] ExecuteThread: '26' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <62bf1925-cf67-4baf-986a-222e6dac6a14-00000037> <1486697950890> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-149060> <Module empty.jar of application piccsFms successfully transitioned from STATE_NEW to STATE_PREPARED on server DefaultServer.>

####<Feb 10, 2017, 8:39:10,891 AM PKT> <Info> <Deployer> <adiscmd> <DefaultServer> <[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <62bf1925-cf67-4baf-986a-222e6dac6a14-00000038> <1486697950891> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-149059> <Module ModelEJB.jar of application piccsFms is transitioning from STATE_NEW to STATE_PREPARED on server DefaultServer.>

####<Feb 10, 2017, 8:39:11,704 AM PKT> <Info> <Deployer> <adiscmd> <DefaultServer> <[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <62bf1925-cf67-4baf-986a-222e6dac6a14-00000038> <1486697951704> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-149061> <Module ModelEJB.jar of application piccsFms failed to transition from STATE_NEW to STATE_PREPARED on server DefaultServer.>

####<Feb 10, 2017, 8:39:12,497 AM PKT> <Info> <Deployer> <adiscmd> <DefaultServer> <[ACTIVE] ExecuteThread: '29' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <62bf1925-cf67-4baf-986a-222e6dac6a14-00000036> <1486697952497> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-149061> <Module ViewController of application piccsFms failed to transition from STATE_NEW to STATE_PREPARED on server DefaultServer.>

####<Feb 10, 2017, 8:39:12,538 AM PKT> <Error> <Deployer> <adiscmd> <DefaultServer> <[ACTIVE] ExecuteThread: '29' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <62bf1925-cf67-4baf-986a-222e6dac6a14-00000036> <1486697952538> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-149265> <Failure occurred in the execution of deployment request with ID "1721529213600" for task "0" on [partition-name: DOMAIN]. Error is: "weblogic.utils.ErrorCollectionException:

There are 2 nested errors:

weblogic.application.ModuleException: java.util.NoSuchElementException

  at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:114)

  at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)

  at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:192)

  at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:187)

  at weblogic.application.utils.StateMachineDriver$ParallelChange.run(StateMachineDriver.java:83)

  at weblogic.work.ContextWrap.run(ContextWrap.java:46)

  at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:666)

  at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)

  at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)

  at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)

  at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)

  at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:640)

  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:406)

  at weblogic.work.ExecuteThread.run(ExecuteThread.java:346)

Caused by: java.util.NoSuchElementException

  at java.util.ArrayList$Itr.next(ArrayList.java:854)

  at org.eclipse.persistence.internal.jpa.metadata.MetadataDescriptor.getPrimaryKeyField(MetadataDescriptor.java:1048)

  at org.eclipse.persistence.internal.jpa.metadata.MetadataDescriptor.getPrimaryKeyFieldName(MetadataDescriptor.java:1057)

  at org.eclipse.persistence.internal.jpa.metadata.accessors.mappings.ObjectAccessor.processForeignKeyRelationship(ObjectAccessor.java:634)

  at org.eclipse.persistence.internal.jpa.metadata.accessors.mappings.ObjectAccessor.processOwningMappingKeys(ObjectAccessor.java:708)

  at org.eclipse.persistence.internal.jpa.metadata.accessors.mappings.ManyToOneAccessor.process(ManyToOneAccessor.java:123)

  at org.eclipse.persistence.internal.jpa.metadata.MetadataProject.processOwningRelationshipAccessors(MetadataProject.java:1595)

  at org.eclipse.persistence.internal.jpa.metadata.MetadataProject.processStage3(MetadataProject.java:1848)

  at org.eclipse.persistence.internal.jpa.metadata.MetadataProcessor.processORMMetadata(MetadataProcessor.java:577)

  at org.eclipse.persistence.internal.jpa.deployment.PersistenceUnitProcessor.processORMetadata(PersistenceUnitProcessor.java:607)

  at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:1948)

  at org.eclipse.persistence.jpa.PersistenceProvider.createContainerEntityManagerFactoryImpl(PersistenceProvider.java:347)

  at org.eclipse.persistence.jpa.PersistenceProvider.createContainerEntityManagerFactory(PersistenceProvider.java:313)

  at weblogic.persistence.BasePersistenceUnitInfo.initializeEntityManagerFactory(BasePersistenceUnitInfo.java:614)

  at weblogic.persistence.BasePersistenceUnitInfo.init(BasePersistenceUnitInfo.java:202)

  at weblogic.persistence.BaseJPAIntegrationProvider.createPersistenceUnitInfo(BaseJPAIntegrationProvider.java:54)

  at weblogic.persistence.AbstractPersistenceUnitRegistry.storeDescriptors(AbstractPersistenceUnitRegistry.java:422)

  at weblogic.persistence.AbstractPersistenceUnitRegistry.loadPersistenceDescriptor(AbstractPersistenceUnitRegistry.java:340)

  at weblogic.persistence.ModulePersistenceUnitRegistry.<init>(ModulePersistenceUnitRegistry.java:62)

  at weblogic.ejb.container.deployer.EJBModule.setupPersistenceUnitRegistry(EJBModule.java:186)

  at weblogic.ejb.container.deployer.EJBModule$1.execute(EJBModule.java:274)

  at weblogic.persistence.PersistenceUnitRegistryInitializer.setupPersistenceUnitRegistries(PersistenceUnitRegistryInitializer.java:58)

  at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)

  at weblogic.application.internal.ExtensibleModuleWrapper$PrepareStateChange.next(ExtensibleModuleWrapper.java:295)

  at weblogic.application.internal.ExtensibleModuleWrapper$PrepareStateChange.next(ExtensibleModuleWrapper.java:285)

  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)

  at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:109)

  ... 13 more

and

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Mar 10 2017
Added on Feb 10 2017
3 comments
331 views