February 2013 - seam-issues - Jboss List Archives

[JBoss JIRA] (JBSEAM-5077) ui example, s:resource s:download error 404

by Jens Westermann (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5077?page=com.atlassian.jira.plugi... ] Jens Westermann edited comment on JBSEAM-5077 at 2/27/13 9:31 AM: ------------------------------------------------------------------ import java.io.Serializable; import java.util.HashMap; import java.util.Map; import javax.faces.application.ViewHandler; import javax.faces.context.FacesContext; import org.jboss.seam.Component; import org.jboss.seam.ScopeType; import org.jboss.seam.annotations.Install; import org.jboss.seam.annotations.Name; import org.jboss.seam.annotations.Scope; import org.jboss.seam.document.DocumentData; import org.jboss.seam.util.Faces; @Name("org.jboss.seam.document.documentStore") @Scope(ScopeType.CONVERSATION) @Install(precedence = Install.APPLICATION) @Deprecated public class DocumentStoreTempFix extends org.jboss.seam.document.DocumentStore implements Serializable { private static final long serialVersionUID = -1L; @Override public String preferredUrlForContent(String baseName, String extension, String contentId) { String result = baseUrlForContent(baseName, extension); StringBuilder sb = new StringBuilder(result); if (result.indexOf('?') >= 0) { sb.append("&"); } else { sb.append("?"); } sb.append("docId="); sb.append(contentId); return sb.toString(); } } was (Author: jan.daces): package ch.inspirion.zeiterfassung.seamfaces; import java.io.Serializable; import java.util.HashMap; import java.util.Map; import javax.faces.application.ViewHandler; import javax.faces.context.FacesContext; import org.jboss.seam.Component; import org.jboss.seam.ScopeType; import org.jboss.seam.annotations.Install; import org.jboss.seam.annotations.Name; import org.jboss.seam.annotations.Scope; import org.jboss.seam.document.DocumentData; import org.jboss.seam.util.Faces; @Name("org.jboss.seam.document.documentStore") @Scope(ScopeType.CONVERSATION) @Install(precedence = Install.APPLICATION) @Deprecated public class DocumentStoreTempFix extends org.jboss.seam.document.DocumentStore implements Serializable { private static final long serialVersionUID = -1L; @Override public String preferredUrlForContent(String baseName, String extension, String contentId) { String result = baseUrlForContent(baseName, extension); StringBuilder sb = new StringBuilder(result); if (result.indexOf('?') >= 0) { sb.append("&"); } else { sb.append("?"); } sb.append("docId="); sb.append(contentId); return sb.toString(); } } > ui example, s:resource s:download error 404 > ------------------------------------------- > > Key: JBSEAM-5077 > URL: https://issues.jboss.org/browse/JBSEAM-5077 > Project: Seam 2 > Issue Type: Bug > Components: JSF Controls > Affects Versions: 2.3.1.CR1 > Environment: AS 7.1.1.Final, Seam 2.3.1-SNAPSHOT > Reporter: Marek Schmidt > Assignee: Marek Novotny > Priority: Critical > Labels: regression > Fix For: 2.3.1.CR1 > > > s:resource and s:download links don't work anymore in the current Seam 2.3.1-SNAPSHOT > Clicking on any of the seam-ui example links in http://127.0.0.1:8080/seam-ui/resource.seam leads to a 404 error -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5077) ui example, s:resource s:download error 404

by Jens Westermann (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5077?page=com.atlassian.jira.plugi... ] Jens Westermann commented on JBSEAM-5077: ----------------------------------------- package ch.inspirion.zeiterfassung.seamfaces; import java.io.Serializable; import java.util.HashMap; import java.util.Map; import javax.faces.application.ViewHandler; import javax.faces.context.FacesContext; import org.jboss.seam.Component; import org.jboss.seam.ScopeType; import org.jboss.seam.annotations.Install; import org.jboss.seam.annotations.Name; import org.jboss.seam.annotations.Scope; import org.jboss.seam.document.DocumentData; import org.jboss.seam.util.Faces; @Name("org.jboss.seam.document.documentStore") @Scope(ScopeType.CONVERSATION) @Install(precedence = Install.APPLICATION) @Deprecated public class DocumentStoreTempFix extends org.jboss.seam.document.DocumentStore implements Serializable { private static final long serialVersionUID = -1L; @Override public String preferredUrlForContent(String baseName, String extension, String contentId) { String result = baseUrlForContent(baseName, extension); StringBuilder sb = new StringBuilder(result); if (result.indexOf('?') >= 0) { sb.append("&"); } else { sb.append("?"); } sb.append("docId="); sb.append(contentId); return sb.toString(); } } > ui example, s:resource s:download error 404 > ------------------------------------------- > > Key: JBSEAM-5077 > URL: https://issues.jboss.org/browse/JBSEAM-5077 > Project: Seam 2 > Issue Type: Bug > Components: JSF Controls > Affects Versions: 2.3.1.CR1 > Environment: AS 7.1.1.Final, Seam 2.3.1-SNAPSHOT > Reporter: Marek Schmidt > Assignee: Marek Novotny > Priority: Critical > Labels: regression > Fix For: 2.3.1.CR1 > > > s:resource and s:download links don't work anymore in the current Seam 2.3.1-SNAPSHOT > Clicking on any of the seam-ui example links in http://127.0.0.1:8080/seam-ui/resource.seam leads to a 404 error -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SOLDER-340) Memory Leak during DOS Attack using OWASP DirBuster

by Ken Finnigan (JIRA)

[ https://issues.jboss.org/browse/SOLDER-340?page=com.atlassian.jira.plugin... ] Ken Finnigan commented on SOLDER-340: ------------------------------------- That's fine, but in the future it's best to include a full description of what is causing the error to prevent wasted time on both our parts. > Memory Leak during DOS Attack using OWASP DirBuster > --------------------------------------------------- > > Key: SOLDER-340 > URL: https://issues.jboss.org/browse/SOLDER-340 > Project: Solder > Issue Type: Bug > Components: Servlet > Affects Versions: 3.2.0.Final > Environment: ALL > Reporter: Melloware Inc > Priority: Critical > Attachments: memoryleak.zip > > > During performance testing of our application using OWASP DirBuster to simulate a DOS attack scanning for directories it appears our EAP 6.0.1 leaked memory until the JVM Locked up. Even after manually attempting a GC the memory stays frozen and does not free up. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SOLDER-340) Memory Leak during DOS Attack using OWASP DirBuster

by Melloware Inc (JIRA)

[ https://issues.jboss.org/browse/SOLDER-340?page=com.atlassian.jira.plugin... ] Melloware Inc commented on SOLDER-340: -------------------------------------- It is not @ViewScoped issue. What is happening is that Solder's ServletEventBridgeListener is creating events which contain non-constant qualifiers (using the HTTP method and path), and that is causing a cache to increase in size without limit. > Memory Leak during DOS Attack using OWASP DirBuster > --------------------------------------------------- > > Key: SOLDER-340 > URL: https://issues.jboss.org/browse/SOLDER-340 > Project: Solder > Issue Type: Bug > Components: Servlet > Affects Versions: 3.2.0.Final > Environment: ALL > Reporter: Melloware Inc > Priority: Critical > Attachments: memoryleak.zip > > > During performance testing of our application using OWASP DirBuster to simulate a DOS attack scanning for directories it appears our EAP 6.0.1 leaked memory until the JVM Locked up. Even after manually attempting a GC the memory stays frozen and does not free up. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SOLDER-340) Memory Leak during DOS Attack using OWASP DirBuster

by Ken Finnigan (JIRA)

[ https://issues.jboss.org/browse/SOLDER-340?page=com.atlassian.jira.plugin... ] Ken Finnigan commented on SOLDER-340: ------------------------------------- If the leaked memory is caused by @ViewScoped beans, then I think your problem is due to: https://issues.jboss.org/browse/JBPAPP-10634 > Memory Leak during DOS Attack using OWASP DirBuster > --------------------------------------------------- > > Key: SOLDER-340 > URL: https://issues.jboss.org/browse/SOLDER-340 > Project: Solder > Issue Type: Bug > Components: Servlet > Affects Versions: 3.2.0.Final > Environment: ALL > Reporter: Melloware Inc > Priority: Critical > Attachments: memoryleak.zip > > > During performance testing of our application using OWASP DirBuster to simulate a DOS attack scanning for directories it appears our EAP 6.0.1 leaked memory until the JVM Locked up. Even after manually attempting a GC the memory stays frozen and does not free up. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SOLDER-340) Memory Leak during DOS Attack using OWASP DirBuster

by Melloware Inc (JIRA)

[ https://issues.jboss.org/browse/SOLDER-340?page=com.atlassian.jira.plugin... ] Melloware Inc updated SOLDER-340: --------------------------------- Attachment: memoryleak.zip Sample WAR demonstrating the issue. > Memory Leak during DOS Attack using OWASP DirBuster > --------------------------------------------------- > > Key: SOLDER-340 > URL: https://issues.jboss.org/browse/SOLDER-340 > Project: Solder > Issue Type: Bug > Components: Servlet > Affects Versions: 3.2.0.Final > Environment: ALL > Reporter: Melloware Inc > Priority: Critical > Attachments: memoryleak.zip > > > During performance testing of our application using OWASP DirBuster to simulate a DOS attack scanning for directories it appears our EAP 6.0.1 leaked memory until the JVM Locked up. Even after manually attempting a GC the memory stays frozen and does not free up. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SOLDER-340) Memory Leak during DOS Attack using OWASP DirBuster

by Melloware Inc (JIRA)

[ https://issues.jboss.org/browse/SOLDER-340?page=com.atlassian.jira.plugin... ] Melloware Inc updated SOLDER-340: --------------------------------- Steps to Reproduce: I have attached a maven project for a simple WAR file that can reproduce it. Reproduction Instructions: 1. Unzip the war and run "mvn clean package" to build the memoryleak.war. 2. Deploy it in a Jboss AS 7.1.1. 3. Download and run the OWASP DirBuster app. https://www.owasp.org/index.php/Category:OWASP_DirBuster_Project 4. The DirBuster app comes with a file directory-list-2.3-medium.txt which is what we used to simulate the run. It attemps to just access random urls under the main webapp. Attached is a screenshot of our exact settings. was: I have attached a maven project for a simple WAR file that can reproduce it. Reproduction Instructions: 1. Unzip the war and run "mvn clean package" to build the memoryleak.war. 2. Deploy it in a Jboss EAP 6. 3. Download and run the OWASP DirBuster app. https://www.owasp.org/index.php/Category:OWASP_DirBuster_Project 4. The DirBuster app comes with a file directory-list-2.3-medium.txt which is what we used to simulate the run. It attemps to just access random urls under the main webapp. Attached is a screenshot of our exact settings. > Memory Leak during DOS Attack using OWASP DirBuster > --------------------------------------------------- > > Key: SOLDER-340 > URL: https://issues.jboss.org/browse/SOLDER-340 > Project: Solder > Issue Type: Bug > Components: Servlet > Affects Versions: 3.2.0.Final > Environment: ALL > Reporter: Melloware Inc > Priority: Critical > Attachments: memoryleak.zip > > > During performance testing of our application using OWASP DirBuster to simulate a DOS attack scanning for directories it appears our EAP 6.0.1 leaked memory until the JVM Locked up. Even after manually attempting a GC the memory stays frozen and does not free up. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SOLDER-340) Memory Leak during DOS Attack using OWASP DirBuster

by Melloware Inc (JIRA)

Melloware Inc created SOLDER-340: ------------------------------------ Summary: Memory Leak during DOS Attack using OWASP DirBuster Key: SOLDER-340 URL: https://issues.jboss.org/browse/SOLDER-340 Project: Solder Issue Type: Bug Components: Servlet Affects Versions: 3.2.0.Final Environment: ALL Reporter: Melloware Inc Priority: Critical During performance testing of our application using OWASP DirBuster to simulate a DOS attack scanning for directories it appears our EAP 6.0.1 leaked memory until the JVM Locked up. Even after manually attempting a GC the memory stays frozen and does not free up. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SEAMREMOTING-54) seam-remoting call identity.logout run to a exception

by haisheng mi (JIRA)

haisheng mi created SEAMREMOTING-54: --------------------------------------- Summary: seam-remoting call identity.logout run to a exception Key: SEAMREMOTING-54 URL: https://issues.jboss.org/browse/SEAMREMOTING-54 Project: Seam Remoting Issue Type: Bug Environment: jboss 7.1.1.final jdk1.7.0_07 Reporter: haisheng mi seam-remoting call identity.logout run to a error. my Authenticator Class below. ------------------------------------------------------- public class SimpleAuthenticator extends BaseAuthenticator implements Authenticator { @Inject Credentials credentials; @Override public void authenticate() { if ("demo".equals(credentials.getUsername()) && credentials.getCredential() instanceof PasswordCredential && "demo".equals(((PasswordCredential) credentials.getCredential()).getValue())) { setStatus(AuthenticationStatus.SUCCESS); setUser(new SimpleUser("demo")); System.out.println("SUCCESS."); }else{ setStatus(AuthenticationStatus.FAILURE); System.out.println("FAILURE."); } } } ----------------------------------------------------- and this is a Login action below. ------------------------------------------------------- public class Login { @Inject Credentials credentials; @Inject Identity identiy; @WebRemote public void check_user(String user_name,String user_password) throws Exception { credentials.setCredential(new PasswordCredential(user_password)); credentials.setUsername(user_name); identiy.login(); } @WebRemote public void logout() throws Exception { identiy.logout(); } } ------------------------------------------------------ in the browser,i use javascript to call check_user function: ------------------------------------------------------ Seam.createBean("Login", "Formal").check_user("demo","demo"); ----------------------------------------------------- then console out put 'SUCCESS'. but when called Seam.createBean("Login", "Formal").logout(callback); the browser show : ============== An exception has occurred while executing a remote request: java.lang.IllegalStateException:Attempted to inject an HttpSession before it has been initialized. ============== the console show : 18:28:04,121 ERROR [org.jboss.seam.remoting.ExecutionHandler] (http-localhost-127.0.0.1-8080-4) Error while executing call: java.lang.IllegalStateException: Attempted to inject an HttpSession before it has been initialized. at org.jboss.solder.servlet.http.ImplicitHttpServletObjectsProducer.getHttpSession(ImplicitHttpServletObjectsProducer.java:55) [solder-impl-3.1.0.Final.jar:3.1.0.Final] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_07] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_07] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_07] at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_07] at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:264) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:260) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:170) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstance(MethodInjectionPoint.java:137) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.jboss.weld.bean.ProducerMethod$1.produce(ProducerMethod.java:133) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:299) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:107) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:90) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:104) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.jboss.weld.proxies.HttpSession$1681475766$Proxy$_$$_WeldClientProxy.invalidate(HttpSession$1681475766$Proxy$_$$_WeldClientProxy.java) [weld-core-1.1.5.AS71.Final.jar:] at org.jboss.seam.security.IdentityImpl.logout(IdentityImpl.java:427) [seam-security-3.1.0.Final.jar:3.1.0.Final] at org.jboss.seam.security.IdentityImpl$Proxy$_$$_WeldClientProxy.logout(IdentityImpl$Proxy$_$$_WeldClientProxy.java) [seam-security-3.1.0.Final.jar:3.1.0.Final] at Login.logout(Login.java:21) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_07] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_07] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_07] at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_07] at org.jboss.seam.remoting.Call.execute(Call.java:170) [seam-remoting-3.1.0.Final.jar:3.1.0.Final] at org.jboss.seam.remoting.ExecutionHandler.handle(ExecutionHandler.java:72) [seam-remoting-3.1.0.Final.jar:3.1.0.Final] at org.jboss.seam.remoting.Remoting.service(Remoting.java:251) [seam-remoting-3.1.0.Final.jar:3.1.0.Final] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07] -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SEAM-138) ...thread is already associated with a transaction!

by Gustavo Oliveira (JIRA)

[ https://issues.jboss.org/browse/SEAM-138?page=com.atlassian.jira.plugin.s... ] Gustavo Oliveira commented on SEAM-138: --------------------------------------- Any word on this issue? I am facing the same problem. > ...thread is already associated with a transaction! > --------------------------------------------------- > > Key: SEAM-138 > URL: https://issues.jboss.org/browse/SEAM-138 > Project: Seam 3 Distribution > Issue Type: Bug > Affects Versions: 3.1.0.Final > Environment: Windows, JBPM 5.3.0 Final, Drools 5.4.0 Final, JBOSS 7.0.2 Final > Reporter: Andrea Carpineti > Labels: jta, transaction > > I believe the issue is related to Seam but I'm not completely sure... > Using the JBPM console sometimes we experienced an issue due to which the deployed processes are no longer available. They simply disappear. > Although the issue is not always repro we experienced it mainly after several minutes of use. > Lookin in the {{server.log}} we found the following exceptions: > {quote} > 10:41:15,751 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]] (http-localhost-127.0.0.1-8080-76) Exception sending request initialized lifecycle event to listener instance of class org.jboss.seam.transaction.TransactionServletListener: javax.enterprise.event.ObserverException > at sun.reflect.GeneratedConstructorAccessor243.newInstance(Unknown Source) [:1.6.0_31] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [:1.6.0_31] > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) [:1.6.0_31] > at java.lang.Class.newInstance0(Class.java:355) [:1.6.0_31] > at java.lang.Class.newInstance(Class.java:308) [:1.6.0_31] > at org.jboss.weld.util.reflection.SecureReflections$16.work(SecureReflections.java:395) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInstantiation(SecureReflectionAccess.java:216) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.util.reflection.SecureReflections.newInstance(SecureReflections.java:390) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:40) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:92) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:214) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.seam.transaction.TransactionServletListener.requestInitialized(TransactionServletListener.java:117) [seam-transaction-3.1.0.Final.jar:] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_31] > Caused by: javax.transaction.NotSupportedException: BaseTransaction.checkTransactionState - thread is already associated with a transaction! > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:65) > at org.jboss.seam.transaction.UTTransaction.begin(UTTransaction.java:51) [seam-transaction-3.1.0.Final.jar:] > at org.jboss.seam.transaction.DefaultSeamTransaction.begin(DefaultSeamTransaction.java:88) [seam-transaction-3.1.0.Final.jar:] > at org.jboss.seam.transaction.TransactionServletListener.requestInitialized(TransactionServletListener.java:110) [seam-transaction-3.1.0.Final.jar:] > ... 8 more > Caused by: java.lang.IllegalStateException: BaseTransaction.checkTransactionState - thread is already associated with a transaction! > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.checkTransactionState(BaseTransaction.java:259) > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:61) > ... 11 more > 10:41:15,760 WARN [org.jboss.seam.transaction.TransactionServletListener] (http-localhost-127.0.0.1-8080-76) Error starting the transaction: javax.transaction.NotSupportedException: BaseTransaction.checkTransactionState - thread is already associated with a transaction! > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:65) > at org.jboss.seam.transaction.UTTransaction.begin(UTTransaction.java:51) [seam-transaction-3.1.0.Final.jar:] > at org.jboss.seam.transaction.DefaultSeamTransaction.begin(DefaultSeamTransaction.java:88) [seam-transaction-3.1.0.Final.jar:] > at org.jboss.seam.transaction.TransactionServletListener.requestInitialized(TransactionServletListener.java:110) [seam-transaction-3.1.0.Final.jar:] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_31] > Caused by: java.lang.IllegalStateException: BaseTransaction.checkTransactionState - thread is already associated with a transaction! > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.checkTransactionState(BaseTransaction.java:259) > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:61) > ... 11 more > 10:41:15,762 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]] (http-localhost-127.0.0.1-8080-76) Exception sending request initialized lifecycle event to listener instance of class org.jboss.seam.transaction.TransactionServletListener: javax.enterprise.event.ObserverException > at sun.reflect.GeneratedConstructorAccessor243.newInstance(Unknown Source) [:1.6.0_31] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [:1.6.0_31] > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) [:1.6.0_31] > at java.lang.Class.newInstance0(Class.java:355) [:1.6.0_31] > at java.lang.Class.newInstance(Class.java:308) [:1.6.0_31] > at org.jboss.weld.util.reflection.SecureReflections$16.work(SecureReflections.java:395) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInstantiation(SecureReflectionAccess.java:216) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.util.reflection.SecureReflections.newInstance(SecureReflections.java:390) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:40) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:92) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:214) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.seam.transaction.TransactionServletListener.requestInitialized(TransactionServletListener.java:117) [seam-transaction-3.1.0.Final.jar:] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_31] > Caused by: javax.transaction.NotSupportedException: BaseTransaction.checkTransactionState - thread is already associated with a transaction! > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:65) > at org.jboss.seam.transaction.UTTransaction.begin(UTTransaction.java:51) [seam-transaction-3.1.0.Final.jar:] > at org.jboss.seam.transaction.DefaultSeamTransaction.begin(DefaultSeamTransaction.java:88) [seam-transaction-3.1.0.Final.jar:] > at org.jboss.seam.transaction.TransactionServletListener.requestInitialized(TransactionServletListener.java:110) [seam-transaction-3.1.0.Final.jar:] > ... 8 more > Caused by: java.lang.IllegalStateException: BaseTransaction.checkTransactionState - thread is already associated with a transaction! > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.checkTransactionState(BaseTransaction.java:259) > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:61) > ... 11 more > {quote} -- 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

11 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2013