[JBoss JIRA] (WFLY-1406) Hibernate cannot process package-info.java any more
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-1406?page=com.atlassian.jira.plugin.... ]
Scott Marlow commented on WFLY-1406:
------------------------------------
Or if there are other ideas, please suggest something else.
> Hibernate cannot process package-info.java any more
> ---------------------------------------------------
>
> Key: WFLY-1406
> URL: https://issues.jboss.org/browse/WFLY-1406
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Affects Versions: 8.0.0.Alpha2
> Reporter: Juergen Zimmermann
> Attachments: javap.log, server.log, server.log.zip, shop2.war, tar.log
>
>
> I tried the snapshot which contains Hibernate 4.3.0.Beta2. However, package-info.java files are causing problems. For instance, the package de.shop.artikelverwaltung.domain has a package-info.java which causes a NoClassDefFoundError:
> "IllegalName: de/shop/artikelverwaltung/domain.package-info". Please see the stacktrace below.
> Here is an example for package-info.java which was working with WildFly 8.0.0.Alpha1:
> @XmlAccessorType(FIELD)
> @Vetoed
> package de.shop.artikelverwaltung.domain;
> import static javax.xml.bind.annotation.XmlAccessType.FIELD;
> import javax.enterprise.inject.Vetoed;
> import javax.xml.bind.annotation.XmlAccessorType;
> The stacktrace:
> ...
> 09:29:53,880 WARN [org.jboss.modules] Failed to define class de/shop/artikelverwaltung/domain.package-info in Module "deployment.shop2.war:main" from Service Module Loader: java.lang.LinkageError: Failed to link de/shop/artikelverwaltung/domain/package-info (Module "deployment.shop2.war:main" from Service Module Loader)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:427) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:260) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:75) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.Module.loadModuleClass(Module.java:526) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:188) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final]
> at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader.findClass(ClassLoaderServiceImpl.java:218) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:423) [rt.jar:1.7.0_21]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356) [rt.jar:1.7.0_21]
> at org.hibernate.annotations.common.util.ReflectHelper.classForName(ReflectHelper.java:160) [hibernate-commons-annotations-4.0.2.Final.jar:4.0.2.Final]
> at org.hibernate.annotations.common.reflection.java.JavaReflectionManager.packageForName(JavaReflectionManager.java:121) [hibernate-commons-annotations-4.0.2.Final.jar:4.0.2.Final]
> at org.hibernate.cfg.AnnotationBinder.bindPackage(AnnotationBinder.java:262) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.cfg.Configuration.addPackage(Configuration.java:792) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.buildHibernateConfiguration(EntityManagerFactoryBuilderImpl.java:1174) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:839) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:836) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:368) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:835) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.HibernatePersistenceProvider.createContainerEntityManagerFactory(HibernatePersistenceProvider.java:142) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:213) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$800(PersistenceUnitServiceImpl.java:58) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:107) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final]
> Caused by: java.lang.NoClassDefFoundError: IllegalName: de/shop/artikelverwaltung/domain.package-info
> at java.lang.ClassLoader.preDefineClass(ClassLoader.java:646) [rt.jar:1.7.0_21]
> at java.lang.ClassLoader.defineClass(ClassLoader.java:785) [rt.jar:1.7.0_21]
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:344) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:422) [jboss-modules.jar:1.2.0.Final]
> ... 28 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (WFLY-1406) Hibernate cannot process package-info.java any more
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-1406?page=com.atlassian.jira.plugin.... ]
Scott Marlow reassigned WFLY-1406:
----------------------------------
Assignee: (was: Scott Marlow)
Someone with a windows machine should try to reproduce and debug this issue.
> Hibernate cannot process package-info.java any more
> ---------------------------------------------------
>
> Key: WFLY-1406
> URL: https://issues.jboss.org/browse/WFLY-1406
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Affects Versions: 8.0.0.Alpha2
> Reporter: Juergen Zimmermann
> Attachments: javap.log, server.log, server.log.zip, shop2.war, tar.log
>
>
> I tried the snapshot which contains Hibernate 4.3.0.Beta2. However, package-info.java files are causing problems. For instance, the package de.shop.artikelverwaltung.domain has a package-info.java which causes a NoClassDefFoundError:
> "IllegalName: de/shop/artikelverwaltung/domain.package-info". Please see the stacktrace below.
> Here is an example for package-info.java which was working with WildFly 8.0.0.Alpha1:
> @XmlAccessorType(FIELD)
> @Vetoed
> package de.shop.artikelverwaltung.domain;
> import static javax.xml.bind.annotation.XmlAccessType.FIELD;
> import javax.enterprise.inject.Vetoed;
> import javax.xml.bind.annotation.XmlAccessorType;
> The stacktrace:
> ...
> 09:29:53,880 WARN [org.jboss.modules] Failed to define class de/shop/artikelverwaltung/domain.package-info in Module "deployment.shop2.war:main" from Service Module Loader: java.lang.LinkageError: Failed to link de/shop/artikelverwaltung/domain/package-info (Module "deployment.shop2.war:main" from Service Module Loader)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:427) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:260) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:75) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.Module.loadModuleClass(Module.java:526) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:188) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final]
> at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader.findClass(ClassLoaderServiceImpl.java:218) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:423) [rt.jar:1.7.0_21]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356) [rt.jar:1.7.0_21]
> at org.hibernate.annotations.common.util.ReflectHelper.classForName(ReflectHelper.java:160) [hibernate-commons-annotations-4.0.2.Final.jar:4.0.2.Final]
> at org.hibernate.annotations.common.reflection.java.JavaReflectionManager.packageForName(JavaReflectionManager.java:121) [hibernate-commons-annotations-4.0.2.Final.jar:4.0.2.Final]
> at org.hibernate.cfg.AnnotationBinder.bindPackage(AnnotationBinder.java:262) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.cfg.Configuration.addPackage(Configuration.java:792) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.buildHibernateConfiguration(EntityManagerFactoryBuilderImpl.java:1174) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:839) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:836) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:368) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:835) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.HibernatePersistenceProvider.createContainerEntityManagerFactory(HibernatePersistenceProvider.java:142) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:213) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$800(PersistenceUnitServiceImpl.java:58) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:107) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final]
> Caused by: java.lang.NoClassDefFoundError: IllegalName: de/shop/artikelverwaltung/domain.package-info
> at java.lang.ClassLoader.preDefineClass(ClassLoader.java:646) [rt.jar:1.7.0_21]
> at java.lang.ClassLoader.defineClass(ClassLoader.java:785) [rt.jar:1.7.0_21]
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:344) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:422) [jboss-modules.jar:1.2.0.Final]
> ... 28 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (WFLY-1496) @Transactional doesn't work
by Juergen Zimmermann (JIRA)
[ https://issues.jboss.org/browse/WFLY-1496?page=com.atlassian.jira.plugin.... ]
Juergen Zimmermann updated WFLY-1496:
-------------------------------------
Attachment: testcase-WFLY-1496.zip
I attached a testcase to reproduce the error. The class CustomerResource has the method createCustomer which has the annotation @Transactional. If you use this annotation from javax.transaction, then the error happens. If you use instead my homegrown annotation and my homegrown @Transactional (see subpackage util) then everything works fine.
> @Transactional doesn't work
> ---------------------------
>
> Key: WFLY-1496
> URL: https://issues.jboss.org/browse/WFLY-1496
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 8.0.0.Alpha2
> Reporter: Juergen Zimmermann
> Assignee: jaikiran pai
> Attachments: testcase-WFLY-1496.zip
>
>
> I just tried the WildFly Alpha 2 snapshot containing Narayana 5.0.0.M3 and get the error message below. The classes causing the error are:
> @Path("/bestellungen")
> @Produces({ APPLICATION_JSON, APPLICATION_XML })
> //@RequestScoped is default for JAX-RS
> @Transactional
> public class BestellungResource {
> @Inject
> private BestellungService bs;
> ...
> }
> @Transactional(TxType.MANDATORY)
> public class BestellungServiceImpl implements Serializable {
> private static final long serialVersionUID = ...L;
>
> @PersistenceContext
> private transient EntityManager em;
> // method invoking JPA / Hibernate
> }
> The fragment of server.log:
> 15:11:43,254 DEBUG [org.hibernate.SQL]
> /* named HQL query Bestellung.findKundeById */ select
> distinct abstractku1_.id as id2_8_,
> abstractku1_.aktualisiert as aktualis3_8_,
> abstractku1_.bemerkungen as bemerkun4_8_,
> abstractku1_.email as email5_8_,
> abstractku1_.erzeugt as erzeugt6_8_,
> abstractku1_.file_fk as file18_8_,
> abstractku1_.kategorie as kategori7_8_,
> abstractku1_.nachname as nachname8_8_,
> abstractku1_.newsletter as newslett9_8_,
> abstractku1_.password as passwor10_8_,
> abstractku1_.rabatt as rabatt11_8_,
> abstractku1_.seit as seit12_8_,
> abstractku1_.umsatz as umsatz13_8_,
> abstractku1_.version as version14_8_,
> abstractku1_.vorname as vorname15_8_,
> abstractku1_.familienstand_fk as familie16_8_,
> abstractku1_.geschlecht_fk as geschle17_8_,
> abstractku1_.art as art1_8_
> from
> Bestellung bestellung0_
> inner join
> kunde abstractku1_
> on bestellung0_.kunde_fk=abstractku1_.id
> where
> bestellung0_.id=?
> 15:11:43,254 WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] SQL Error: 0, SQLState: null
> 15:11:43,254 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] UserTransaction is not available within the scope of a bean or method annotated with @Transactional and a Transactional.TxType other than NOT_SUPPORTED or NEVER
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (WFLY-1496) @Transactional doesn't work
by Juergen Zimmermann (JIRA)
[ https://issues.jboss.org/browse/WFLY-1496?page=com.atlassian.jira.plugin.... ]
Juergen Zimmermann updated WFLY-1496:
-------------------------------------
Summary: @Transactional doesn't work (was: ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] UserTransaction is not available)
> @Transactional doesn't work
> ---------------------------
>
> Key: WFLY-1496
> URL: https://issues.jboss.org/browse/WFLY-1496
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 8.0.0.Alpha2
> Reporter: Juergen Zimmermann
> Assignee: jaikiran pai
>
> I just tried the WildFly Alpha 2 snapshot containing Narayana 5.0.0.M3 and get the error message below. The classes causing the error are:
> @Path("/bestellungen")
> @Produces({ APPLICATION_JSON, APPLICATION_XML })
> //@RequestScoped is default for JAX-RS
> @Transactional
> public class BestellungResource {
> @Inject
> private BestellungService bs;
> ...
> }
> @Transactional(TxType.MANDATORY)
> public class BestellungServiceImpl implements Serializable {
> private static final long serialVersionUID = ...L;
>
> @PersistenceContext
> private transient EntityManager em;
> // method invoking JPA / Hibernate
> }
> The fragment of server.log:
> 15:11:43,254 DEBUG [org.hibernate.SQL]
> /* named HQL query Bestellung.findKundeById */ select
> distinct abstractku1_.id as id2_8_,
> abstractku1_.aktualisiert as aktualis3_8_,
> abstractku1_.bemerkungen as bemerkun4_8_,
> abstractku1_.email as email5_8_,
> abstractku1_.erzeugt as erzeugt6_8_,
> abstractku1_.file_fk as file18_8_,
> abstractku1_.kategorie as kategori7_8_,
> abstractku1_.nachname as nachname8_8_,
> abstractku1_.newsletter as newslett9_8_,
> abstractku1_.password as passwor10_8_,
> abstractku1_.rabatt as rabatt11_8_,
> abstractku1_.seit as seit12_8_,
> abstractku1_.umsatz as umsatz13_8_,
> abstractku1_.version as version14_8_,
> abstractku1_.vorname as vorname15_8_,
> abstractku1_.familienstand_fk as familie16_8_,
> abstractku1_.geschlecht_fk as geschle17_8_,
> abstractku1_.art as art1_8_
> from
> Bestellung bestellung0_
> inner join
> kunde abstractku1_
> on bestellung0_.kunde_fk=abstractku1_.id
> where
> bestellung0_.id=?
> 15:11:43,254 WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] SQL Error: 0, SQLState: null
> 15:11:43,254 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] UserTransaction is not available within the scope of a bean or method annotated with @Transactional and a Transactional.TxType other than NOT_SUPPORTED or NEVER
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (WFLY-190) infinispan.DistributedCacheManagerTest unit tests fail with openjdk7
by Carlo de Wolf (JIRA)
[ https://issues.jboss.org/browse/WFLY-190?page=com.atlassian.jira.plugin.s... ]
Carlo de Wolf reopened WFLY-190:
--------------------------------
> infinispan.DistributedCacheManagerTest unit tests fail with openjdk7
> --------------------------------------------------------------------
>
> Key: WFLY-190
> URL: https://issues.jboss.org/browse/WFLY-190
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Test Suite
> Environment: affected master
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 8.0.0.Alpha1
>
> Attachments: org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest.txt, TEST-org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest.xml
>
>
> Noticed by alexey
> [rhusar@rhusar jboss-as]$ java -version
> java version "1.7.0_06-icedtea"
> OpenJDK Runtime Environment (fedora-2.3.1.fc17.2-x86_64)
> OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode)
> {noformat}
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ jboss-as-clustering-web-infinispan ---
> [debug] execute contextualize
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory /home/rhusar/git/jboss-as/clustering/web-infinispan/src/test/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ jboss-as-clustering-web-infinispan ---
> [INFO] Compiling 6 source files to /home/rhusar/git/jboss-as/clustering/web-infinispan/target/test-classes
> [INFO]
> [INFO] --- maven-surefire-plugin:2.11:test (default-test) @ jboss-as-clustering-web-infinispan ---
> [INFO] Surefire report directory: /home/rhusar/git/jboss-as/clustering/web-infinispan/target/surefire-reports
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.as.clustering.web.infinispan.FineSessionAttributeStorageTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.334 sec
> Running org.jboss.as.clustering.web.infinispan.CoarseSessionAttributeStorageTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec
> Running org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest
> Tests run: 22, Failures: 2, Errors: 6, Skipped: 0, Time elapsed: 0.42 sec <<< FAILURE!
> Running org.jboss.as.clustering.web.infinispan.SimpleExternalizerTestCase
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
> Running org.jboss.as.clustering.web.infinispan.SessionAttributeStorageFactoryTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
> Running org.jboss.as.clustering.web.infinispan.SessionMapEntryTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
> Results :
> Failed tests: getSessionDataNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): expected same:<Mock for IncomingDistributableSessionData, hashCode: 1688182366> was not:<null>
> getMissingSessionDataNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): expected same:<Mock for IncomingDistributableSessionData, hashCode: 981356300> was not:<null>
> Tests in error:
> removeSession(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
> removeSessionLocal(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
> removeSessionLocalNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
> evictSession(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
> evictSessionNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
> getSessionIds(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest)
> Tests run: 33, Failures: 2, Errors: 6, Skipped: 0
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (WFLY-190) infinispan.DistributedCacheManagerTest unit tests fail with openjdk7
by Carlo de Wolf (JIRA)
[ https://issues.jboss.org/browse/WFLY-190?page=com.atlassian.jira.plugin.s... ]
Carlo de Wolf resolved WFLY-190.
--------------------------------
Resolution: Cannot Reproduce Bug
Truly fixed in WFLY-512
> infinispan.DistributedCacheManagerTest unit tests fail with openjdk7
> --------------------------------------------------------------------
>
> Key: WFLY-190
> URL: https://issues.jboss.org/browse/WFLY-190
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Test Suite
> Environment: affected master
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 8.0.0.Alpha1
>
> Attachments: org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest.txt, TEST-org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest.xml
>
>
> Noticed by alexey
> [rhusar@rhusar jboss-as]$ java -version
> java version "1.7.0_06-icedtea"
> OpenJDK Runtime Environment (fedora-2.3.1.fc17.2-x86_64)
> OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode)
> {noformat}
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ jboss-as-clustering-web-infinispan ---
> [debug] execute contextualize
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory /home/rhusar/git/jboss-as/clustering/web-infinispan/src/test/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ jboss-as-clustering-web-infinispan ---
> [INFO] Compiling 6 source files to /home/rhusar/git/jboss-as/clustering/web-infinispan/target/test-classes
> [INFO]
> [INFO] --- maven-surefire-plugin:2.11:test (default-test) @ jboss-as-clustering-web-infinispan ---
> [INFO] Surefire report directory: /home/rhusar/git/jboss-as/clustering/web-infinispan/target/surefire-reports
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.as.clustering.web.infinispan.FineSessionAttributeStorageTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.334 sec
> Running org.jboss.as.clustering.web.infinispan.CoarseSessionAttributeStorageTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec
> Running org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest
> Tests run: 22, Failures: 2, Errors: 6, Skipped: 0, Time elapsed: 0.42 sec <<< FAILURE!
> Running org.jboss.as.clustering.web.infinispan.SimpleExternalizerTestCase
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
> Running org.jboss.as.clustering.web.infinispan.SessionAttributeStorageFactoryTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
> Running org.jboss.as.clustering.web.infinispan.SessionMapEntryTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
> Results :
> Failed tests: getSessionDataNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): expected same:<Mock for IncomingDistributableSessionData, hashCode: 1688182366> was not:<null>
> getMissingSessionDataNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): expected same:<Mock for IncomingDistributableSessionData, hashCode: 981356300> was not:<null>
> Tests in error:
> removeSession(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
> removeSessionLocal(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
> removeSessionLocalNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
> evictSession(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
> evictSessionNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..)
> getSessionIds(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest)
> Tests run: 33, Failures: 2, Errors: 6, Skipped: 0
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (WFLY-1513) remove operation on JMS queue/topic doesn't remove the destination but just unbinds from JNDI
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-1513?page=com.atlassian.jira.plugin.... ]
jaikiran pai updated WFLY-1513:
-------------------------------
Fix Version/s: (was: 8.0.0.Alpha2)
Affects Version/s: 8.0.0.Alpha2
> remove operation on JMS queue/topic doesn't remove the destination but just unbinds from JNDI
> ---------------------------------------------------------------------------------------------
>
> Key: WFLY-1513
> URL: https://issues.jboss.org/browse/WFLY-1513
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, JMS
> Affects Versions: 8.0.0.Alpha1, 8.0.0.Alpha2
> Reporter: jaikiran pai
> Assignee: Jeff Mesnil
>
> The remove (management) operation on a JMS queue merely unbinds the queue from JNDI instead of destroying the queue. It appears that the change was done as part of https://issues.jboss.org/browse/AS7-1899 (the PR is here https://github.com/wildfly/wildfly/pull/398). The change done in that PR to address the original issue reported in that other JIRA doesn't look right.
> So the original issue reported in that thread is that a server has a queue with messages and the server is stopped. Upon restart the messages have disappeared because upon stop, the JMSQueueService's stop() method used to destroy the queue. The real fix would have been to differentiate the "remove()" operation from a mere service stop. The explicit remove (handler) would then be responsible for destroying the queue (which even means a JNDI unbind) and not that service's stop method.
> All of this even applies to the JMS topic which has a similar problem.
> On a related note, the add() operation too seems suspicious because it ends up calling a createXXX on the JMSServer API which says:
> {code}
> /**
> * Creates a JMS Queue.
> *
> * @param queueName
> * The name of the queue to create
> * @param selectorString
> * @param durable
> * @return true if the queue is created or if it existed and was added to
> * JNDI
> * @throws Exception
> * if problems were encountered creating the queue.
> */
> boolean createQueue(boolean storeConfig, String queueName, String selectorString, boolean durable, String ...bindings) throws Exception;
> {code}
> Notice the "if the queue is created or if it existed and was added to JNDI" part. So it appears that the management "add" operation can end up behaving like an update (write-attribute) kind of operation in some cases. I'm not sure if that's good thing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (WFLY-1513) remove operation on JMS queue/topic doesn't remove the destination but just unbinds from JNDI
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-1513?page=com.atlassian.jira.plugin.... ]
jaikiran pai reopened WFLY-1513:
--------------------------------
> remove operation on JMS queue/topic doesn't remove the destination but just unbinds from JNDI
> ---------------------------------------------------------------------------------------------
>
> Key: WFLY-1513
> URL: https://issues.jboss.org/browse/WFLY-1513
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, JMS
> Affects Versions: 8.0.0.Alpha1
> Reporter: jaikiran pai
> Assignee: Jeff Mesnil
> Fix For: 8.0.0.Alpha2
>
>
> The remove (management) operation on a JMS queue merely unbinds the queue from JNDI instead of destroying the queue. It appears that the change was done as part of https://issues.jboss.org/browse/AS7-1899 (the PR is here https://github.com/wildfly/wildfly/pull/398). The change done in that PR to address the original issue reported in that other JIRA doesn't look right.
> So the original issue reported in that thread is that a server has a queue with messages and the server is stopped. Upon restart the messages have disappeared because upon stop, the JMSQueueService's stop() method used to destroy the queue. The real fix would have been to differentiate the "remove()" operation from a mere service stop. The explicit remove (handler) would then be responsible for destroying the queue (which even means a JNDI unbind) and not that service's stop method.
> All of this even applies to the JMS topic which has a similar problem.
> On a related note, the add() operation too seems suspicious because it ends up calling a createXXX on the JMSServer API which says:
> {code}
> /**
> * Creates a JMS Queue.
> *
> * @param queueName
> * The name of the queue to create
> * @param selectorString
> * @param durable
> * @return true if the queue is created or if it existed and was added to
> * JNDI
> * @throws Exception
> * if problems were encountered creating the queue.
> */
> boolean createQueue(boolean storeConfig, String queueName, String selectorString, boolean durable, String ...bindings) throws Exception;
> {code}
> Notice the "if the queue is created or if it existed and was added to JNDI" part. So it appears that the management "add" operation can end up behaving like an update (write-attribute) kind of operation in some cases. I'm not sure if that's good thing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (WFLY-1513) remove operation on JMS queue/topic doesn't remove the destination but just unbinds from JNDI
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-1513?page=com.atlassian.jira.plugin.... ]
jaikiran pai commented on WFLY-1513:
------------------------------------
The linked PR wasn't merged. It looks like this JIRA was accidentally closed. Re-opening it.
> remove operation on JMS queue/topic doesn't remove the destination but just unbinds from JNDI
> ---------------------------------------------------------------------------------------------
>
> Key: WFLY-1513
> URL: https://issues.jboss.org/browse/WFLY-1513
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, JMS
> Affects Versions: 8.0.0.Alpha1
> Reporter: jaikiran pai
> Assignee: Jeff Mesnil
> Fix For: 8.0.0.Alpha2
>
>
> The remove (management) operation on a JMS queue merely unbinds the queue from JNDI instead of destroying the queue. It appears that the change was done as part of https://issues.jboss.org/browse/AS7-1899 (the PR is here https://github.com/wildfly/wildfly/pull/398). The change done in that PR to address the original issue reported in that other JIRA doesn't look right.
> So the original issue reported in that thread is that a server has a queue with messages and the server is stopped. Upon restart the messages have disappeared because upon stop, the JMSQueueService's stop() method used to destroy the queue. The real fix would have been to differentiate the "remove()" operation from a mere service stop. The explicit remove (handler) would then be responsible for destroying the queue (which even means a JNDI unbind) and not that service's stop method.
> All of this even applies to the JMS topic which has a similar problem.
> On a related note, the add() operation too seems suspicious because it ends up calling a createXXX on the JMSServer API which says:
> {code}
> /**
> * Creates a JMS Queue.
> *
> * @param queueName
> * The name of the queue to create
> * @param selectorString
> * @param durable
> * @return true if the queue is created or if it existed and was added to
> * JNDI
> * @throws Exception
> * if problems were encountered creating the queue.
> */
> boolean createQueue(boolean storeConfig, String queueName, String selectorString, boolean durable, String ...bindings) throws Exception;
> {code}
> Notice the "if the queue is created or if it existed and was added to JNDI" part. So it appears that the management "add" operation can end up behaving like an update (write-attribute) kind of operation in some cases. I'm not sure if that's good thing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months