Query Error: Could not find field [JobId] on model [LsJob]

Hi,

Am getting a random error in a multi threaded service, where LightSpeed can't find it's own metadata on the model, occurring about 1% of the time. 99% it's ok, so it seems to be a threading issue.

A new UnitOfWork is being created per Find() call (hence per thread), so is LightSpeed fully thread safe?

Version 2.2.948.10429 of Mindscape.Lightspeed.dll

Andrew

<exception type="Mindscape.LightSpeed.LightSpeedException">
<message>Query Error: Could not find field [JobId] on model [LsJob]</message>
<source>Mindscape.LightSpeed</source>
<stackTrace>
at Mindscape.LightSpeed.LightSpeedException.&#x11;(Exception , String , Object[] )    
at &#x4;.&#x7;.&#x11;(String )    
at &#x4;.&#x7;.&#x11;(IdentifierExpression )    
at Mindscape.LightSpeed.Querying.IdentifierExpression.&#x11;[T](&#x6; )    
at &#x4;.&#x7;.&#x11;(PredicateExpression )    
at Mindscape.LightSpeed.Querying.PredicateExpression.&#x11;[T](&#x6; )    
at &#x4;.&#x7;.&#x12;(TypeModel , QueryExpression , Order , String , Boolean , Boolean )    
at &#x4;.&#x5;.&#x11;(TypeModel , QueryExpression , Order , String , Boolean , Boolean )    
at &#x4;.&#x7;.&#x11;(TypeModel , Query , String , String )    
at &#x8;.&#x7;.&#x11;(TypeModel , Query , IList )    
at &#x3;.&#x8;.&#x11;(Query , TypeModel , IList )    
at &#x3;.&#x8;.&#x11;(Query , IList )    
at Mindscape.LightSpeed.UnitOfWork.Find(Query query, IList results)    
at Mindscape.LightSpeed.UnitOfWorkBase.Find(Query query)    
at Mindscape.LightSpeed.UnitOfWork.FindOne(Query query)    
at Mindscape.LightSpeed.UnitOfWorkBase.FindOne[TEntity](Query query)    
at Mindscape.LightSpeed.UnitOfWorkBase.FindOne[TEntity](QueryExpression queryExpression)    
at [...]Repositories.LsJobRepository.Find(Guid jobId)

Found the change log stating threading issues fixed, trying a much newer version.

Hi Andrew,

Sorry for the delayed response - as you noted we did some work on this in subsequent builds and this should not be a problem but please let us know if this is still an issue for you and we can look in to it.

Jeremy