Thank you Ayende. I noticed that when i access to Raven from only one
thread - everything is okay. But when i access from multiple threads
simultaneously i see the following in the console of RavenDB:
Request # 209: GET - 86 ms - 404 - /docs/Raven/Replication/
Destinations
Request # 210: GET - 23 ms - 404 - /docs/Raven/Replication/
Destinations
Request # 211: GET - 1 ms - 404 - /docs/Raven/Replication/
Destinations
Requests sent almost at the same time. I use one DocumentStore with
container lifetime (singleton) and i create DocumentSession in every
thread.
Yes it happens consistently for me, but only with the first set of
requests (which are sent simultaneously). After raven got info about
destination all subsequent simultaneous requests are handled without
exception.
Actually i'm using nservicebus and send requests to raven in message
handlers - should i work to reproduce this problem without NServiceBus
before asking your help? (just in case information i provided is not
enough to explain the problem i faced)
On Oct 10, 7:50 pm, Ayende Rahien <
aye...@ayende.com> wrote:
> Rationalle,
> The client API will check if you setup replication on the server every 5
> minutes or so.
> There isn't a way to turn that off.
> However, you shouldn't see the bug report.
> Does it happen consistently?
>
>
>
> On Sun, Oct 10, 2010 at 6:32 PM, Rationalle <
rationa...@gmail.com> wrote:
> > My test project which use Raven sends first request to /docs/Raven/
> > Replication/Destinations. Raven reply with 404. And i see the
> > following error in console of my project (no errors in Raven.Server
> > console):
>
> > BUG: Could not find failure count forhttp://localhost:8086