February 2012 - seam-issues - Jboss List Archives

[JBoss JIRA] (JBSEAM-4863) Memory Leak when calling @Destroy (with SFSBs)

by Daniel Lechner (Created) (JIRA)

Memory Leak when calling @Destroy (with SFSBs) ---------------------------------------------- Key: JBSEAM-4863 URL: https://issues.jboss.org/browse/JBSEAM-4863 Project: Seam 2 Issue Type: Bug Affects Versions: 2.2.2.Final Environment: JBoss AS 5.1.0.GA Reporter: Daniel Lechner In an example-project, we have 2 Seam components, one POJO and one SFSB. The POJO-component uses the SFSB-component via Seam-DI (@In). The POJO-component has a method annotated with @Destroy. We are using the POJO-component in a (long-running-)conversation. So the POJO-component as well as the SFSB-component will be created within the conversation. When the conversation ends and all components will be removed, the @Destroy-methods of all seam-components are called one after each other. The order, the @Destroy-methods are called, depend on the hashCode of the seam-name of the components (the component-names are put into an java.util.HashSet in the method org.jboss.seam.contexts.ServerConversationContext.getNamesFromSession() - the for-loop of the method org.jboss.seam.contexts.Contexts.destroy iterates through this HashSet afterwards). If the component-names are chosen this way, that the SFSB-component will be removed before the POJO-component is removed, a memory leak occurs: 1. the SFSB-component is destroyed by seam - the container removes the SFSB (the @Remove-method of the SFSB is called) 2. the @Destroy-method of the POJO-component is called. But before, Seam-DI creates a new SFSB-component TestEJB because of the @In-annotation 3. the POJO-component is removed from the conversation (and later by the GC) 4. the SFSB-component's @Remove-method is not called again - the container keeps the SFSB-instance An example-code can be found in the forum reference -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

4
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB

by Siarhei Dudzin (JIRA)

MDB activated too early to use Seam components as a standard EJB ---------------------------------------------------------------- Key: JBSEAM-2286 URL: http://jira.jboss.com/jira/browse/JBSEAM-2286 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Reporter: Siarhei Dudzin Priority: Critical As specified in the forum reference I have an MDB which uses a SLSB (also declared as Seam component) with business logic. If I deploy the application and there are already messages in the queue I get the following exception: javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted to invoke a Seam component outside the an initialized application at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138) at $Proxy111.onMessage(Unknown Source) Looks like the MDB processing the message before Seam is initialized? This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate business logic if I want to re-use the same functionality of the SLSB in Seam. I could use the solution from http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me to use vendor-specific API. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

13
22
0 / 0

[JBoss JIRA] (JBSEAM-4867) Run Seam 2.3 through the Seam 2 smoke tests

by Pete Muir (JIRA)

Pete Muir created JBSEAM-4867: --------------------------------- Summary: Run Seam 2.3 through the Seam 2 smoke tests Key: JBSEAM-4867 URL: https://issues.jboss.org/browse/JBSEAM-4867 Project: Seam 2 Issue Type: Feature Request Reporter: Pete Muir Priority: Critical Fix For: 2.3.0.BETA1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

5
12
0 / 0

[JBoss JIRA] (JBSEAM-4871) Seam 2.3 Critical Path - describes key requirements for Seam 2.3

by Pete Muir (JIRA)

Pete Muir created JBSEAM-4871: --------------------------------- Summary: Seam 2.3 Critical Path - describes key requirements for Seam 2.3 Key: JBSEAM-4871 URL: https://issues.jboss.org/browse/JBSEAM-4871 Project: Seam 2 Issue Type: Task Reporter: Pete Muir Assignee: Pete Muir Fix For: 2.3.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

2
2
0 / 0

[JBoss JIRA] (JBSEAM-4878) Create migration guide from Seam 2.2 to Seam 2.3 for reference guide

by Pete Muir (JIRA)

Pete Muir created JBSEAM-4878: --------------------------------- Summary: Create migration guide from Seam 2.2 to Seam 2.3 for reference guide Key: JBSEAM-4878 URL: https://issues.jboss.org/browse/JBSEAM-4878 Project: Seam 2 Issue Type: Sub-task Reporter: Pete Muir -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4320) Conversation propagation in SeamTest is broken.

by Arno Mittelbach (JIRA)

Conversation propagation in SeamTest is broken. ----------------------------------------------- Key: JBSEAM-4320 URL: https://jira.jboss.org/jira/browse/JBSEAM-4320 Project: Seam Issue Type: Bug Reporter: Arno Mittelbach Coversation propagation between FacesRequests in SeamTest is broken when redirects occur. If a conversation is started in a FacesRequest that ends with a redirect, this conversation cannot be restored in a consecutive FacesRequest. -- 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

11 years, 7 months

2
1
0 / 0

[JBoss JIRA] (JBSEAM-4884) Misc issues

by Pete Muir (JIRA)

Pete Muir created JBSEAM-4884: --------------------------------- Summary: Misc issues Key: JBSEAM-4884 URL: https://issues.jboss.org/browse/JBSEAM-4884 Project: Seam 2 Issue Type: Sub-task Reporter: Pete Muir Fix For: 2.3.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBSEAM-4693) 6.12.2. Enabling Seam exception handling : web:exception-filter in components.xml

by simon lebettre (JIRA)

6.12.2. Enabling Seam exception handling : web:exception-filter in components.xml --------------------------------------------------------------------------------- Key: JBSEAM-4693 URL: https://jira.jboss.org/browse/JBSEAM-4693 Project: Seam Issue Type: Task Components: Documentation Issues Reporter: simon lebettre this does not make sense : " 6.12.2. Enabling Seam exception handling To enable Seam's exception handling, we need to make sure we have the master servlet filter declared in web.xml: " ==> Of course the master filter is in web.xml ! this would be more relevant : "we need to make sure that <web:exception-filter url-pattern="*.seam" /> is declared in components.xml" I m not being picky about the doc, it's been 7 months I have a bad user experience or loose some exception feedback because I forgot this line in components.xml ! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
3
0 / 0

[JBoss JIRA] (JBSEAM-4882) Verify JBDS "seam-gen" works with new Maven structure

by Pete Muir (JIRA)

Pete Muir created JBSEAM-4882: --------------------------------- Summary: Verify JBDS "seam-gen" works with new Maven structure Key: JBSEAM-4882 URL: https://issues.jboss.org/browse/JBSEAM-4882 Project: Seam 2 Issue Type: Sub-task Reporter: Pete Muir Fix For: 2.3.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
3
0 / 0

[JBoss JIRA] (JBSEAM-4881) Verify Seam-gen works with maven build structure

by Pete Muir (JIRA)

Pete Muir created JBSEAM-4881: --------------------------------- Summary: Verify Seam-gen works with maven build structure Key: JBSEAM-4881 URL: https://issues.jboss.org/browse/JBSEAM-4881 Project: Seam 2 Issue Type: Sub-task Reporter: Pete Muir -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2012