Hello,
I met a strange TMF ID issue these day , here is the case -
Pathway server - Server 1 , Server 2
Audit File - File 2
#1 Server 1 - Begin TMF, send request to Server 2
#2 Server 2 - Get the TMF ID passed from Server 1, response back
imediately and then read File 2 with lock ( record A)
#3 Server 1 - send the 2nd request to Server 2
#4 Server 2 - Get the same TMF ID , response back imediately and then
read File 2 with lock ( record A)
#5 Server 1 - END TMF
The issue happened on #4, somehow it looks as the TMF ID waits the
record A lock taken by Server 2's process itself. This looks odd but
I cannot say where the problem is, could someone assist on this ?
Server 2 process pstate -
$VOL.SUBVOL.FILE2
LOCK REQUESTER KEY
TYPE STATE ID LEN KEY/RECORD ADDRESS
F GI \NODE.2.399332052
LOCK STATE = LK^IX
F G
LOCK STATE = UNDEFINED
$VOL.SUBVOL.SECMIN
LOCK REQUESTER KEY
TYPE STATE ID LEN KEY/RECORD ADDRESS
R G \NODE.2.399332052 14
LOCK STATE = LK^X
Thanks
WILL
|
|
0
|
|
|
|
Reply
|
cdyjldy (59)
|
12/1/2011 4:57:53 PM |
|