Firebird 3 events broken
------------------------

                 Key: CORE-4756
                 URL: http://tracker.firebirdsql.org/browse/CORE-4756
             Project: Firebird Core
          Issue Type: Bug
          Components: API / Client Library
    Affects Versions: 3.0 Beta 2
         Environment: Jaybird 2.2 branch (head), Jaybird 3.0 (trunk, head), 
fbclient.dll 3.0.0.31794 (64 bit) against Firebird server 3.0.0.31794 (64 bit)
            Reporter: Mark Rotteveel


I have several problems using events in both Jaybird 2.2 and Jaybird 3.0 when 
testing the native implementation in combination with a recent Firebird 3 
fbclient.dll (3.0.0.31794). Depending on the exact test and timing, I get the 
following errors:

Unrecognized events block (335544973) when calling isc_que_events for the 
second time.
invalid events id (handle) (335545021) when calling isc_cancel_events

Adding extra pauses and delays sometimes seems to remove the error only to have 
it replaced by a different error. Running the same test multiple times can give 
different errors. Sometimes it also looks like the callback is triggered when 
no events have been raised.

When switching to the Firebird 2.5.4 fbclient.dll the problems go away.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to