I've read the comments for this issue. May I assume that the Trinidad fixes will be in the 1.0.9/1.2.9 release?
Thank you, Ed On 5/27/08, Thomas Jacob (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/TRINIDAD-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600099#action_12600099 > ] > > Thomas Jacob commented on TRINIDAD-73: > -------------------------------------- > > ... I have set a breakpoint in the errorneous JDK method, and > unfortunatelly, the method is still getting called. Now by MyFaces... I fear > the story continues... > >> trinidad-impl.jar file is left open during execution >> ---------------------------------------------------- >> >> Key: TRINIDAD-73 >> URL: https://issues.apache.org/jira/browse/TRINIDAD-73 >> Project: MyFaces Trinidad >> Issue Type: Bug >> Affects Versions: 1.0.1-core >> Reporter: Adam Winer >> Fix For: 1.0.2-core >> >> Attachments: AggregatingResourceLoader-patch-on-547038.txt, >> CachingResourceLoader-patch-on-549615.txt, >> ProxyResourceLoader-patch-on-518820.txt, >> ResourceServlet-patch-on-549620.txt, >> URLInputStreamProvider-patch-on-549615.txt, URLUtils-patch-on-660215.txt, >> URLUtils.java >> >> >> When running a Trinidad application, trinidad-impl.jar is getting locked >> with open FileInputStream objects. When GC occurs, the FileInputStreams >> are getting cleared, but as new FileInputStreams are opened on each >> request, the file is eternally locked. Other files are likely getting >> locked too. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >
