You say in the other thread that oomkiller took out couchdb, which would
obviously stop it from sending more data. The TCP socket should close, though,
and you should be able to detect that.
I think you have http/1.0 and 1.1 confused. A 1.0 connection is supposed to
always close after the resp
I don't think this is the case, here's why... If the process
receiving the data died due to lack of resources, I don't think my php
script would continue running and then try to parse the JSON into a
PHP object. Most likely it would just die. I haven't had a chance
yet, but I should try a few ot
The package from Erlang Solutions repository is built with wxwidgets and
java connectivity and that's why the package requires x11-common and
java-common. For CouchDB neither of them is necessary.
CGS
On Sun, Aug 19, 2012 at 7:18 PM, Tim Tisdall wrote:
> That's strange... I'm using erlang-d
Robert, inject a very large number docs in a database and try to access
_all_docs with a browser (the behavior is similar in a Linux terminal by
injecting the cURL output in an environment variable and, I suppose, in
every OS). You will see that the browser crashes (or becomes unresponsive)
when th
That's strange... I'm using erlang-dev from the Debian 6 repository.
I see that there's a debian repository run by erlang-solutions.com but
it's in a different format than the main Debian repository. If I try
to install "erlang" from the main repository or "esl-erlang" from the
erlang-solutions r
Tim, what are you using as scripting language to retrieve the CouchDB
response?
On Sun, Aug 19, 2012 at 2:17 PM, Tim Tisdall wrote:
> Does the Mochiweb server have separate logs from couch? If not, then
> there was nothing in the logs.
>
> - Original message -
> >
> > On Aug 18, 2012, a
Does the Mochiweb server have separate logs from couch? If not, then there was
nothing in the logs.
- Original message -
>
> On Aug 18, 2012, at 4:46 PM, Tim Tisdall wrote:
>
> > I have a script where I query a view for multiple entries of data.
> > I'm doing it in batches of 1000.
A full view response should always be valid JSON, so that does point towards a
bug in CouchDB assuming the response output you posted is verbatim what CouchDB
returned. Can you reproduce this reliably?
Oh, and unrelated to the bug itself, but R14A is a beta release, you should
upgrade.
B.
O
I don't suppose the problem is coming from CouchDB, but from your external
environment which has a limited number of characters per line, truncating
the message if more. It happened to me in few occasions (Linux terminal
truncated my message because it was single line - line end was translated
as "
On Aug 18, 2012, at 4:46 PM, Tim Tisdall wrote:
> I have a script where I query a view for multiple entries of data.
> I'm doing it in batches of 1000. It works fine multiple times and
> then suddenly it returns a result that doesn't properly parse as JSON
> because it's missing some content at
I have a script where I query a view for multiple entries of data.
I'm doing it in batches of 1000. It works fine multiple times and
then suddenly it returns a result that doesn't properly parse as JSON
because it's missing some content at the end (not sure how much, but
it's at least missing the
11 matches
Mail list logo
