Pb in transaction ? between firebird 2.5 and 3.0

[dehorter]

HI

I migrate my database from Firebird 2.5 to 3.0 using the same application compiled from Delphi XE7 (using IbDAC 5.6.21) [the soft is exactly the same].
And now I receive this message :

invalid transaction handle (expecting explicit transaction start)

or

Error writing data to the connection

According to Firebird team, this problem doesn't come from them..

All computers use its own firebird driver on 3050 port (servermode = Super).

I am downgrading all computers to 2.5, but 2 of them are able to use firebird 3.0 in order to respond of your recommendations and test them

regards

olivier

[ViktorV]

Unfortunately, we couldn't reproduce the issue. In order to investigate the issue, please compose and send to viktorv*devart*com a small sample demonstrating the issue, including scripts for creating database objects.

[dehorter]

Hello

Unfortunately, we couldn't reproduce the issue.

damned

In order to investigate the issue, please compose and send to viktorv*devart*com a small sample demonstrating the issue, including scripts for creating database objects.

Yes why not, but I don't know where and when the problem occurs . It should be better in first time to precise a little bit more when and where the pb occurs. I set-up logger along the soft in order to track the bug.
Do you have some recommendations for me to place this log at strategic places and which "devart" information you wish to obtain in order to solve that ?

regarrds

olivier

[ViktorV]

Try to clarify when the error occurs: while connecting to the database, on table opening, record insertion or editing, transaction start/commit, etc. Set logging in such places of your code. Analyze the log and try to find code lines leading to the error. Then try to compose a separate simple application reproducing the issue and send it to viktorv*devart*com, including a script to create and fill in the test database object.

[dehorter]

Hi

Just to give you some information about this pb.

I follow your recommendations. I turned my application on 2 computers for half-day without any trouble...

I will do it an other time with more computers and using Trace and audit services. But unfortunately, I cannot to that for the moment. But I will contact you again as soon as I make this test

regards

olivier

[ViktorV]

When you get any results concerning this question, please let us know about them.

[dehorter]

Hi Victor

Since one week, I come back to use Firebird 3.0 at production level.
And the same problem occurs. I receive this error :

invalid transaction handle (expecting explicit transaction start

Just to remind you:
* the same database on Firebird 2.5 with the same app work perfectly
* In firebird 3.0, with only one user, it works perfectly too

I place logger in any StartTransaction / prepare and commit/rollback and open/execute operations.

They are 2-3 transactions opened at the same time.
Each opened transactions is closed by a commit/rollback action.

The errors appears each time when on user active a insert/update procedure whereas the other user, during the same time active reading procedure.
When both use reading procedure, everything is ok.

I found than other peoples had the same trouble :
http://comments.gmane.org/gmane.comp.db ... user/13932


But maybe it is not a pb coming from devart ?

[ViktorV]

Please compose a small sample reproducing the described behavior and send it to viktorv*devart*com, including scripts for creating database objects, in order for us to be able to give you a more detailed answer.

[dehorter]

Hello

I tried but without success till now.

No idea ?
What change between 2.5 and 3.0 can explain this change of behaviour ?

I continue to put logger into my code in order to track that.
I check the status of the transactions each time. Do you expect others informations coming from logger (about connexion status, ...) ?

regards
olivier

[ViktorV]

If you want to know what changes between Firebird 2.5 and Firebird 3 could lead to such behavior, please address the Firebird technical support.
As we informed you earlier, unfortunately, we could not reproduce the problem. To determine the cause of the problem and find out a solution to fix it, we need a test case in which the problem consistently occurs. Therefore, we ask you to compose and send us an example that reproduces the problem. Once we receive this example, we will try to fix it as soon as possible.

[dehorter]

Hi

For your information, it seems to be a bug from firebird 3 (http://tracker.firebirdsql.org/browse/CORE-5307)

Thanks for your help

olivier

[ViktorV]

Thank you for being interested in our products.
Feel free to contact us if you have any further questions about IBDAC.