The reason that I assumed that the error was related more to memory limitations was the pattern that it seemed to follow. Although there seems to be a problem with quick, successive queries, the error is also given after very general queries with large result sets such as "person" and "live."
Concerning Joost's comment, the line, column, byte triplet of the error are dependent upon the query. For example, the error returned for "person" is ". . . (invalid token) at line 1449, column 38, byte 61239 at C:/Perl/lib/XML/Parser.pm line 187," while a query for "live" returns ". . . at line 516, column 31, byte 22317 at C:/Perl/lib/XML/Parser.pm line 187." What may be more useful is that the error occurs on line 187 of the XML::Parser module.
Is it more likely that what I've thought to be a memory error has more to do with the data sent from the XML-RPC server itself? If this is the case, would the implementation of XML::Smart within Frontier::Client solve the problem?
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|