livedomain Issue Tracker Rss Feed

Edited Issue: Log files created by default in application path [2488]

rofr — Sun, 25 Nov 2012 00:28:27 GMT

NLog creates log files in the current working directory. When running in a web context this is the IIS system directory, not the application virtual directory, resulting in an access denied exception. This will be fixed in the next release. Workaround #1 Configure logging to use the a specified directory: Log.SetLogFactory(new SingletonLogFactory(new FileLogger("path to log"))); Workaround #2 Disable logging by setting a null logger: Log.SetLogFactory(new SingletonLogFactory(new NullLogger()));

Created Issue: Log files created by default in application path [2488]

rofr — Sun, 25 Nov 2012 00:24:51 GMT

NLog creates log files in the current working directory. When running in a web context this is the IIS system directory, not the application virtual directory, resulting in an access denied exception

Edited Issue: Enterprise.Client serialization exception [2485]

rofr — Fri, 10 Aug 2012 14:00:31 GMT

Reopened Issue: Enterprise.Client serialization exception [2485]

rofr — Fri, 10 Aug 2012 14:00:16 GMT

Closed Issue: Enterprise.Client serialization exception [2485]

rofr — Fri, 10 Aug 2012 13:02:54 GMT

Commented Issue: Enterprise.Client serialization exception [2485]

rofr — Fri, 10 Aug 2012 13:02:33 GMT

When the engine throws a CommandFailedException on the server side, the client is unable to deserialize it. The exception message is:

The constructor to deserialize an object of type 'LiveDomain.Core.CommandFailedException' was not found."}
Comments: When deriving from a class which implements ISerializable, a special constructor must be added that takes SerializationInfo and StreamingContext parameters. Fixed in release 0.4.1

Edited Issue: Server crashes when client connection is lost [2487]

WooCode — Mon, 11 Jun 2012 12:56:44 GMT

Running the TODO sample client console application, the client requested todo items for a list that didnt exist. The client threw an exception and so did the server.
Unhandled Exception: System.IO.IOException: Unable to write data to the transpor
t connection: An established connection was aborted by the software in your host
machine. ---> System.Net.Sockets.SocketException: An established connection was
aborted by the software in your host machine
at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, So
cketFlags socketFlags)
at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32
size)
--- End of inner exception stack trace ---
at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32
size)
at System.IO.BinaryWriter.Write(Int32 value)
at System.Runtime.Serialization.Formatters.Binary.SerializationHeaderRecord.W
rite(__BinaryWriter sout)
at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.WriteSerialize
dStreamHeader(Int64 topId, Int64 headerId)
at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Obje
ct graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(S
tream serializationStream, Object graph, Header[] headers, Boolean fCheck)
at LiveDomain.Enterprise.Networking.Server.StandaloneServer.HandleRequest(Obj
ect state)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object sta
te)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, C
ontextCallback callback, Object state, Boolean ignoreSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWor
kItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

Edited Issue: Server throws NullReferenceException on exit [2486]

WooCode — Mon, 11 Jun 2012 08:17:45 GMT

When shutting down server (typing exit on the console), an unhandled exception is thrown. The error message is:

Unhandled Exception: System.NullReferenceException: Object reference not set to
an instance of an object.
at LiveDomain.Enterprise.Networking.Server.StandaloneServer.Stop(Boolean clos
eEngine)
at LiveDomain.Enterprise.Server.Program.Run(EnterpriseConfiguration config)
at LiveDomain.Enterprise.Server.Program.Main(String[] args)

Created Issue: Server crashes when client connection is lost [2487]

rofr — Fri, 08 Jun 2012 21:10:32 GMT

Created Issue: Server throws NullReferenceException on exit [2486]

rofr — Fri, 08 Jun 2012 17:20:52 GMT

Created Issue: Enterprise.Client serialization exception [2485]

rofr — Fri, 08 Jun 2012 17:18:35 GMT

Created Feature: CloneResults and write to journal in parallel [2484]

rofr — Tue, 28 Feb 2012 16:28:20 GMT

After a command is executed, it's return value is cloned and the command itself is written to the command journal. These operations are independent of each other, possibly lengthy and thus can be executed in parallel.

Created Feature: Downgrade lock after command execute [2483]

rofr — Tue, 28 Feb 2012 16:25:19 GMT

After a command executes its results are cloned. This can be time consuming compared to the actual command execution and could be performed using only a read lock.

Closed Issue: Bug in CreateOrLoad [2358]

rofr — Mon, 27 Feb 2012 09:45:47 GMT

Engine.LoadOrCreate works with load but not create
Comments:

Fixed in version 0.4.0, available on nuget

Closed Issue: Wrong default location in web context [2377]

rofr — Mon, 27 Feb 2012 09:44:52 GMT

Default location when running in a web context is not ~/App_Data as documented.
Comments:

Fixed in version 0.4.0, available on nuget

Closed Issue: Unable to query LiveDb with LINQ [2474]

rofr — Mon, 27 Feb 2012 09:42:50 GMT

I am receiving an error about serializing a Where statement when attempting to query LiveDb.

I am using a syntax similar to: engine.Execute(m => m.Jobs.Where(j => j.JobId == 5)).First();

See the full code with unit test at:
https://gist.github.com/32d24b9222cc5c019c51
Comments:

This is a very common mistake. LINQ uses deferred execution so you need to force evaluation within your execute method.

All query and command results are cloned (deep copy using serialization) so result types must be marked Serializable. This is to prevent read or write access to the model not performed from a query or command.

Cloning can be disabled by setting EngineConfiguration.CloneResults to false.

However, the error message could be more clear on this point.

Commented Issue: Unable to query LiveDb with LINQ [2474]

jfritz — Sat, 25 Feb 2012 21:35:14 GMT

I've moved the First() predicate inside the Execute command and this now executes properly.

You may mark this as Resolved.

Commented Issue: Unable to query LiveDb with LINQ [2474]

jfritz — Sat, 25 Feb 2012 21:21:33 GMT

My error stack looks from this query looks like:

System.Runtime.Serialization.SerializationException : Type 'System.Linq.Enumerable+WhereListIterator`1[[SPIKE.Aesop.Disruptor.Data.Job, SPIKE.Aesop.Disruptor, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null]]' in Assembly 'System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' is not marked as serializable.
at System.Runtime.Serialization.FormatterServices.InternalGetSerializableMembers(RuntimeType type)
at System.Runtime.Serialization.FormatterServices.GetSerializableMembers(Type type, StreamingContext context)
at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitMemberInfo()
at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter, SerializationBinder binder)
at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.Serialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter, SerializationBinder binder)
at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph, Header[] headers, Boolean fCheck)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph)
at LiveDomain.Core.Serializer.Serialize(Object graph)
at LiveDomain.Core.Serializer.Clone[T](T graph)
at LiveDomain.Core.Engine.Execute[M,T](Func`2 query)
at LiveDomain.Core.Engine`1.Execute[T](Func`2 query)

Created Issue: Unable to query LiveDb with LINQ [2474]

jfritz — Sat, 25 Feb 2012 21:18:38 GMT

Commented Issue: Serialization exceptions [2359]

rofr — Tue, 22 Nov 2011 21:47:34 GMT

Engine does not handle serialization erros when serializing a graph containing types not marked with a Serializable attribute.
Comments: ** Comment from web user: rofr **

Now, commands are cloned before being executed and journaled. Serialization exceptions will be caught early and wont corrupt the command log.