yeah, it's the completely-separate-webapp bit that's got me weirded out and also what took me down so many fruitless turns
is it also the headless issue that causes all the various applets to pop up and steal focus when I run the integration tests on OS X (typically ingest/purge-related I think)? never saw this under Linux. On 16 Dec 2009, at 12:51 AM, Chris Wilper wrote: > I don't have any leads on why running another webapp alongside > imagemanip would be problematic, but I found this thread relating to > odd server behavior with imagemanip: > > http://n2.nabble.com/A-ImageManipulation-that-kill-my-fedora-daemon-td2826668.html > > It seems odd that getting a new XACML PDP instance would have anything > to do with awt... > > - Chris > > On Tue, Dec 15, 2009 at 5:54 PM, Edwin Shin <[email protected]> wrote: >> background: integration tests that used the imagemanip service were failing >> with fesl (the new, experimental security layer) enabled. >> >> The odd thing was, even requests to: >> >> http://localhost:8080/imagemanip/ImageManipulation?op=resize&newWidth=50&url=http://localhost:8080/tomcat.gif >> would hang/timeout if the fedora webapp had started with fesl enabled was >> running alongside in the same container. >> >> In the ImageManipulation servlet at line 271, it was at JAI.create that >> things would hang. See: >> http://fedora-commons.svn.sourceforge.net/viewvc/fedora-commons/fedora/trunk/fcrepo-webapp/fcrepo-webapp-imagemanip/src/main/java/fedora/localservices/imagemanip/ImageManipulation.java?view=markup >> >> On the fesl side of things, the problem appeared to be with created a new >> com.sun.xacml.PDP instance. See: >> http://fedora-commons.svn.sourceforge.net/viewvc/fedora-commons/fedora/trunk/fcrepo-security/fcrepo-security-pdp/src/main/java/melcoe/xacml/pdp/MelcoePDPImpl.java?view=markup >> >> Commenting out the populatepolicies and instantiation of the PDP instance >> would get imagemanip working again. >> >> After spending entirely too much time trying to run this issue down, I tried >> setting >> System.setProperty("java.awt.headless", "true"); >> in the imagemanip servlet and suddenly imagemanip is working. I'd sort of >> understand if this was happening all the time in the imagemanip servlet >> without headless. But having it only happen when a different webapp is >> running alongside using an unrelated package is just weird. >> >> Anyone ever see something like this or have any insights? >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> Fedora-commons-developers mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers >> ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Fedora-commons-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
