From: <oe...@gm...> - 2012-10-11 19:52:24
|
Are not user and User in the fm namespace? Jens Sent from my HTC ----- Reply message ----- From: "Debra Willrett" <wil...@st...> Date: Thu, Oct 11, 2012 21:22 Subject: [Exist-open] Exist-open Digest, Vol 78, Issue 43 To: <exi...@li...> Cc: "Hakan BULU" <hak...@gm...> Hi, I have eXist installed on localhost and am having problems retrieving information with my query. http://localhost:8080/exist/rest/db/aim.dbxml/?_query=declare namespace fm='gme://caCORE.caCORE/3.2/edu.northwestern.radiology.AIM';for $x in collection('/db/aim.dbxml/')/fm:ImageAnnotation/user/User[@name='dwillrett'] return $x I can match on an attribute in the topmost level, ImageAnnotation, but not anything underneath that. I have attached an xml file. Any suggestions? Thanks. Regards, Debra ----- Original Message ----- From: exi...@li... To: exi...@li... Sent: Thursday, October 11, 2012 11:56:40 AM Subject: Exist-open Digest, Vol 78, Issue 43 Send Exist-open mailing list submissions to exi...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/exist-open or, via email, send a message with subject or body 'help' to exi...@li... You can reach the person managing the list at exi...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of Exist-open digest..." Today's Topics: 1. Re: eXist crashes after large upload! (W.S. Hager) 2. Re: combination of xQuery 3.0 function that stall eXist (christophe geiser) ---------------------------------------------------------------------- Message: 1 Date: Thu, 11 Oct 2012 20:40:37 +0200 From: "W.S. Hager" <ws...@gm...> Subject: Re: [Exist-open] eXist crashes after large upload! To: Casey Jordan <cas...@jo...> Cc: eXist ml <exi...@li...> Message-ID: <CAP8fv=0Px...@ma...> Content-Type: text/plain; charset="iso-8859-1" No it is not a network attack, but the service is unavailable, so let's call it flood protection. Exist can become unavailable when processing hits too hard on the available resources. This may be a user error, but seeing the rare test cases roll by on the list there must be a way to box it in. I'd rather have a portion of the resources unavailable than everything altogether. So I think that is where the main problem with exist lies. If the JVM is too busy processing xslt, the CPU goes awry. Let's say I'd have a way of priorizing plain document reads over querying indexed documents over xquery processing over xslt, there would be a way of guaranteeing critical data being available. Or perhaps all these processes need to be capped somehow. Or perhaps all of them need their own JVM instance. I don't know if any of these measures are taken, I'm just thinking out loud. 2012/10/11 Casey Jordan <cas...@jo...> > The Billion laughs attack is not a network DDOS, it is a done by causing > the processor to go haywire when parsing the XML document, has nothing to > do with Jetty. > > The system should indeed have some method of detecting this, however it > may not be efficient to enable it. > > On Thu, Oct 11, 2012 at 2:06 PM, W.S. Hager <ws...@gm...> wrote: > >> Allow me to sidetrack some more. Isn't jetty supposed to have a ddos >> filter? Is it enabled? >> Somehow I keep getting the idea that the exist architecture is flawed. >> The coupling of the database with the server still feels like a slippery >> slope. Is there another way, I ask myself. >> I'm facing a daily oome of 1.4.3 (a stable release?) and before getting >> excited about 2.0 I'd like to discuss this. So out with it please. >> Op 11 okt. 2012 16:55 schreef "Jens ?stergaard Petersen" < >> oe...@gm...> het volgende: >> >> I am sidetracking the issue, I know, but I tried today to crash eXist >>> with the 1 Billion Laughs <http://en.wikipedia.org/wiki/Billion_laughs>, >>> and got an OOME, but eXist still kept on serving all through my attempts, >>> slowly. >>> >>> What would be the chances of a serious hacker using this to down a >>> server? >>> >>> Jens >>> >>> On Oct 11, 2012, at 4:21 PM, Casey Jordan <cas...@jo...> >>> wrote: >>> >>> Erik, >>> >>> Could you post the relevant parts of your script? We have an upload >>> which works in a similar manner and have had no problems with zip files in >>> the 1-2 GB range. >>> >>> Also, we are running this code on rev 16986, which is about a month >>> back. You may want to try it on that revision to see if it is some type of >>> new regression. >>> >>> Thanks, >>> >>> Casey >>> >>> On Thu, Oct 11, 2012 at 10:04 AM, Erik Siegel <ma...@xa...>wrote: >>> >>>> Hello,**** >>>> >>>> ** ** >>>> >>>> I have an annoying problem. I tried to pin it down. Here is what I did: >>>> **** >>>> >>>> Version: Latest trunk version (5min ago), mem.max 2Gb Stack max 2Mb. >>>> Problem observed on W7 and Ubuntu**** >>>> >>>> ** ** >>>> >>>> **? **I have a form on which I upload a large file (27Mb) >>>> (enctype= |