[Bug 1031694] New: hibernate-entitymanager is missing org/hibernate/jpa/internal/EntityManagerMessageLogger_$logger.class
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1031694
Bug ID: 1031694
Summary: hibernate-entitymanager is missing
org/hibernate/jpa/internal/EntityManagerMessageLogger_
$logger.class
Product: Fedora
Version: rawhide
Component: hibernate
Assignee: puntogil(a)libero.it
Reporter: mgoldman(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
puntogil(a)libero.it
Description of problem:
When deploying a sample application - WildFly i throwing this error:
14:44:15,801 INFO [org.jboss.as.jpa] (MSC service thread 1-7) JBAS011401: Read
persistence.xml for primary
14:44:15,889 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service
thread 1-5) JBAS010400: Bound data source
[java:jboss/datasources/KitchensinkQuickstartDS]
14:44:15,891 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 14)
JBAS011409: Starting Persistence Unit (phase 1 of 2) Service
'jboss-as-kitchensink.war#primary'
14:44:15,906 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool --
14) MSC000001: Failed to start service
jboss.persistenceunit."jboss-as-kitchensink.war#primary".__FIRST_PHASE__:
org.jboss.msc.service.StartException in service
jboss.persistenceunit."jboss-as-kitchensink.war#primary".__FIRST_PHASE__:
java.lang.ExceptionInInitializerError
at
org.jboss.as.jpa.service.PhaseOnePersistenceUnitServiceImpl$1$1.run(PhaseOnePersistenceUnitServiceImpl.java:120)
at
org.jboss.as.jpa.service.PhaseOnePersistenceUnitServiceImpl$1$1.run(PhaseOnePersistenceUnitServiceImpl.java:102)
at java.security.AccessController.doPrivileged(Native Method)
[rt.jar:1.7.0_45]
at
org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:463)
[wildfly-security-manager.jar:1.0.0.Beta3]
at
org.jboss.as.jpa.service.PhaseOnePersistenceUnitServiceImpl$1.run(PhaseOnePersistenceUnitServiceImpl.java:129)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[rt.jar:1.7.0_45]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[rt.jar:1.7.0_45]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
[jboss-threads.jar:2.1.0.Final]
Caused by: java.lang.ExceptionInInitializerError
at
org.hibernate.jpa.boot.spi.Bootstrap.getEntityManagerFactoryBuilder(Bootstrap.java:43)
at
org.hibernate.jpa.boot.spi.Bootstrap.getEntityManagerFactoryBuilder(Bootstrap.java:55)
at
org.jboss.as.jpa.hibernate4.TwoPhaseBootstrapImpl.<init>(TwoPhaseBootstrapImpl.java:38)
at
org.jboss.as.jpa.hibernate4.HibernatePersistenceProviderAdaptor.getBootstrap(HibernatePersistenceProviderAdaptor.java:134)
at
org.jboss.as.jpa.service.PhaseOnePersistenceUnitServiceImpl.createContainerEntityManagerFactoryBuilder(PhaseOnePersistenceUnitServiceImpl.java:233)
at
org.jboss.as.jpa.service.PhaseOnePersistenceUnitServiceImpl.access$800(PhaseOnePersistenceUnitServiceImpl.java:59)
at
org.jboss.as.jpa.service.PhaseOnePersistenceUnitServiceImpl$1$1.run(PhaseOnePersistenceUnitServiceImpl.java:117)
... 8 more
Caused by: java.lang.IllegalArgumentException: Invalid logger interface
org.hibernate.jpa.internal.EntityManagerMessageLogger (implementation not found
in ModuleClassLoader for Module "org.hibernate:main" from local module loader
@2e44dfad (finder: local module finder @2bb8ee96 (roots:
/usr/share/wildfly/modules,/usr/share/wildfly/modules/system/layers/base)))
at org.jboss.logging.Logger$1.run(Logger.java:2254)
[jboss-logging.jar:3.1.3.GA]
at java.security.AccessController.doPrivileged(Native Method)
[rt.jar:1.7.0_45]
at org.jboss.logging.Logger.getMessageLogger(Logger.java:2227)
[jboss-logging.jar:3.1.3.GA]
at org.jboss.logging.Logger.getMessageLogger(Logger.java:2214)
[jboss-logging.jar:3.1.3.GA]
at
org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.<clinit>(EntityManagerFactoryBuilderImpl.java:120)
... 15 more
14:44:15,916 ERROR [org.jboss.as.controller.management-operation]
(DeploymentScanner-threads - 2) JBAS014613: Operation ("deploy") failed -
address: ([("deployment" => "jboss-as-kitchensink.war")]) - failure
description: {"JBAS014671: Failed services" =>
{"jboss.persistenceunit.\"jboss-as-kitchensink.war#primary\".__FIRST_PHASE__"
=> "org.jboss.msc.service.StartException in service
jboss.persistenceunit.\"jboss-as-kitchensink.war#primary\".__FIRST_PHASE__:
java.lang.ExceptionInInitializerError
Caused by: java.lang.ExceptionInInitializerError
Caused by: java.lang.IllegalArgumentException: Invalid logger interface
org.hibernate.jpa.internal.EntityManagerMessageLogger (implementation not found
in ModuleClassLoader for Module \"org.hibernate:main\" from local module loader
@2e44dfad (finder: local module finder @2bb8ee96 (roots:
/usr/share/wildfly/modules,/usr/share/wildfly/modules/system/layers/base)))"}}
14:44:15,918 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2)
JBAS015870: Deploy of deployment "jboss-as-kitchensink.war" was rolled back
with the following failure message:
{"JBAS014671: Failed services" =>
{"jboss.persistenceunit.\"jboss-as-kitchensink.war#primary\".__FIRST_PHASE__"
=> "org.jboss.msc.service.StartException in service
jboss.persistenceunit.\"jboss-as-kitchensink.war#primary\".__FIRST_PHASE__:
java.lang.ExceptionInInitializerError
Caused by: java.lang.ExceptionInInitializerError
Caused by: java.lang.IllegalArgumentException: Invalid logger interface
org.hibernate.jpa.internal.EntityManagerMessageLogger (implementation not found
in ModuleClassLoader for Module \"org.hibernate:main\" from local module loader
@2e44dfad (finder: local module finder @2bb8ee96 (roots:
/usr/share/wildfly/modules,/usr/share/wildfly/modules/system/layers/base)))"}}
14:44:15,923 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service
thread 1-5) JBAS010409: Unbound data source
[java:jboss/datasources/KitchensinkQuickstartDS]
14:44:15,928 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1)
JBAS015877: Stopped deployment jboss-as-kitchensink.war (runtime-name:
jboss-as-kitchensink.war) in 9ms
14:44:15,929 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2)
JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service
jboss.persistenceunit."jboss-as-kitchensink.war#primary".__FIRST_PHASE__
(missing) dependents: [service
jboss.deployment.unit."jboss-as-kitchensink.war".POST_MODULE]
JBAS014777: Services which failed to start: service
jboss.persistenceunit."jboss-as-kitchensink.war#primary".__FIRST_PHASE__
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Jup7g1xZtq&a=cc_unsubscribe
10 years, 4 months
[Bug 978306] New: glassfish-el: version 3.0 is available
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=978306
Bug ID: 978306
Summary: glassfish-el: version 3.0 is available
Product: Fedora
Version: rawhide
Component: glassfish-el
Severity: unspecified
Priority: unspecified
Assignee: davidx(a)fedoraproject.org
Reporter: msrb(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: davidx(a)fedoraproject.org,
java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com
Description of problem:
Final version of glassfish-el 3.0 has been recently released. This version is
needed by latest glassfish-jsp (#960404), but please don't rush with this
update. This is major update, glassfish-el 3.0 is reference implementation of
EL API from Java EE 7. We should first decide how and when to update to Java EE
7 APIs in Fedora.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=uWGDqTbbNA&a=cc_unsubscribe
10 years, 4 months