[ https://jira.jboss.org/jira/browse/JBSEAM-3570?page=com.atlassian.jira.pl... ] Shane Bryzak updated JBSEAM-3570: --------------------------------- Fix Version/s: 2.1.1.CR2 (was: 2.1.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

[ https://jira.jboss.org/jira/browse/JBSEAM-3570?page=com.atlassian.jira.pl... ] Marek Novotny commented on JBSEAM-3570: --------------------------------------- WAS V7 JSF implementation is somehow broken. The processing is hanging while you send request for home page of jpa example: [22.1.09 16:34:52:861 SEČ] 00000013 config I Initializing Sun's JavaServer Faces implementation (1.2_07-b03-FCS) for context '/seam-jpa' [22.1.09 16:34:54:774 SEČ] 00000013 servlet I com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I: [jboss-seam-jpa_war] [/seam-jpa] [Faces Servlet]: Inicializace proběhla úspěšně. [22.1.09 16:34:54:781 SEČ] 00000013 webcontainer I com.ibm.ws.wswebcontainer.VirtualHost addWebApplication SRVE0250I: Webový modul null byl svázán s virtuálním hostitelem default_host[*:9080,*:80,*:9443,*:5060,*:5061,*:443]. [22.1.09 16:34:54:809 SEČ] 00000013 ApplicationMg A WSVR0221I: Application started: jboss-seam-jpa_war [22.1.09 16:34:54:811 SEČ] 00000013 CompositionUn A WSVR0191I: Composition unit WebSphere:cuname=jboss-seam-jpa_war in BLA WebSphere:blaname=jboss-seam-jpa_war started. [22.1.09 16:35:28:731 SEČ] 00000011 SeamFilter I org.jboss.seam.servlet.SeamFilter init Initializing filter: org.jboss.seam.web.ajax4jsfFilter [22.1.09 16:35:28:814 SEČ] 00000011 CacheManager I org.ajax4jsf.cache.CacheManager getCacheFactory Selected [org.ajax4jsf.cache.LRUMapCacheFactory] cache factory [22.1.09 16:46:34:256 SEČ] 0000001c ThreadMonitor W WSVR0605W: Thread "WebContainer : 0" (00000011) has been active for 665558 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung. at org.ajax4jsf.cache.ServletContextInitMap$1.size(ServletContextInitMap.java:78) at java.util.AbstractMap.size(Unknown Source) at java.util.AbstractMap.isEmpty(Unknown Source) at java.util.AbstractMap.toString(Unknown Source) at java.lang.String.valueOf(String.java:1511) at java.lang.StringBuilder.append(StringBuilder.java:191) at org.ajax4jsf.cache.LRUMapCacheFactory.createCache(LRUMapCacheFactory.java:44) at org.ajax4jsf.resource.InternetResourceService.init(InternetResourceService.java:107) at org.ajax4jsf.webapp.BaseFilter.init(BaseFilter.java:188) at org.jboss.seam.web.Ajax4jsfFilter.init(Ajax4jsfFilter.java:82) at org.jboss.seam.servlet.SeamFilter.init(SeamFilter.java:97) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.init(FilterInstanceWrapper.java:140) at com.ibm.ws.webcontainer.filter.WebAppFilterManager._loadFilter(WebAppFilterManager.java:509) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.loadFilter(WebAppFilterManager.java:423) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.getFilterInstanceWrapper(WebAppFilterManager.java:282) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.getFilterChain(WebAppFilterManager.java:340) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:812) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:917) at com.ibm.ws.webcontainer.servlet.FileServletWrapper.handleRequest(FileServletWrapper.java:489) at com.ibm.ws.webcontainer.servlet.StaticFileServletWrapperImpl.handleRequest(StaticFileServletWrapperImpl.java:62) at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:803) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3610) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:274) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:926) at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1557) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:173) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:455) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:384) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:272) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) at com.ibm.io.async.AsyncChannelFuture$1.run(AsyncChannelFuture.java:205) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1527) [22.1.09 17:05:19:388 SEČ] 00000005 ArchiveDeploy W ADMA0142W: Trying to close the archive that is already closed. -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-3570?page=com.atlassian.jira.pl... ] Marek Novotny commented on JBSEAM-3570: --------------------------------------- workaround from RF-4537 is not working for me -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-3570?page=com.atlassian.jira.pl... ] Julien Kronegg commented on JBSEAM-3570: ---------------------------------------- Upgrading to Richfaces 3.3.0.GA also solved the issue with infinite loop in richfaces caching implementation for me. -- 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