Error on first session.Load<>() in Raven 4.0.2

[Kyle Levien]

Working on migrating a 3.x to 4.0 and am getting this error on the first session.Load<> after initializing a DocumentStore:

This stream does not support seek operations.

   at System.Net.ConnectStream.set_Position(Int64 value)

   at Raven.Client.Exceptions.ExceptionDispatcher.<GetJson>d__7.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at Raven.Client.Exceptions.ExceptionDispatcher.<Throw>d__3.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at Raven.Client.Http.RequestExecutor.<HandleUnsuccessfulResponse>d__87`1.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at Raven.Client.Http.RequestExecutor.<ExecuteAsync>d__72`1.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at Raven.Client.Http.RequestExecutor.<ExecuteAsync>d__72`1.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at Raven.Client.Http.RequestExecutor.<UpdateTopologyAsync>d__60.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at Raven.Client.Http.RequestExecutor.<FirstTopologyUpdate>d__67.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at Raven.Client.Util.AsyncHelpers.RunSync(Func`1 task)

   at Raven.Client.Documents.Session.DocumentSession.Load[T](String id)

Could this be related to something with my server setup? I'm running against the default command line server (no auth, port 8080)

Thanks,

Kyle

[Paweł Pekról]

Hi Kyle,

we have encountered this problem with certain thread cultures. The problem was related to the fact that in those cultures (e.g. Swedish) header values were send with invalid characters causing Kestrel to deny processing the request. This should be resolved in 4.0.3-patch-40034. Can you try using this version of client and server?

P.

[Kyle Levien]

I am still seeing the error after upgrading the client and server to 4.0.3-patch-40034
the Thread.CurrentThread.CurrentCulture also looks pretty standard en-US:

[Kyle Levien]

Wait, may have found it. The url it was using was http://localhost/:8080. Fixing that to http://localhost:8080 no longer throws "stream not supported" error, but I do get a new 'Service Unavailable':

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at Raven.Client.Http.RequestExecutor.ThrowFailedToContactAllNodes[TResult](RavenCommand`1 command, HttpRequestMessage request)

   at Raven.Client.Http.RequestExecutor.<ExecuteAsync>d__72`1.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at Raven.Client.Http.RequestExecutor.<ExecuteAsync>d__72`1.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at Raven.Client.Http.RequestExecutor.<UpdateTopologyAsync>d__60.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at Raven.Client.Http.RequestExecutor.<FirstTopologyUpdate>d__67.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at Raven.Client.Util.AsyncHelpers.RunSync(Func`1 task)

   at Raven.Client.Documents.Session.DocumentSession.Load[T](String id)

[Kyle Levien]

Update: running the server as a service (setup-as-service.ps1) looks to be working. Something was just up with running as standard console app.

[Paweł Pekról]

Great to hear that, although I do not recall any differences between those two that could result in such a different behavior. Can you tell us how you were starting the console app (some external script? parameters? run.ps1?).

With regards,

P.

[Oren Eini (Ayende Rahien)]

Most likely reason was permissions issues on the ports?

Hibernating Rhinos Ltd  

Oren Eini l CEO l Mobile: + 972-52-548-6969

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

 

--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.