[JBoss JIRA] (WFLY-2011) jboss-ejb3.xml deployment descriptor is not parsed correct for the clustering element
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-2011?page=com.atlassian.jira.plugin.... ]
Stuart Douglas resolved WFLY-2011.
----------------------------------
Fix Version/s: 8.0.0.CR1
Resolution: Done
> jboss-ejb3.xml deployment descriptor is not parsed correct for the clustering element
> -------------------------------------------------------------------------------------
>
> Key: WFLY-2011
> URL: https://issues.jboss.org/browse/WFLY-2011
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB
> Affects Versions: 8.0.0.Beta1
> Reporter: Wolf-Dieter Fink
> Assignee: Stuart Douglas
> Labels: ejb-jar.xml
> Fix For: 8.0.0.CR1
>
>
> If beans of an application are marked as clustered by using the jboss-ejb3.xml DD the behaviour is not consistent.
> From the XSD the <ejb-name> element can not be added multiple times.
> And the following configuration will be not valid:
> <assembly-descriptor>
> <c:clustering>
> <ejb-name>Bean1</ejb-name>
> <ejb-name>Bean2</ejb-name>
> <c:clustered>true</c:clustered>
> </c:clustering>
> </assembly-descriptor>
> The parser should throw an Exception and the application should not be deployed.
--
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
10 years, 6 months
[JBoss JIRA] (WFLY-2387) CDI injection in entity listeners failing
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-2387?page=com.atlassian.jira.plugin.... ]
Stuart Douglas resolved WFLY-2387.
----------------------------------
Fix Version/s: 8.0.0.CR1
Resolution: Done
> CDI injection in entity listeners failing
> -----------------------------------------
>
> Key: WFLY-2387
> URL: https://issues.jboss.org/browse/WFLY-2387
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: CDI / Weld, Class Loading, JPA / Hibernate
> Affects Versions: 8.0.0.Beta1
> Reporter: Emond Papegaaij
> Assignee: Stuart Douglas
> Fix For: 8.0.0.CR1
>
>
> When trying to use CDI injection in JPA entity listeners, deployment fails with the following exception:
> {code}
> 16:16:37,448 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 15) MSC000001: Failed to start service jboss.persistenceunit."inject-ear.ear#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."inject-ear.ear#primary": java.lang.IllegalStateException: JBAS016071: Singleton not set for org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader@4eeb95dc. This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment.
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:169)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:117)
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_25]
> at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:463) [wildfly-security-manager-1.0.0.Beta3.jar:1.0.0.Beta3]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:178)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
> Caused by: java.lang.IllegalStateException: JBAS016071: Singleton not set for org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader@4eeb95dc. This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment.
> at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:75)
> at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:128)
> at org.jboss.weld.Container.instance(Container.java:65)
> at org.jboss.weld.manager.BeanManagerImpl.getBeans(BeanManagerImpl.java:563)
> at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:90)
> at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358)
> at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369)
> at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72)
> at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60)
> at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66)
> at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48)
> at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64)
> at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90)
> at org.hibernate.jpa.event.internal.jpa.BeanManagerListenerFactory$BeanMetaData.<init>(BeanManagerListenerFactory.java:82)
> at org.hibernate.jpa.event.internal.jpa.BeanManagerListenerFactory$BeanMetaData.<init>(BeanManagerListenerFactory.java:71)
> at org.hibernate.jpa.event.internal.jpa.BeanManagerListenerFactory.buildListener(BeanManagerListenerFactory.java:57)
> at org.hibernate.jpa.event.internal.jpa.LegacyCallbackProcessor.resolveCallbacks(LegacyCallbackProcessor.java:168)
> at org.hibernate.jpa.event.internal.jpa.LegacyCallbackProcessor.processCallbacksForEntity(LegacyCallbackProcessor.java:71)
> at org.hibernate.jpa.event.spi.JpaIntegrator.integrate(JpaIntegrator.java:150)
> at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:310)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1837)
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:854)
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:847)
> at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:396)
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:846)
> at org.jboss.as.jpa.hibernate4.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:151)
> ... 8 more
> {code}
> I've created a small showcase of the problem: https://github.com/papegaaij/listener-injection
--
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
10 years, 6 months
[JBoss JIRA] (LOGMGR-73) Configured logger filters don't work; NPE is hidden
by James Livingston (JIRA)
[ https://issues.jboss.org/browse/LOGMGR-73?page=com.atlassian.jira.plugin.... ]
James Livingston updated LOGMGR-73:
-----------------------------------
Forum Reference: https://community.jboss.org/thread/229586
> Configured logger filters don't work; NPE is hidden
> ---------------------------------------------------
>
> Key: LOGMGR-73
> URL: https://issues.jboss.org/browse/LOGMGR-73
> Project: JBoss Log Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.4.1.Final
> Reporter: Stuart Douglas
> Assignee: David Lloyd
> Fix For: 1.3.3.Final, 1.4.2.Final, 1.5.0.Beta1, 2.0.0.Beta1
>
>
> In org.jboss.logmanager.config.LoggerConfigurationImpl line 83:
> configuration.getHandlerRefs().get(getName()).setFilter((Filter) param.getObject());
> throws a NPE, as configuration.getHandlerRefs() does not contain the relevant entry. The whole thing looks very suspicous because getHandlerRefs() has two entries under 'FILE' and 'CONSOLE' while getName() returns log categories such as 'com.arjuna', so it seems very unlikely that this will ever work.
> The only reason that this appears to work ok is because in org.jboss.logmanager.config.LogContextConfigurationImpl#doApplyPostCreate any exceptions or errors are silently ignored:
> {code}
> try {
> action.applyPostCreate((T) arg);
> } catch (Throwable ignored) {}
> {code}
--
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
10 years, 6 months
[JBoss JIRA] (WFLY-943) XML schema; use of elementFormDefault='unqualified'; cannot validate some documents
by Joshua Wilson (JIRA)
[ https://issues.jboss.org/browse/WFLY-943?page=com.atlassian.jira.plugin.s... ]
Joshua Wilson commented on WFLY-943:
------------------------------------
In my last comment I wrote about how changing the version makes the error go away in Eclipse. While this is true it does not actually allow you to deploy the application to JBoss (where the schema lives).
After looking deeper into this I believe that you are right and that the elementFormDefault="unqualified" needs to be changed to elementFormDefault="qualified".
> XML schema; use of elementFormDefault='unqualified'; cannot validate some documents
> -----------------------------------------------------------------------------------
>
> Key: WFLY-943
> URL: https://issues.jboss.org/browse/WFLY-943
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Documentation
> Affects Versions: 8.0.0.Alpha3
> Reporter: Elias Ross
> Fix For: 8.0.0.CR1
>
> Attachments: jboss-deployment-structure.xml
>
>
> When attempting to write a (seemingly) valid jboss-deployment-structure.xml using the schema in ./docs, my document fails to validate.
> This is because of the settings used in the XSD. Have these XSDs been used to validate actual documents? By setting unqualified to 'qualified' then the documents will probably validate.
> $ git grep elementFormDefault..unqualified
> jboss-deployment-dependencies-1_0.xsd: elementFormDefault="unqualified"
> jboss-deployment-structure-1_0.xsd: elementFormDefault="unqualified"
> jboss-deployment-structure-1_1.xsd: elementFormDefault="unqualified"
> jboss-deployment-structure-1_2.xsd: elementFormDefault="unqualified"
> jboss-ejb-client_1_0.xsd: elementFormDefault="unqualified"
> jboss-ejb-client_1_1.xsd: elementFormDefault="unqualified"
> jboss-ejb-client_1_2.xsd: elementFormDefault="unqualified"
> jboss-jpa_1_0.xsd: elementFormDefault="unqualified"
--
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
10 years, 6 months
[JBoss JIRA] (JBMETA-367) CLONE - XML schema; use of elementFormDefault='unqualified'; cannot validate some documents
by Joshua Wilson (JIRA)
[ https://issues.jboss.org/browse/JBMETA-367?page=com.atlassian.jira.plugin... ]
Joshua Wilson commented on JBMETA-367:
--------------------------------------
In my last comment I wrote about how changing the version makes the error go away in Eclipse. While this is true it does not actually allow you to deploy the application to JBoss (where the schema lives).
After looking deeper into this I believe that you are right and that the elementFormDefault="unqualified" needs to be changed to elementFormDefault="qualified".
> CLONE - XML schema; use of elementFormDefault='unqualified'; cannot validate some documents
> -------------------------------------------------------------------------------------------
>
> Key: JBMETA-367
> URL: https://issues.jboss.org/browse/JBMETA-367
> Project: JBoss Metadata
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Elias Ross
>
> When attempting to write a (seemingly) valid jboss-deployment-structure.xml using the schema in ./docs, my document fails to validate.
> This is because of the settings used in the XSD. Have these XSDs been used to validate actual documents? By setting unqualified to 'qualified' then the documents will probably validate.
> $ git grep elementFormDefault..unqualified
> jboss-deployment-dependencies-1_0.xsd: elementFormDefault="unqualified"
> jboss-deployment-structure-1_0.xsd: elementFormDefault="unqualified"
> jboss-deployment-structure-1_1.xsd: elementFormDefault="unqualified"
> jboss-deployment-structure-1_2.xsd: elementFormDefault="unqualified"
> jboss-ejb-client_1_0.xsd: elementFormDefault="unqualified"
> jboss-ejb-client_1_1.xsd: elementFormDefault="unqualified"
> jboss-ejb-client_1_2.xsd: elementFormDefault="unqualified"
> jboss-jpa_1_0.xsd: elementFormDefault="unqualified"
--
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
10 years, 6 months
[JBoss JIRA] (WFLY-2428) MDBs should use the full identifier of the resource adapter
by Jesper Pedersen (JIRA)
Jesper Pedersen created WFLY-2428:
-------------------------------------
Summary: MDBs should use the full identifier of the resource adapter
Key: WFLY-2428
URL: https://issues.jboss.org/browse/WFLY-2428
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB
Affects Versions: 8.0.0.CR1
Reporter: Jesper Pedersen
Assignee: Jesper Pedersen
Fix For: 8.0.0.CR1
The .rar suffix shouldn't be stripped anymore, as the resource adapters are registered under their full name.
--
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
10 years, 6 months
[JBoss JIRA] (JBMETA-367) CLONE - XML schema; use of elementFormDefault='unqualified'; cannot validate some documents
by Joshua Wilson (JIRA)
[ https://issues.jboss.org/browse/JBMETA-367?page=com.atlassian.jira.plugin... ]
Joshua Wilson commented on JBMETA-367:
--------------------------------------
I just found that if you use `<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:2.0">` it works.
> CLONE - XML schema; use of elementFormDefault='unqualified'; cannot validate some documents
> -------------------------------------------------------------------------------------------
>
> Key: JBMETA-367
> URL: https://issues.jboss.org/browse/JBMETA-367
> Project: JBoss Metadata
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Elias Ross
>
> When attempting to write a (seemingly) valid jboss-deployment-structure.xml using the schema in ./docs, my document fails to validate.
> This is because of the settings used in the XSD. Have these XSDs been used to validate actual documents? By setting unqualified to 'qualified' then the documents will probably validate.
> $ git grep elementFormDefault..unqualified
> jboss-deployment-dependencies-1_0.xsd: elementFormDefault="unqualified"
> jboss-deployment-structure-1_0.xsd: elementFormDefault="unqualified"
> jboss-deployment-structure-1_1.xsd: elementFormDefault="unqualified"
> jboss-deployment-structure-1_2.xsd: elementFormDefault="unqualified"
> jboss-ejb-client_1_0.xsd: elementFormDefault="unqualified"
> jboss-ejb-client_1_1.xsd: elementFormDefault="unqualified"
> jboss-ejb-client_1_2.xsd: elementFormDefault="unqualified"
> jboss-jpa_1_0.xsd: elementFormDefault="unqualified"
--
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
10 years, 6 months
[JBoss JIRA] (WFLY-943) XML schema; use of elementFormDefault='unqualified'; cannot validate some documents
by Joshua Wilson (JIRA)
[ https://issues.jboss.org/browse/WFLY-943?page=com.atlassian.jira.plugin.s... ]
Joshua Wilson commented on WFLY-943:
------------------------------------
I guess someone has worked it because I just found that if you use `<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:2.0">` it works.
Thanks team! :)
> XML schema; use of elementFormDefault='unqualified'; cannot validate some documents
> -----------------------------------------------------------------------------------
>
> Key: WFLY-943
> URL: https://issues.jboss.org/browse/WFLY-943
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Documentation
> Affects Versions: 8.0.0.Alpha3
> Reporter: Elias Ross
> Fix For: 8.0.0.CR1
>
> Attachments: jboss-deployment-structure.xml
>
>
> When attempting to write a (seemingly) valid jboss-deployment-structure.xml using the schema in ./docs, my document fails to validate.
> This is because of the settings used in the XSD. Have these XSDs been used to validate actual documents? By setting unqualified to 'qualified' then the documents will probably validate.
> $ git grep elementFormDefault..unqualified
> jboss-deployment-dependencies-1_0.xsd: elementFormDefault="unqualified"
> jboss-deployment-structure-1_0.xsd: elementFormDefault="unqualified"
> jboss-deployment-structure-1_1.xsd: elementFormDefault="unqualified"
> jboss-deployment-structure-1_2.xsd: elementFormDefault="unqualified"
> jboss-ejb-client_1_0.xsd: elementFormDefault="unqualified"
> jboss-ejb-client_1_1.xsd: elementFormDefault="unqualified"
> jboss-ejb-client_1_2.xsd: elementFormDefault="unqualified"
> jboss-jpa_1_0.xsd: elementFormDefault="unqualified"
--
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
10 years, 6 months
[JBoss JIRA] (WFLY-943) XML schema; use of elementFormDefault='unqualified'; cannot validate some documents
by Joshua Wilson (JIRA)
[ https://issues.jboss.org/browse/WFLY-943?page=com.atlassian.jira.plugin.s... ]
Joshua Wilson commented on WFLY-943:
------------------------------------
In the version that I use it does NOT have the "p" and I still get the errors. For examples please refer to any of the Spring related [quickstarts|https://github.com/jboss-developer/jboss-wfk-quickstarts/tree...] in the JBoss Web Framework Kit quickstarts.
To be clear you need to Build with Eclipse to see the errors.
Does anyone know if this is being worked?
> XML schema; use of elementFormDefault='unqualified'; cannot validate some documents
> -----------------------------------------------------------------------------------
>
> Key: WFLY-943
> URL: https://issues.jboss.org/browse/WFLY-943
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Documentation
> Affects Versions: 8.0.0.Alpha3
> Reporter: Elias Ross
> Fix For: 8.0.0.CR1
>
> Attachments: jboss-deployment-structure.xml
>
>
> When attempting to write a (seemingly) valid jboss-deployment-structure.xml using the schema in ./docs, my document fails to validate.
> This is because of the settings used in the XSD. Have these XSDs been used to validate actual documents? By setting unqualified to 'qualified' then the documents will probably validate.
> $ git grep elementFormDefault..unqualified
> jboss-deployment-dependencies-1_0.xsd: elementFormDefault="unqualified"
> jboss-deployment-structure-1_0.xsd: elementFormDefault="unqualified"
> jboss-deployment-structure-1_1.xsd: elementFormDefault="unqualified"
> jboss-deployment-structure-1_2.xsd: elementFormDefault="unqualified"
> jboss-ejb-client_1_0.xsd: elementFormDefault="unqualified"
> jboss-ejb-client_1_1.xsd: elementFormDefault="unqualified"
> jboss-ejb-client_1_2.xsd: elementFormDefault="unqualified"
> jboss-jpa_1_0.xsd: elementFormDefault="unqualified"
--
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
10 years, 6 months
[JBoss JIRA] (JGRP-1716) Regression between 3.2.x and 3.3.x/3.4.x in Infinispan read simulation
by Divya Mehra (JIRA)
[ https://issues.jboss.org/browse/JGRP-1716?page=com.atlassian.jira.plugin.... ]
Divya Mehra updated JGRP-1716:
------------------------------
Labels: dm (was: jdg620_dm)
> Regression between 3.2.x and 3.3.x/3.4.x in Infinispan read simulation
> ----------------------------------------------------------------------
>
> Key: JGRP-1716
> URL: https://issues.jboss.org/browse/JGRP-1716
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.3, 3.4
> Reporter: Dan Berindei
> Assignee: Bela Ban
> Labels: dm
> Fix For: 3.4.1, 3.5
>
> Attachments: benchmark-jgroups.xml, jgroups-udp.pdf, jgroups-udp.xml
>
>
> Comparing JGroups 3.2/3.3/3.4 performance with Radargun, the throughput of reads in scenario simulating Infinispan went down by ~10%. See the attached chart.
> * getall: the get request is sent to single node (randomly picked owner)
> * getfirst: the get requests are sent to 2 nodes with ResponseMode.GET_FIRST - the second response is discarded.
> .h5 Suspects:
> Erik Salter profiled his application and noticed that the message parsing in the UDP receiver thread seemed to slow things down. He wrote a patch that brought his throughput back to 3.2 levels: https://github.com/an1310/JGroups/compare/t_perfhack
> The UDP receiver thread may not tell the whole story, however: in the Radargun tests, performance with his patch was even lower.
--
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
10 years, 6 months