January 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Updated: (WELD-59) Clustered WebBeans, no support for sessionscoped (and higher) replication

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-59?page=com.atlassian.jira.plugin... ] Pete Muir updated WELD-59: -------------------------- Fix Version/s: 1.0.1.CR2 (was: 1.0.2.CR1) > Clustered WebBeans, no support for sessionscoped (and higher) replication > ------------------------------------------------------------------------- > > Key: WELD-59 > URL: https://jira.jboss.org/jira/browse/WELD-59 > Project: Weld > Issue Type: Bug > Components: Scopes & Contexts > Affects Versions: 1.0.0.PREVIEW1 > Environment: JBoss AS 5.1 + JDK 6 > Reporter: John Ament > Fix For: 1.0.1.CR2 > > Attachments: ClusteredWebBeansTestApp.zip, ClusteredWebBeansTestApp.zip > > > From what I can tell, this is what happens. > Assume you have a 2 node environment w/ apache httpd + mod_jk in front of the jboss servers, used to limit servers exposed + a loadbalancer (F5 ASM) in front of those. The apache servers are only configured to talk to one jboss server each (httpd + jboss are on same box, they only talk to the local client). the f5 serving the initial request is configured for pure round robin (no cookie persistence) and as a result request 1 could go to server 1 and then request 2 goes to server 2. > Now assume that the two jboss servers are clustered together, the EJBs are clustered and have a cache policy (based on the JBoss annotations). They only have local interfaces. In addition, there are some classes that are only POJOs; but they sit in the ejb module. Based on what's happening these objects should be replicated as part of the HTTP session state. > A few problems seem to occur when the request goes to the second server after the first request goes to the first server. > 1. References to the resources required by the EJBs are not injected in the second server. This includes members decorated @Resource or @PersistenceContext > 2. References to EJBs required at the view level are not restored. > In addition, concurrent modification exceptions seem to be more likely when deployed like this, resulting in having to downgrade EJBs to POJOs in order to remain stateful. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (WELD-80) Passivation of stateful session beans results in a loss of reference to injected object

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-80?page=com.atlassian.jira.plugin... ] Pete Muir updated WELD-80: -------------------------- Fix Version/s: 1.0.1.CR2 (was: 1.0.2.CR1) > Passivation of stateful session beans results in a loss of reference to injected object > --------------------------------------------------------------------------------------- > > Key: WELD-80 > URL: https://jira.jboss.org/jira/browse/WELD-80 > Project: Weld > Issue Type: Bug > Components: Scopes & Contexts > Environment: JBoss AS 5.1 > Reporter: John Ament > Fix For: 1.0.1.CR2 > > Attachments: statefulpassivate.zip > > > See forum post -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (WELD-15) Request scope is not active/destroyed during call to Ejb timeout method

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-15?page=com.atlassian.jira.plugin... ] Pete Muir closed WELD-15. ------------------------- Resolution: Done Assignee: Pete Muir Documented the correct approach, but not tested in JBAS as not support > Request scope is not active/destroyed during call to Ejb timeout method > ----------------------------------------------------------------------- > > Key: WELD-15 > URL: https://jira.jboss.org/jira/browse/WELD-15 > Project: Weld > Issue Type: Bug > Components: Class Beans (Managed and Session) > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Minor > Fix For: 1.0.1.CR1 > > > org.jboss.jsr299.tck.tests.context.request.ejb.EJBRequestContextTest.testRequestScopeActiveDuringCallToEjbTimeoutMethod() > org.jboss.jsr299.tck.tests.context.request.ejb.EJBRequestContextTest.testRequestScopeDestroyedAfterCallToEjbTimeoutMethod() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (WELD-29) web.xml configured jsf error-page throws ContextNotActiveException

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-29?page=com.atlassian.jira.plugin... ] Pete Muir updated WELD-29: -------------------------- Fix Version/s: 1.0.1.CR2 (was: 1.0.1.CR1) > web.xml configured jsf error-page throws ContextNotActiveException > ------------------------------------------------------------------ > > Key: WELD-29 > URL: https://jira.jboss.org/jira/browse/WELD-29 > Project: Weld > Issue Type: Bug > Components: GlassFish Integration, Scopes & Contexts, Web Tier integration (JSF, JSP, EL and Servlet) > Affects Versions: 1.0.0.PREVIEW1 > Environment: glassfish V3 prelude, jsf 2.0.0-SNAPSHOT (May 17 2009) > Reporter: Guy Veraghtert > Assignee: Pete Muir > Fix For: 1.0.1.CR2 > > > An ContextNotActiveException is thrown by Web beans when the container tries to forward to a jsf error-page (configured in web.xml). See forum reference. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-372) Consider whether we should treat AnnotatedClass definitions which do exactly mirror the reflected class definition as an error

by Pete Muir (JIRA)

Consider whether we should treat AnnotatedClass definitions which do exactly mirror the reflected class definition as an error ------------------------------------------------------------------------------------------------------------------------------ Key: WELD-372 URL: https://jira.jboss.org/jira/browse/WELD-372 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Reporter: Pete Muir Priority: Critical Fix For: 1.0.1.CR1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
5
0 / 0

[JBoss JIRA] Created: (WELD-272) DefinitionError thrown when a decorated bean is final or has final method (should be DeploymentError)

by Jozef Hartinger (JIRA)

DefinitionError thrown when a decorated bean is final or has final method (should be DeploymentError) ----------------------------------------------------------------------------------------------------- Key: WELD-272 URL: https://jira.jboss.org/jira/browse/WELD-272 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API, Interceptors and Decorators Affects Versions: 1.0.0.CR1 Reporter: Jozef Hartinger Fix For: 1.0.0.GA org.jboss.jsr299.tck.tests.decorators.definition.broken.finalBeanClass.FinalBeanClassTest.testAppliesToFinalManagedBeanClass() org.jboss.jsr299.tck.tests.decorators.definition.broken.finalBeanMethod.FinalBeanMethodTest.testAppliesToFinalMethodOnManagedBeanClass() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
4
0 / 0

[JBoss JIRA] Created: (WELD-274) Deployment problem not detected when a custom decorator can decorate final bean

by Jozef Hartinger (JIRA)

Deployment problem not detected when a custom decorator can decorate final bean ------------------------------------------------------------------------------- Key: WELD-274 URL: https://jira.jboss.org/jira/browse/WELD-274 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API, Interceptors and Decorators Affects Versions: 1.0.0.CR1 Reporter: Jozef Hartinger Fix For: 1.0.0.GA org.jboss.jsr299.tck.tests.decorators.custom.broken.finalBeanClass.CustomDecoratorMatchingBeanWithFinalClassTest.testCustomDecoratorDecoratingFinalBean() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
5
0 / 0

[JBoss JIRA] Updated: (WELD-27) Consider using JBoss maven plugin, not ant for example builds

by Dan Allen (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-27?page=com.atlassian.jira.plugin... ] Dan Allen updated WELD-27: -------------------------- Fix Version/s: 1.0.2.CR1 (was: 1.0.1.CR1) The Embedded JBoss configuration should be opened as a separate issue because, as it turns out, there isn't actually an Embedded JBoss Maven plugin yet, so there is nothing we can do there. > Consider using JBoss maven plugin, not ant for example builds > ------------------------------------------------------------- > > Key: WELD-27 > URL: https://jira.jboss.org/jira/browse/WELD-27 > Project: Weld > Issue Type: Task > Components: Examples > Reporter: Pete Muir > Assignee: Dan Allen > Fix For: 1.0.2.CR1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-291) Decorator @Delegate injection points cause unsatisfied and ambiguous dependencies

by Gavin King (JIRA)

Decorator @Delegate injection points cause unsatisfied and ambiguous dependencies --------------------------------------------------------------------------------- Key: WELD-291 URL: https://jira.jboss.org/jira/browse/WELD-291 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.0.GA Reporter: Gavin King Priority: Critical Fix For: 1.0.1.CR1 A decorator delegate injection point should not be validated for unsatisfied or ambiguous dependencies. Currently Weld fails at startup when a decorator applies to either 0 or more than 1 bean. Which makes decorators useless :-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (WELD-314) Interceptors applied twice on beans when there is a decorator

by Wayne Zhang (JIRA)

Interceptors applied twice on beans when there is a decorator ------------------------------------------------------------- Key: WELD-314 URL: https://jira.jboss.org/jira/browse/WELD-314 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.0.GA Environment: Os: Linux AppServer: Glassfish v3 b73 Reporter: Wayne Zhang Interceptors applied twice when there is a decorator. The following log is from a example application. Bean SimplePaymentService has two interceptors - AuditInterceptor and TransactionInterceptor. Also, SimplePaymentService has a decorator - SecurePaymentService. When business method pay() is called, these 2 interceptors called twice: (Example application in a NetBeans 6.8 project attached) [#|2009-11-24T14:29:03.887+0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Thread-1;|2009-11-24 14:29:03,885 - INFO weld.lab1.interceptor.TransactionInterceptor - Start transaction for weld.lab1.service.SimplePaymentService_$$_javassist_384, instance=weld.lab1.service.SimplePaymentService@1b5adb0 |#] [#|2009-11-24T14:29:03.888+0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Thread-1;|2009-11-24 14:29:03,887 - INFO weld.lab1.interceptor.AuditInterceptor - Method public boolean weld.lab1.service.SimplePaymentService.pay(java.lang.String,java.math.BigDecimal) throws java.lang.Exception on Bean class org.jboss.interceptor.proxy.AbstractClassInterceptionHandler$DelegatingInvocationContext invoked. |#] [#|2009-11-24T14:29:03.888+0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Thread-1;|2009-11-24 14:29:03,888 - INFO weld.lab1.service.SecurePaymentService - I'm a secure payment service |#] [#|2009-11-24T14:29:03.888+0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Thread-1;|2009-11-24 14:29:03,888 - INFO weld.lab1.interceptor.TransactionInterceptor - Start transaction for weld.lab1.service.SimplePaymentService_$$_javassist_384, instance=weld.lab1.service.SimplePaymentService@1b5adb0 |#] [#|2009-11-24T14:29:03.888+0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Thread-1;|2009-11-24 14:29:03,888 - INFO weld.lab1.interceptor.AuditInterceptor - Method public boolean weld.lab1.service.SimplePaymentService.pay(java.lang.String,java.math.BigDecimal) throws java.lang.Exception on Bean class org.jboss.interceptor.proxy.AbstractClassInterceptionHandler$DelegatingInvocationContext invoked. |#] [#|2009-11-24T14:29:03.888+0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Thread-1;|2009-11-24 14:29:03,888 - INFO weld.lab1.service.SimplePaymentService - Pay $0.03 for NetBeans. |#] [#|2009-11-24T14:29:03.904+0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Thread-1;|2009-11-24 14:29:03,904 - INFO weld.lab1.event.PaymentServiceListener - Payment processed: account=NetBeans, amount=0.03 |#] [#|2009-11-24T14:29:03.905+0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Thread-1;|2009-11-24 14:29:03,905 - INFO weld.lab1.interceptor.TransactionInterceptor - Transaction commited. |#] [#|2009-11-24T14:29:03.905+0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Thread-1;|2009-11-24 14:29:03,905 - INFO weld.lab1.event.PaymentServiceListener - Payment success: account=NetBeans, amount=0.03 |#] [#|2009-11-24T14:29:03.905+0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Thread-1;|2009-11-24 14:29:03,905 - INFO weld.lab1.interceptor.TransactionInterceptor - Transaction commited. |#] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues January 2010