The following message is observed in the Alert logs:
|CID: 11, Client IP: , User: , Debug_Code: 524, Message: INSIST(\\\"Query in transaction\\\" && fd_st->holder->bReset_conn_bit_srvsend_pending == NO) failed, reset_bit_logic:8228, [ssid 14827245,fdtype CLIENT_FD], State: 21, SSID: 0, DB: , DB IP: , Type: 37|
This message gets logged in ScaleArc's Alert Message in certain conditions, like one discussed here.
Consider the following sequence of events
1. Transaction start using TM_BEGIN_XACT
2. UPDATE query fired
3. Transaction end using TM_COMMIT_XACT
4. Fire RPC called DSgetUserDefaultSiteId with RESET BIT set on it. - This is where we see the INSIST message
5. Start Transaction using TM_BEGIN_XACT with reset bit
What happened here is since ScaleArc goes in query pass through for the transaction manager requests, it did not detect that the transaction got over, and immediately after that the query came with a reset bit, thus making it believe that connection is still in the transaction and gets a reset bit. This issue won't affect the traffic though and the message can be safely ignored.
If you are experiencing issues with ScaleArc or with any of its features, please contact ScaleArc Support. We are available 24x7 by phone at 855 800 7225 or +1 408 412 7315. For general support inquiries, you can also e-mail us at firstname.lastname@example.org.