Hi,

Using two virtual DataPower appliances running Release: IDG.2018.4.1.6 Build number: 309660 and DataPower Operations DashBoard running v1.0.8.0 2018-07-10 11:50:34 Z,

We also have a third DataPower not load balanced. It does not exhibit the behavior I'll describe. So we know the behavior described is due to load balanced devices.

So, two identical DataPower appliances monitored by DPOD. The load balance algorithm is based on connections not round robin. We see identical transaction ID's in DPOD as though they are going through each device. We have reviewed the DataPower Gateway logs and the transactions only go through one device The problem here of course is that the counts are off and there's no good way to tell which device the transaction actually went through. The problem is pretty clearly related to the Operations Dashboard.

We've opened an IBM case but no answers so I thought I'd throw it out to this group. Thoughts? Any place else I can try to ask the question?

Thanks,
Jerry

------------------------------
Jerry Way
------------------------------

Hi Jerry,

• Are you talking about the classic simple tid(...) in DP?
• In case there is also some gtid(...), does that differ?
• Do the timestamps of the duplicate tid(...) differ? (I would expect so.)
• Or are you referring to any other custom (DPOD?) transaction id?
• The simple tid(...) in DP is more or less just a limited simple counter that does not guarantee uniqueness, not if looking across multiple instance, even not if looking on one instance and different timestamps. For example, it restarts from small numbers after a restart. I think to recall it is just an int32 or so will rollover after a while depending on transaction volume.
• To overcome tid(...)'s small range, the Global Transaction Id (gtid) got introduced some years ago.

------------------------------
August Ziesemer
------------------------------

Thanks for the reply August,

Everything is duplicated:

(Service) MCI_CI_Inbound 
(URI) GetConversionStatus
01/17 10:00:21.066
(DP Gateway) APONEDPGL01
<Domain>
OK
(tid) 346649521
(gid) 93187ccf35e21f63514a973b1
318

(Service) MCI_CI_Inbound
(URI) GetConversionStatus
01/17 10:00:21.066
(DP Gateway) APONEDPGL02
<Domain>
OK
(tid) 346649521
(gid) 3187ccf35e21f63514a973b1
318


------------------------------
Jerry Way
------------------------------

Original Message:
Sent: Fri January 17, 2020 04:06 AM
From: August Ziesemer
Subject: DPOD duplicate transaction messages in load balanced setup

Hi Jerry,

• Are you talking about the classic simple tid(...) in DP?
• In case there is also some gtid(...), does that differ?
• Do the timestamps of the duplicate tid(...) differ? (I would expect so.)
• Or are you referring to any other custom (DPOD?) transaction id?
• The simple tid(...) in DP is more or less just a limited simple counter that does not guarantee uniqueness, not if looking across multiple instance, even not if looking on one instance and different timestamps. For example, it restarts from small numbers after a restart. I think to recall it is just an int32 or so will rollover after a while depending on transaction volume.
• To overcome tid(...)'s small range, the Global Transaction Id (gtid) got introduced some years ago.

------------------------------
August Ziesemer
------------------------------

Mhm, strange indeed. I suggest to raise a support ticket at https://www.ibm.com/mysupport/ to get this analysed in more detail.

------------------------------
August Ziesemer
------------------------------

Original Message:
Sent: Fri January 17, 2020 01:53 PM
From: Jerry Way
Subject: DPOD duplicate transaction messages in load balanced setup

Thanks for the reply August,

Everything is duplicated:

(Service) MCI_CI_Inbound 
(URI) GetConversionStatus
01/17 10:00:21.066
(DP Gateway) APONEDPGL01
<Domain>
OK
(tid) 346649521
(gid) 93187ccf35e21f63514a973b1
318

(Service) MCI_CI_Inbound
(URI) GetConversionStatus
01/17 10:00:21.066
(DP Gateway) APONEDPGL02
<Domain>
OK
(tid) 346649521
(gid) 3187ccf35e21f63514a973b1
318


------------------------------
Jerry Way
------------------------------


Original Message:
Sent: Fri January 17, 2020 04:06 AM
From: August Ziesemer
Subject: DPOD duplicate transaction messages in load balanced setup

Hi Jerry,

• Are you talking about the classic simple tid(...) in DP?
• In case there is also some gtid(...), does that differ?
• Do the timestamps of the duplicate tid(...) differ? (I would expect so.)
• Or are you referring to any other custom (DPOD?) transaction id?
• The simple tid(...) in DP is more or less just a limited simple counter that does not guarantee uniqueness, not if looking across multiple instance, even not if looking on one instance and different timestamps. For example, it restarts from small numbers after a restart. I think to recall it is just an int32 or so will rollover after a while depending on transaction volume.
• To overcome tid(...)'s small range, the Global Transaction Id (gtid) got introduced some years ago.

------------------------------
August Ziesemer