innovaphone Apps SDK Developer Forum

Registered 5 years 214 days

iqbal Wednesday, 6 December 2023, 02:06 PM

Replicator is running in infinite loop after update 13r1 App to 13r3 App

I have a problem that Replicator is running in infinite loop after update 13r1 App to 13r3 App. Users are replicated again and again. Funny part is that only one instance of app is affected. other instances are running normaly.

we are using Following platform versions:

App Manager: 13r2 136437 sr28

IPVA: 13r3 sr11 IPVA[13.7919], Bootcode[1000], Hardware[0]

second question is, can 13r3 App run on App Manager and IPVA with different versions ?

Best Regards

Iqbal

Moderator

Registered 13 years 45 days

Andreas Fink (innovaphone) Wednesday, 6 December 2023, 02:37 PM

Re: Replicator is running in infinite loop after update 13r1 App to 13r3 App

Hello Iqbal,

the version of the AP Manager should not affect the replication process. It is more the SDK version, that contains the replication library, that was used to compile the app binary and the PBX firmware version that provides the API.

The app can usually run on different versions of the AP manager and depending on PBX API used by the app it can be also different version of the PBX firmware.

It depends on the used APIs. You can check notes regarding compatibility between the different versions in the "Project Upgrade" articles of the "Tutorials" section.

Moderator

Registered 13 years 45 days

Andreas Fink (innovaphone) Wednesday, 6 December 2023, 02:40 PM in response to iqbal

Re: Replicator is running in infinite loop after update 13r1 App to 13r3 App

Regarding the loop of the replication - we will need some more input here, especially the message flow where the replication was set up and the loop itself.

Best Regards

Andreas Fink

Registered 5 years 214 days

iqbal Wednesday, 6 December 2023, 03:39 PM

Re: Replicator is running in infinite loop after update 13r1 App to 13r3 App

Hi Andreas

Thanks for your reply. I sent you Log file via email.

Best Regards

Iqbal

Registered 5 years 214 days

iqbal Thursday, 7 December 2023, 11:52 AM in response to iqbal

Re: Replicator is running in infinite loop after update 13r1 App to 13r3 App

I found out that this endless loop is caused by non-existing unique key constraints.

But question is why does the replicator expect username(h323) as "ON CONFLICT (username)" part of the query?

here we want to use "ON CONFLICT (uid)".

Is there any way to override this replicator query ?

Also in my opinion the replicator should not run endlessly if the unique key constraint does not match.

Here is Log snippet that causes infinite loop:

PostgreSQLDatabase(013b22c0,013b1b28)::ExecSQLV user:013bc3d8 flags:00800001 sqlCmd:INSERT INTO users (username,phone,cn,uid,node,pseudo) VALUES ('Test Import Test Import','106','Test Import Test Import','b6c8189d3cd364011ad70050569337b0','root',NULL) ON CONFLICT (username) DO UPDATE SET (username,phone,cn,uid,node,pseudo) = (EXCLUDED.username,EXCLUDED.phone,EXCLUDED.cn,EXCLUDED.uid,EXCLUDED.node,EXCLUDED.pseudo) RETURNING id

12-07 10:27:35.369 test_app PostgreSQLDatabase(013b22c0,013b1b28)::LastCommandFailed (42P10):ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification

12-07 10:27:35.369 test_app PostgreSQLDatabase(013b22c0,013bc3d8)::DatabaseError error: DB_ERR_SQL_COMMAND_FAILED

12-07 10:27:35.369 DatabaseError3

12-07 10:27:35.370 test_app AppWebsocket(013be410)::AppWebsocketMessageComplete connected:true

12-07 10:27:35.370 ReplicatorSession(13bf160)::SendReplicateNext

12-07 10:27:35.370 test_app AppWebsocket(013be410)::AppWebsocketMessageSend {"mt":"ReplicateNext","api":"PbxTableUsers"} connected:true

Registered 5 years 214 days

iqbal Friday, 8 December 2023, 11:21 AM in response to iqbal

Re: Replicator is running in infinite loop after update 13r1 App to 13r3 App

with a little bit of experimentig i found the Problem. The Problem was that Replicator was using username(h323) "ON CONFLICT (username)" part of the query and that cant be used because it contains null values.

for this to work you have to change ON CONFLICT (some_unique_key)" part of the query. Only way I could change this clause was to reorder replicator AddColumn code.

Here is solution:

replicator = IReplicator::createReplicator(this, "PbxTableUsers", 0, 0, "domain", "pbx", database, "users", true, false);
RegisterJsonApi(replicator);
replicator->AddColumn("guid", "uid", ReplicationString, false); <--- must be on first place to change "ON CONFLICT (uid)" part of insert query of replicator
replicator->AddColumn("h323", "username", ReplicationString, true);
replicator->AddColumn("e164", "phone", ReplicationString, true);
replicator->AddColumn("cn", "cn", ReplicationString, true);
replicator->AddColumn("node", "node", ReplicationString, false);
replicator->AddColumn("pseudo", "pseudo", ReplicationString, false);

I could not find this in any tutorial or any documentation.

Best Regards

Iqbal

You are here