Quantcast
Viewing all articles
Browse latest Browse all 240675

Re: .net native client crashes

Thanks for looking into the dumps, hiteshk.

 

You must be referring to the two CO1-*.dmp files, as only the consumers call RegisterRegex.

 

The strange thing is however, that in the one case I checked (CO1-gemfire_nativeclient-1362994468-1364.dmp, and I assume the same is true for the other crash), there was no exception during RegisterRegex, at least not in .net land. Check the following log snippet:

 

Registering interest in regex CO1-269-.*
Called GemFire Function 'IAmReady'

 

which corresponds to the following code, the only one calling RegisterRegex:

 

String registerInterestRegex = sessionId + "-.*";
Console.WriteLine("Registering interest in regex " + registerInterestRegex);
myRegion.GetSubscriptionService()
  .RegisterRegex(registerInterestRegex);

execution.Execute("IAmReady");
Console.WriteLine("Called GemFire Function 'IAmReady'");

 

In this particular case (still CO1-gemfire_nativeclient-1362994468-1364.dmp), the AccessViolationException was immediately preceded by another exception:

 

[warning 2013/03/11 18:34:28.232356 東京 (標準時) MACHINE23:1364 2648] Error during send for endpoint MACHINE12:40401 due to gemfire::OutOfRangeException: DataInput: attempt to read beyond buffer:

   場所 GemStone.GemFire.Cache.Generic.DataInput.CheckBufferSize(Int32 size)
   場所 GemStone.GemFire.Cache.Generic.Internal.PdxType.FromData(DataInput input)
   場所 gemfire.ManagedCacheableKeyGeneric.fromData(ManagedCacheableKeyGeneric*, DataInput* input)
[warning 2013/03/11 18:34:28.232356 東京 (標準時) MACHINE23:1364 2648] Stack trace:   No stack available.
ハンドルされていない例外: System.AccessViolationException: 保護されているメモリに読み取りまたは書き込み操作を行おうとしました。他のメモリが壊れていることが考え
られます。
   場所 GemStone.GemFire.Cache.Generic.Region`2.Put(TKey key, TValue value, Object callbackArg)
   場所 ProtoClient.QueueCacheListener.<>c__DisplayClass1.<AfterCreate>b__0(Object state) 場所 C:\GemFire7\ProtoClient\ProtoClient\Consumer.cs:行 205
...

 

In the other cases, there was no such OutOfRangeException.

 

Is the native client doing other registerRegex calls "behind my back"? Not sure though if this question is relevant to my problem.


Viewing all articles
Browse latest Browse all 240675

Trending Articles