ClntIdent is wrong sometimes

Sometimes when a java client requests something from a java server ClntIdent is set to other’s id.

To be clear:

client1 - java PID=1234

client2 - java PID=4321

server has transactionType = TransactionType.NONE

client1 writes an attribute on the server and gets ClntIdent = java PID=4321, i.e. ClntIdent of the client2

JTangoServer-9.0.3; TangORB-9.1.0

Does anyone have any idea why this can happen?

Thank you in advance.

Best regards,

Igor.

Looks like this happens when CORBA switches RequestProcessor thread, i.e.

For instance, when client1 requests the server on the server request is executed in RequestProcessor-5 thread.
If subsequent request from the client1 is executed in Requestprocessor-4 there is chance of this problem to happen (client1 gets identity of client2).

Seems to be multi-threading issue…