[ https://issues.jboss.org/browse/AS7-4018?page=com.atlassian.jira.plugin.s... ] David Lloyd updated AS7-4018: ----------------------------- Fix Version/s: 7.1.2.Final Priority: Critical (was: Major) Assignee: Stan Silvert Component/s: JSF Forum Reference: https://community.jboss.org/message/721289#721289 (was: https://community.jboss.org/message/721289#721289) -- 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

[ https://issues.jboss.org/browse/AS7-4018?page=com.atlassian.jira.plugin.s... ] Stuart Douglas commented on AS7-4018: ------------------------------------- Is there ant chance it could be this: http://java.net/jira/browse/JAVASERVERFACES-2113 It looks like this fix is part of AS7 upstream, but did not make it into 7.1.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

[ https://issues.jboss.org/browse/AS7-4018?page=com.atlassian.jira.plugin.s... ] Stuart Douglas commented on AS7-4018: ------------------------------------- It might be easier to just build AS 7.1.1 upstream from source, which should have this fix already. -- 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

[ https://issues.jboss.org/browse/AS7-4018?page=com.atlassian.jira.plugin.s... ] Stuart Douglas commented on AS7-4018: ------------------------------------- yes, you should be able to build it by simply running build.sh -- 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

[ https://issues.jboss.org/browse/AS7-4018?page=com.atlassian.jira.plugin.s... ] Stan Silvert commented on AS7-4018: ----------------------------------- Hi Cody, Can you check to see if the file is released when the session expires? You can set session timeout down to 1 minutes in web.xml. <session-config> <session-timeout>1</session-timeout> </session-config> Stan -- 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

[ https://issues.jboss.org/browse/AS7-4018?page=com.atlassian.jira.plugin.s... ] Stan Silvert commented on AS7-4018: ----------------------------------- Hi Cody, I haven't been able to reproduce this. If I understand correctly, I should see a new file handle for jsf-impl-2.1.7-jbossorg-2.jar every time I create a new session. However, I only see one instance of this handle. I am running on Windows, which might make a difference. Can others verify this behavior on other OS's? -- 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

[ https://issues.jboss.org/browse/AS7-4018?page=com.atlassian.jira.plugin.s... ] Stan Silvert updated AS7-4018: ------------------------------ Priority: Major (was: Critical) Forum Reference: https://community.jboss.org/message/721289#721289 (was: https://community.jboss.org/message/721289#721289) Downgrading the priority as it's no longer critical. This will most likely need to be resolved in Mojarra anyway. -- 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

[ https://issues.jboss.org/browse/AS7-4018?page=com.atlassian.jira.plugin.s... ] Stan Silvert commented on AS7-4018: ----------------------------------- What have you done so far to narrow the problem down? Have you tried it with different JSF applications? Have you tried it on a different OS? I do think we need to report this to Mojarra but we need to narrow it down as much as possible. Unfortunately I can't be much help with that because I've been unable to reproduce the problem on my end. Stan -- 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

[ https://issues.jboss.org/browse/AS7-4018?page=com.atlassian.jira.plugin.s... ] Nicklas Karlsson commented on AS7-4018: --------------------------------------- Is it only the jsf jar? I noticed a general trend in AS7-2939 -- 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

[ https://issues.jboss.org/browse/AS7-4018?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on AS7-4018: ----------------------------------- If you have the heap.bin still, look at input/output streams. If I remember correctly, calling close on each stream will close the underlying file (immediately). When someone forgets to call close on the stream, the file will stay open until the stream is GCd (that is what I have seen in the past). [http://www.eclipse.org/mat/] can be used to examine the heap dump file. A few years ago, I found it helpful to find file leaks by instrumenting the FileInputStream/FileOutputStream class. In the FileInputStream/FileOutputStream constuctors created a new Exception and saved it in a class instance variable. Then, in the finalize method, if the stream didn't get closed, called printStackTrace() on the exception created in the constructor (showing the origin of the code that caused the leak). Perhaps you could find a [Byteman|http://www.jboss.org/byteman] way to do that. :) -- 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

[ https://issues.jboss.org/browse/AS7-4018?page=com.atlassian.jira.plugin.s... ] Cody Lerum edited comment on AS7-4018 at 3/23/12 7:53 PM: ---------------------------------------------------------- by changing my vm options to "-XX:+UseConcMarkSweepGC -XX:+ExplicitGCInvokesConcurrent -verbosegc" The files are now cleaned up much more frequently and I'm never going above 20 I'm thinking with my large heap -Xms3072m -Xmx3072m + -XX:-DisableExplicitGC + G1GC and a pretty quiet application the vm could avoid doing a full gc for days or weeks. Thus these references could just sit without being cleaned up. I'm guessing there is an underlying problem though with something not closing these streams. All I can find is that these are open streams with references to java.lang.ref.Finalizer was (Author: clerum): by changing my vm options to "-XX:+UseConcMarkSweepGC -XX:+ExplicitGCInvokesConcurrent -verbosegc" The files are now cleaned up much more frequently and I'm never going above 20 I'm thinking with my large heap -Xms3072m -Xmx3072m + -XX:-DisableExplicitGC + G1GC and a pretty quiet application the vm could avoid doing a gc for days or weeks. Thus these references could just sit without being cleaned up. I'm guessing there is an underlying problem though with something not closing these streams. All I can find is that these are open streams with references to java.lang.ref.Finalizer -- 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

[ https://issues.jboss.org/browse/AS7-4018?page=com.atlassian.jira.plugin.s... ] Stuart Douglas commented on AS7-4018: ------------------------------------- A good way to debug this would be to set a logging breakpoint in java.io.FileInputStream#FileInputStream, and every time the jsf-impl file is opened log the complete stack trace to the console. This should make it easy to identify where these files are coming from. -- 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

[ https://issues.jboss.org/browse/AS7-4018?page=com.atlassian.jira.plugin.s... ] Stan Silvert reassigned AS7-4018: --------------------------------- Assignee: (was: Stan Silvert) Unassigning for now. Feel free to reassign to me if something comes up that I need to look at. -- 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