MySQL Forums
Forum List  »  InnoDB

Advanced Search
New Topic

Re: Connection.close() has already been called. Invalid operation in this state
Posted by: Eric Long
Date: December 29, 2010 08:35AM

You might try disabling the call to the fn_transaction_id().

update sym_trigger
set tx_id_expression = 'null',
last_update_time = now()

Restart your SymmetricDS server and it will re-generate the triggers. The triggers will no longer use fn_transaction_id(). This will disable the transaction awareness for the SymmetricDS replication software, but in many applications it is not needed. If that fixes it for you, we can debug the fn_transaction_id() stored procedure to see what we can do there.

Eric

Navigate: Previous Message• Next Message
Options: Reply• Quote


Subject
Views
Written By
Posted
Connection.close() has already been called. Invalid operation in this state
8918
santosh jami
November 15, 2010 04:29AM
Re: Connection.close() has already been called. Invalid operation in this state
2450
Rick James
November 16, 2010 11:48PM
Re: Connection.close() has already been called. Invalid operation in this state
2194
santosh jami
November 17, 2010 01:09AM
Re: Connection.close() has already been called. Invalid operation in this state
1918
Rick James
November 18, 2010 12:17AM
Re: Connection.close() has already been called. Invalid operation in this state
2149
santosh jami
November 26, 2010 12:22AM
Re:crash using SymmetricDS
1656
Rick James
November 26, 2010 01:25PM
Re: Re:crash using SymmetricDS
2330
santosh jami
December 01, 2010 04:56AM
Re: Connection.close() has already been called. Invalid operation in this state
1936
Eric Long
December 29, 2010 08:35AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.