Hello, thanks for your reply. The tool gives the following info: that fop.jar, batik.jar and xmlgraphics.jar are not unloaded when the AS shuts down. I am using Fop 0.95 so it's Batik 1.7 and xmlgraphics1.3.1. There may be some unclosed streams somewhere: looking at the source code, for instance, you can see that in org.apache.xmlgraphics.util.Service.providers() three streams are not closed. The same method appears in org.apache.batik.util.Service and it does have a finally block. Which of them is used in Fop ? I'd like to rebuild xmlgraphics and see what happens, if I have the time (not that much).
- Pierangelo Jeremias Maerki-2 wrote: > > I don't use Glassfish, so I haven't experienced this. But did that tool > provide some additional information as to why it thinks that fop.jar is > the problem? Maybe that gives us some hints in case we're doing > something wrong somewhere. > > On 09.03.2009 17:12:01 p_repetti wrote: >> >> Hello >> >> I am using FOP 0.95 as embedded in a web application. The WAR gets >> deployed >> into an instance of Sun Java System Application Server(SJSAS) 8.2 on >> Windows >> Vista Business. >> >> When I undeploy/redeploy my WAR, I get a problem with the AS, namely >> >> [#|2009-03-09T15:45:17.164+0000|INFO|sun-appserver-pe8.2|javax.enterprise.system.util|_ThreadID=24;|UTIL6044: >> Error attempting to rename >> C:\Programs\Sun\AppServer\domains\domain1\applications\j2ee-modules\InvoiceNormalizer|#] >> [#|2009-03-09T15:45:17.164+0000|INFO|sun-appserver-pe8.2|javax.enterprise.system.util|_ThreadID=24;|UTIL6041: >> Performing gc to try to force file closures|#] >> [#|2009-03-09T15:45:18.673+0000|INFO|sun-appserver-pe8.2|javax.enterprise.system.util|_ThreadID=24;|UTIL6046: >> Attempt to rename >> C:\Programs\Sun\AppServer\domains\domain1\applications\j2ee-modules\InvoiceNormalizer >> to >> C:\Programs\Sun\AppServer\domains\domain1\applications\j2ee-modules\InvoiceNormalizer_old >> failed after 4 retries|#] >> >> The tool available >> http://blogs.sun.com/quinn/entry/tool_for_diagnosing_failed_glassfish >> here >> directed me to fop.jar. The problem is caused by fop.jar remaining in the >> way after the undeploy. In other words, fop.jar is not getting >> closed/unloaded by the undeploy process and it prevents a fresh redeploy, >> unless you restart the AS. >> >> Has anyone experienced the same problem ? Is there a solution ? >> Thanks >> >> -- >> View this message in context: >> http://www.nabble.com/Glassfish-redeploy-fails%2C-fop.jar-still-loaded-tp22413672p22413672.html >> Sent from the FOP - Users mailing list archive at Nabble.com. >> > > > > Jeremias Maerki > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://www.nabble.com/Glassfish-redeploy-fails%2C-fop.jar-still-loaded-tp22413672p22450654.html Sent from the FOP - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
