Re: [Exist-open] problem with uitl:binary-doc() related to new conf.xml

[Dan M. <dan...@gm...>]

Hi Adam,

Thank makes sense.  I will try to be more careful when I upgrade in the
future.

- Dan

On Tue, Aug 28, 2012 at 5:04 PM, Adam Retter <ad...@ex...> wrote:

> The problem you had was cause by missing this bit:
>
> <binary-manager>
>    <cache class="org.exist.util.io.FileFilterInputStreamCache"/>
> </binary-manager>
>
> I made the cache class configurable, because different people wanted
> different things. Without that information, we try to load an unknown
> class, which doesnt exist.
>
>
> On 28 August 2012 19:10, Dan McCreary <dan...@gm...> wrote:
> > To be quite honest, the changes don't seem to be related to the util
> module
> > at all or the util:binary-doc() function.  I suspect that the
> > "binary-manager"
> > changes are what might be related but it is only a guess.  Here is what
> the
> > differences were:
> >
> > $ diff conf-old.xml conf.xml
> > 11a12,13
> >>                 startup
> >>                     trigger
> > 15a18
> >>             binary-manager
> > 51c54
> > <     Version: 2.0-tech-preview-rev:0000-20120210
> > ---
> >>     Version: 2.1-dev-rev:0000-20120828
> > 53c56
> > <     $Id: conf.xml.tmpl 15780 2012-02-02 10:42:50Z wolfgang_m $
> > ---
> >>     $Id: conf.xml.tmpl 16993 2012-08-22 15:22:26Z wolfgang_m $
> > 151a155,162
> >>       <!-- EXQuery RESTXQ trigger to load the RESTXQ Registry at startup
> >> time -->
> >>       <startup>
> >>               <triggers>
> >>                       <trigger
> >> class="org.exist.extensions.exquery.restxq.impl.RestXqStartupTrigger"/>
> >>               </triggers>
> >>       </startup>
> >>
> >>
> > 296a308,336
> >>     <!--
> >>         Settings for the Binary Manager:
> >>
> >>         - cache
> >>             Defines the class to use to Cache InputStreams when reading
> >> binary documents
> >>             from the database or from a read once source such as a http
> >> request (e.g. request:get-data()).
> >>             There are currently three options available:
> >>
> >>             - org.exist.util.io.FileFilterInputStreamCache
> >>                 Default. Temporary binary streams are cached to a
> >> temporary file on disk.
> >>
> >>             - org.exist.util.io.MemoryMappedFileFilterInputStreamCache
> >>                 Temporary binary streams are cached to a temporary file
> on
> >> disk which
> >>                 has been mapped into memory. Faster than
> >> FileFilterInputStreamCache.
> >>                 Not reliable on Windows platforms.
> >>
> >>             - org.exist.util.io.MemoryFilterInputStreamCache
> >>                 Temporary binary streams are cached in memory.
> >>                 This is the fastest approach. However it can result in
> out
> >> of memory
> >>                 errors under heavy load or if using large binary files.
> >>
> >>            Where temporary files are used, they will be deleted after
> use.
> >>            However, due to a bug in the JVM on Windows platforms,
> >> temporary files cannot be deleted, so instead
> >>            they are re-cycled and re-used and deleted if the database is
> >> restarted.
> >>     -->
> >>     <binary-manager>
> >>         <cache class="org.exist.util.io.FileFilterInputStreamCache"/>
> >>     </binary-manager>
> >>
> > 546a587,594
> >>       <!--
> >>               You may add as many custom-filters as you want, they will
> be
> >> executed
> >>               in the order you specify them. Thus:
> >>
> >>               <custom-filter class="org.exist.FirstFilter"/>
> >>               <custom-filter class="org.exist.SecondFilter"/>
> >>         -->
> >>
> > 677c725
> > <
> > ---
> >>                       <module
> >> uri="http://www.w3.org/2005/xpath-functions/map"
> >> class="org.exist.xquery.functions.map.MapModule" />
> > 701a750,753
> >>             <!-- EXQuery Modules -->
> >>             <!-- RESTXQ -->
> >>             <module uri="http://exquery.org/ns/rest/annotation/"
> >> class="org.exist.extensions.exquery.restxq.impl.xquery.RestXqModule"/>
> >>
> > 748a801
> >>
> > 752c805,807
> > < <!-- added by DGM -->
> > ---
> >> <module uri="http://exist-db.org/xquery/scheduler"
> >> class="org.exist.xquery.modules.scheduler.SchedulerModule" />
> >> <module uri="http://exist-db.org/xquery/math"
> >> class="org.exist.xquery.modules.math.MathModule" />
> >> <module uri="http://exist-db.org/xquery/datetime"
> >> class="org.exist.xquery.modules.datetime.DateTimeModule" />
> > 753a809
> >> <module uri="http://expath.org/ns/ft-client"
> >> class="org.expath.exist.ftclient.ExistExpathFTClientModule" />
> > 755,760d810
> > < <!--
> > <    <module uri="http://exist-db.org/xquery/scheduler"
> > class="org.exist.xquery.modules.scheduler.SchedulerModule" />
> > <    <module uri="http://exist-db.org/xquery/datetime"
> > class="org.exist.xquery.modules.datetime.DateTimeModule" />
> > <    <module uri="http://exist-db.org/xquery/math"
> > class="org.exist.xquery.modules.math.MathModule" />
> > <    <module uri="http://expath.org/ns/ft-client"
> > class="org.expath.exist.ftclient.ExistExpathFTClientModule" />
> > < -->
> > 762d811
> > <
> > 769a819,820
> >>             <module uri="http://exist-db.org/xquery/cqlparser"
> >> class="org.exist.xquery.modules.cqlparser.CQLParserModule" />
> >>             <module uri="http://exist-db.org/xquery/datetime"
> >> class="org.exist.xquery.modules.datetime.DateTimeModule" />
> > 776a828
> >>             <module uri="http://exist-db.org/xquery/math"
> >> class="org.exist.xquery.modules.math.MathModule" />
> > 778a831
> >>             <module uri="http://exist-db.org/xquery/scheduler"
> >> class="org.exist.xquery.modules.scheduler.SchedulerModule" />
> > 788c841
> > <             <!--
> > ---
> >>             <!--
> > 792a846
> >>                 -
> >> org.exist.xquery.modules.xslfo.AntennaHouseProcessorAdapter for
> AntennaHouse
> >> Formatter
> > 794d847
> > <             <!--
> > 798d850
> > <             -->
> >
> >
> >
> > On Tue, Aug 28, 2012 at 12:55 PM, Joe Wicentowski <jo...@gm...>
> wrote:
> >>
> >> Hi Dan,
> >>
> >> > After going through and doing diffs of the configuration files we
> found
> >> > there was a change in the conf.xml file in the newest version that I
> did
> >> > not
> >> > see when I did the diff.  By updating the conf.xml file to the new
> >> > format
> >> > and then merging my customization back in we got things working again.
> >>
> >> Glad to hear you've got things working.
> >>
> >> I'm curious - what was the change in conf.xml that was related to
> >> this?  And were you able to track down which revision introduced the
> >> change to conf.xml?  This info might be helpful for others who
> >> encounter this problem.
> >>
> >> Thanks,
> >> Joe
> >
> >
> >
> >
> > --
> > Dan McCreary
> > NoSQL Evangelist
> > office: (952) 931-9198
> > cell: (612) 986-1552
> >
> >
> ------------------------------------------------------------------------------
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > _______________________________________________
> > Exist-open mailing list
> > Exi...@li...
> > https://lists.sourceforge.net/lists/listinfo/exist-open
> >
>
>
>
> --
> Adam Retter
>
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb
>



-- 
Dan McCreary
NoSQL Evangelist
office: (952) 931-9198
cell: (612) 986-1552