We have had an example of a crash with this assertion. The only reference I can find to this on the interweb comes from CR 447782 (in v10.0.1) where spurious cases of it were being reported. I'm opening a support case, but I wondered if anyone has come across it before?

v 16.0.0.2076

asked 30 Jul '15, 06:53

Justin%20Willey's gravatar image

Justin Willey
6.8k111145214
accept rate: 20%

Case ref 586955

(30 Jul '15, 09:08) Justin Willey
Replies hidden
Comment Text Removed

How do I look up "Case ref 586955"?

(11 Aug '15, 11:00) Breck Carter
readme_10_0_1.txt     
Size on disk: 344 KB (352,256 bytes)     
Created: Thursday, ‎April ‎26, ‎2007, ‏‎1:06:02 PM

SQL Anywhere 10.0.1 Release Notes for Windows and Netware

10.0.1 Behavior Changes and Critical Bug fixes

    ===============(Release Build  - Engineering Case #447782)===============

    The server could have reported spurious 104904 assertions ("latch count not 
    0 at end of request"). This would only have happened on multiprocessor machines. 
    A problem with the per-connection counters in question has been corrected.

(11 Aug '15, 11:11) Breck Carter
Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×207
×46
×32

question asked: 30 Jul '15, 06:53

question was seen: 12,386 times

last updated: 11 Aug '15, 11:11