June 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

12 years, 3 months

4
10
0 / 0

[JBoss JIRA] (JBSEAM-4995) seam-gen doesn't automatically include jdbc-driver jar to project classpath

by Tomas Remes (JIRA)

12 years, 3 months

4
8
0 / 0

[JBoss JIRA] (JBSEAM-4957) JBoss Tools and M2e-WTP doesn't filter properly

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-4957: ------------------------------------- Summary: JBoss Tools and M2e-WTP doesn't filter properly Key: JBSEAM-4957 URL: https://issues.jboss.org/browse/JBSEAM-4957 Project: Seam 2 Issue Type: Task Components: Tools Affects Versions: 2.3.0.BETA1, 2.3.0.BETA2 Environment: JBoss Tools nightly build from 21st May Reporter: Marek Novotny Imported examples from SVN into JBoss Tools are not correctly build. There is blocked filtering of @@ tokens and that causes errors in deployment phase for instance @jndiPattern@ are not evaluated correctly. {noformat} Caused by: java.lang.IllegalArgumentException: Exception setting property org.jboss.seam.core.init.jndiPattern on component org.jboss.seam.core.init. Expression @jndiPattern@ evaluated to null. {noformat} -- 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

12 years, 3 months

2
7
0 / 0

[JBoss JIRA] (JBSEAM-4926) openid example fails with "/openid.xhtml Not Found in ExternalContext as a Resource"

by Marek Schmidt (JIRA)

Marek Schmidt created JBSEAM-4926: ------------------------------------- Summary: openid example fails with "/openid.xhtml Not Found in ExternalContext as a Resource" Key: JBSEAM-4926 URL: https://issues.jboss.org/browse/JBSEAM-4926 Project: Seam 2 Issue Type: Bug Components: Security Affects Versions: 2.3.0.BETA1 Environment: AS7.1.1.Final Reporter: Marek Schmidt Assignee: Marek Novotny Fix For: 2.3.0.BETA2 The OpenIdPhaseListener doesn't seem to work unless a fake openid.xhtml exists: Exception during request processing: Caused by com.sun.faces.context.FacesFileNotFoundException with message: "/openid.xhtml Not Found in ExternalContext as a Resource" {noformat} com.sun.faces.facelets.impl.DefaultFaceletFactory.resolveURL(DefaultFaceletFactory.java:232) com.sun.faces.facelets.impl.DefaultFaceletFactory.resolveURL(DefaultFaceletFactory.java:273) com.sun.faces.facelets.impl.DefaultFaceletFactory.getMetadataFacelet(DefaultFaceletFactory.java:209) com.sun.faces.application.view.ViewMetadataImpl.createMetadataView(ViewMetadataImpl.java:114) com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:233) com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116) com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) org.jboss.seam.web.RewriteFilter.doFilter(RewriteFilter.java:63) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) java.lang.Thread.run(Thread.java:662) {noformat} -- 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

12 years, 3 months

4
6
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

12 years, 3 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

12 years, 3 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

12 years, 3 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

12 years, 3 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

12 years, 3 months

2
1
0 / 0

[JBoss JIRA] (JBSEAM-4978) Seam-gen commands using hibernate-tools doesn't work

by Tomas Remes (JIRA)

Tomas Remes created JBSEAM-4978: ----------------------------------- Summary: Seam-gen commands using hibernate-tools doesn't work Key: JBSEAM-4978 URL: https://issues.jboss.org/browse/JBSEAM-4978 Project: Seam 2 Issue Type: Bug Components: Tools Affects Versions: 2.3.0.BETA2 Reporter: Tomas Remes Fix For: 2.3.0.CR1 Seam-gen commands like "generate-model","generate", "generate-ui" does not work, because it's using old hibernate-tools version. Major problem is that this old version is using classes from hibernate-core 3.2.4 (and probably many other jars) and those are not compatible with hibernate 4 versions. So when you try for example command "generate-model", you will get following error: {noformat} jboss-seam-2.3.0.CR1-SNAPSHOT/seam-gen/build.xml:1554: java.lang.NoClassDefFoundError: org/hibernate/engine/Mapping {noformat} I am trying/investigating how is this used in JBoss Tools, but as far as I've understood there is entirely bundled old hibernate 3 and its related stuff. -- 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

12 years, 3 months

4
13
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues June 2012