[ARIES-977] JPA Deployment fails for WAB

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: jpa-container-context-1.0.1
• Component/s: JPA

Environment

Hibernate/ Glassfish/ Felix / Jpa Container 1.0.0

• Assignee: Unassigned
• Reporter: Tony L
• Created: 30/Nov/12 19:42
• Updated: 03/Dec/12 19:53
• Resolved: 03/Dec/12 19:53

Description

When I attempt to deploy a WAB with Aries JPA this is what happens:

SEVERE: java.lang.IllegalStateException: The bundle com.somebundle/0.0.1.SNAPSHOT is not started.
at org.apache.aries.jpa.container.unit.impl.JndiDataSource.getDs(JndiDataSource.java:61)
at org.apache.aries.jpa.container.unit.impl.DelayedLookupDataSource.getConnection(DelayedLookupDataSource.java:36)
at org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider.getConnection(InjectedDataSourceConnectionProvider.java:71)
at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:114)
at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2163)
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2159)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1383)
at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:954)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:887)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73)
at org.apache.aries.jpa.container.impl.EntityManagerFactoryManager.createEntityManagerFactories(EntityManagerFactoryManager.java:329)
at org.apache.aries.jpa.container.impl.EntityManagerFactoryManager.bundleStateChange(EntityManagerFactoryManager.java:175)
at org.apache.aries.jpa.container.impl.PersistenceBundleManager.modifiedBundle(PersistenceBundleManager.java:296)
at org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:453)
at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:237)
at org.osgi.util.tracker.BundleTracker$Tracked.bundleChanged(BundleTracker.java:413)
at org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:807)
at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:729)
at org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:610)
at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:3758)
at org.apache.felix.framework.Felix.access$600(Felix.java:80)
at org.apache.felix.framework.Felix$FelixResolver.fireResolvedEvents(Felix.java:4296)
at org.apache.felix.framework.Felix$FelixResolver.resolve(Felix.java:4062)
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3436)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1727)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:909)
at

It seems that there is an expectation that the bundle should be in a STARTED state when it is in RESOLVED. I think this is very similar to issue https://issues.apache.org/jira/browse/ARIES-832 except that it happens in a different place.

This is a very serious issue, currently no known workarounds.

Issue Links

• is duplicated by: ARIES-978 Aries JPA does not work with Hibernate