[Mulgara-dev] TransactionalAnswer not closed
Paul Gearon
gearon at ieee.org
Thu Feb 1 22:52:31 UTC 2007
Actually, I don't know how to talk to Mulgara with SOAP (I also thought that
Simon said that the SOAP interface isn't working 100% at the moment?).
Could you send me a code snippet so I can see how it is done? I may be able
to spot something.
If it turns out that this is not possible, then there may be a way to adjust
the interface to work for us. (Perhaps we automatically close sub-answers
after encoding to SOAP?)
Regards,
Paul
On 2/1/07, David Moll <DMoll at viewpointusa.com> wrote:
>
> I do recall the discussion regarding whether or not to automatically
> close answers.
>
>
>
> So my question would be – how is this handled over the SOAP interface?
> I'm sending the full query as a string with the "executeQueryToString" as an
> XML request via the SOAP interface.
>
>
>
> We generated a class ItqlInterpreterBeanService that extends the .NET 2.0
> System.Web.Services.Protocols.SoapHttpClientProtocol. The query is
> actually sent via:
>
>
>
> object[] results = this.Invoke("executeQueryToString", new object[]
> {queryString});
>
>
>
> Now, Invoke is a synchronous call, so there is no need to explicitly end
> it. I could use the BeginInvoke and EndInvoke methods to begin and end an
> asynchronous XML request, but I don't imagine that it would solve the
> problem of closing the answers.
>
>
>
> It doesn't appear that there is a method exposed to the SOAP interface on
> Mulgara that would allow me to close the sub-answers.
>
>
>
> Since the only way that we talk to Mulgara is via SOAP, I'm not sure how
> to close the answers.
>
>
>
> Hopefully that made sense.
>
>
>
> ~dave
> ------------------------------
>
> *From:* gearon at gmail.com [mailto:gearon at gmail.com] *On Behalf Of *Paul
> Gearon
> *Sent:* Thursday, February 01, 2007 5:05 PM
> *To:* David Moll
> *Cc:* mulgara-dev at mulgara.org
> *Subject:* Re: [Mulgara-dev] TransactionalAnswer not closed
>
>
>
> Hi David,
> Did you know that you have to close the sub-answers as well as the parent
> answer?
>
> We considered closing the sub-answers automatically, but this is
> problematic. When do we close them? After you've seen them once? What if
> you rewind and look at them again? When the main Answer is closed? But
> that means rewinding, and iterating over a potentially huge list (for a
> second time, since you've already been through your answers once).
>
> The cleanest and best performing way is to close the sub-answers yourself
> once you've finished with them.
>
> The reason your warnings are not repeatable is because these messages are
> being triggered when the garbage collector sees that they are no longer in
> use and closes them for you. Incidentally, the sub answers are holding onto
> old phases, and this may be the cause of the "massive file" you were asking
> about last week.
>
> Regards,
> Paul Gearon
>
> On 2/1/07, *David Moll* <DMoll at viewpointusa.com> wrote:
>
> Gentlemen,
>
>
>
> I am bringing more questions and problems to you!
>
>
>
> I've been getting the following error several times while doing testing to
> try and find more date/time errors.
>
>
>
> I set up queries to get information about the first 100 "tests" in Mulgara
> (using limit 100 on the query), checking the information, and then deleting
> those triples. I can't grab all the information because the resulting XML
> is too large to be passed back via SOAP and it times out. Intermittently
> the Mulgara console will toss out:
>
>
>
> ;
>
> 2007-02-01 16:10:24,700 WARN TransactionalAnswer - TransactionalAnswer
> not clos
>
> ed
>
> 2007-02-01 16:10:24,700 WARN TransactionalAnswer - TransactionalAnswer
> not clos
>
> ed
>
> 2007-02-01 16:10:24,716 WARN TransactionalAnswer - TransactionalAnswer
> not clos
>
> ed
>
> 2007-02-01 16:10:24,716 WARN TransactionalAnswer - TransactionalAnswer
> not clos
>
> ed
>
> 2007-02-01 16:10:24,716 WARN TransactionalAnswer - TransactionalAnswer
> not clos
>
> ed
>
> 2007-02-01 16:10:24,716 WARN TransactionalAnswer - TransactionalAnswer
> not clos
>
> ed
>
>
>
> but this is not repeatable or predictable. Any thoughts as to what is
> happening?
>
>
>
> The query I am running to retrieve 100 tests to verify is:
>
>
>
> select $test subquery(
>
> select $p $o
>
> from <rmi://192.168.10.205/server1#datetest> where $test $p
> $o
>
> )
>
> from <rmi://192.168.10.205/server1#datetest>
>
> where $test <http://www.w3.org/1999/02/22-rdf-syntax-ns#type>
>
> <http://www.viewpointusa.com/vss/fm/elements/1.0/localFile>
>
> limit 100;
>
>
>
> And to delete the triples:
>
>
>
> delete (select $test $p $o
>
> from <rmi://192.168.10.205/server1#datetest>
>
> where $test $p $o and
>
> $test <http://www.w3.org/1999/02/22-rdf-syntax-ns#type>
>
> <http://www.viewpointusa.com/vss/fm/elements/1.0/localFile>
>
> limit 600) from <rmi://192.168.10.205/server1#datetest>;
>
>
>
> Limit 600 on the select for the delete because each test is the subject of
> 6 triples, and doing a delete with a subquery caused issues.
> *~Dave*
>
>
> _______________________________________________
> Mulgara-dev mailing list
> Mulgara-dev at mulgara.org
> http://mulgara.org/mailman/listinfo/mulgara-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mulgara.org/pipermail/mulgara-dev/attachments/20070201/40810969/attachment.htm>
More information about the Mulgara-dev
mailing list