[weld-issues] [JBoss JIRA] (WELD-1564) Memory leak caused by retained instances of BeanManagerImpl / WeldInterceptorClassMetadata
Jozef Hartinger updated WELD-1564 Memory leak caused by retained instances of BeanManagerImpl / WeldInterceptorClassMetadata Change By: Jozef Hartinger (18/Dec/13 3:59 AM) Status: PullRequestSent Resolved Fix Version/s: 2.2.0.Alpha1 Resolution: Done 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1566) Null Pointer during conversation context activation
Jozef Hartinger commented on WELD-1566 Null Pointer during conversation context activation Are you able to consistently reproduce this? 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1510) Weld does not work together with WebSocket API 1.0 and Tomcat 8
Jozef Hartinger resolved WELD-1510 as Rejected Weld does not work together with WebSocket API 1.0 and Tomcat 8 Should be fixed already. Feel free to reopen if it is not. Change By: Jozef Hartinger (18/Dec/13 4:06 AM) Status: Open Resolved Resolution: Rejected 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1566) Null Pointer during conversation context activation
Fabian Lange commented on WELD-1566 Null Pointer during conversation context activation Unfortunately I was not able to manually reproduce it. It however affects about 10% of our automated test suite. Where it appears is random, so my feeling is that this is a concurrency / race condition issue. 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1566) Null Pointer during conversation context activation
Fabian Lange edited a comment on WELD-1566 Null Pointer during conversation context activation Unfortunately I was not able to manually reproduce it. It however affects about 10% of our automated test suite. Where it appears is random, so my feeling is that this is a concurrency / race condition issue. The code causing this at least is concurrency related. lock(conversation); setRequestAttribute(getRequest(), CURRENT_CONVERSATION_ATTRIBUTE_NAME, conversation); here the return value of lock() is not checked, which may have to do with the issue. 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1566) Null Pointer during conversation context activation
Jozef Hartinger commented on WELD-1566 Null Pointer during conversation context activation That should not be a problem since at that point lock() is called for a new-ly created conversation whose lock is not shared with any other thread and therefore the lock operation should not timeout. Looking at the Tomcat source code I think that this may not be a Weld issue at all: http://grepcode.com/file/repo1.maven.org/maven2/org.apache.tomcat/tomcat-catalina/7.0.42/org/apache/catalina/connector/Request.java#1563 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-376) Interceptors spec - improve tests for setcion Section 2.5 - Business Method Interceptors
Matus Abaffy resolved CDITCK-376 as Done Interceptors spec - improve tests for setcion Section 2.5 - Business Method Interceptors Change By: Matus Abaffy (18/Dec/13 6:41 AM) Status: Open Resolved Resolution: Done 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-377) Interceptors spec - duplicate existing interceptor tests to test session beans too
Matus Abaffy resolved CDITCK-377 as Done Interceptors spec - duplicate existing interceptor tests to test session beans too Change By: Matus Abaffy (18/Dec/13 6:42 AM) Status: Open Resolved Resolution: Done 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1571) Proxy creation fails when a superclass does not have a no-arg constructor
Emond Papegaaij created WELD-1571 Proxy creation fails when a superclass does not have a no-arg constructor Issue Type: Bug Affects Versions: 2.1.1.Final Assignee: Jozef Hartinger Components: Proxies Created: 19/Dec/13 2:09 AM Description: When injecting an @ApplicationScoped bean, which extends a class that does not have a no-arg constructor, the following NPE occurs: Caused by: java.lang.NullPointerException at org.jboss.weld.bean.proxy.ClientProxyProvider.getClientProxy(ClientProxyProvider.java:214) [weld-core-impl-2.1.1.Final.jar:2013-12-03 09:59] at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:727) [weld-core-impl-2.1.1.Final.jar:2013-12-03 09:59] at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:789) [weld-core-impl-2.1.1.Final.jar:2013-12-03 09:59] at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:92) [weld-core-impl-2.1.1.Final.jar:2013-12-03 09:59] at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) [weld-core-impl-2.1.1.Final.jar:2013-12-03 09:59] at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) [weld-core-impl-2.1.1.Final.jar:2013-12-03 09:59] at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) [weld-core-impl-2.1.1.Final.jar:2013-12-03 09:59] at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) [weld-core-impl-2.1.1.Final.jar:2013-12-03 09:59] at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) [weld-core-impl-2.1.1.Final.jar:2013-12-03 09:59] at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) [weld-core-impl-2.1.1.Final.jar:2013-12-03 09:59] at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) [weld-core-impl-2.1.1.Final.jar:2013-12-03 09:59] at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) [weld-core-impl-2.1.1.Final.jar:2013-12-03 09:59] at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:150) [weld-core-impl-2.1.1.Final.jar:2013-12-03 09:59] at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:94) [weld-core-impl-2.1.1.Final.jar:2013-12-03 09:59] at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:98) [weld-core-impl-2.1.1.Final.jar:2013-12-03 09:59] at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:78) [weld-core-impl-2.1.1.Final.jar:2013-12-03 09:59] at nl.topicus.digdag.rest.integration.RemoteClientBuilder$Proxy$_$$_WeldClientProxy.createTopicusClient(Unknown Source) [classes:] at nl.topicus.digdag.rest.RemoteAuthenticationRESTService.getRemoteAuthentication(RemoteAuthenticationRESTService.java:223) [classes:] Debugging the code in ClientProxyProvider.getClientProxy reveals that this caused by the following problem (in Proxies.getUnproxyableTypesExceptionInt): org.jboss.weld.exceptions.UnproxyableResolutionException: WELD-001435: Normal scoped bean class org.openid4java.consumer.AbstractNonceVerifier is not proxyable because it has no no-args constructor - Managed Bean [class nl.topicus.digdag.rest.integration.CachedNonceVerifier] with qualifiers [@Any @Default]. CachedNonceVerifier extends AbstractNonceVerifier. CachedNonceVerifier does have a no-arg constructor, AbstractNonceVerifier does not, but I do not see why it would need it as CachedNonceVerifier is the type that is proxied. Environment: Wildfly master build (2013-12-19) Project: Weld Priority: Major Reporter: Emond Papegaaij
