Even after upgrading the client from 184.108.40.206 to 220.127.116.11 there was no use but when 10.2.0.1 client was installed, the problem disappeared.
Now customer wants to know root cause of the problem on 18.104.22.168/8.
I would like to know:
What is the condition which causes the above assertion or more accurately invokes this assertion ?
Do our development still leave assertions within production code ?
Any known bugs on this particular version 22.214.171.124/126.96.36.199 ?