Recently we had an issue where mobile users were unable to do transactions, as mobile server transaction processes stilll existed in the database. Killing them had no result. truss on them did not work. adb or mdb debuggers gave unspecified system error. While googling for this, I came across the following command here:
dtrace -n profile-1234hz'/pid == 4308/{@[stack()] = count()}'
which might return a stack trace like this one:
issig_forreal+0x5c0()
cv_wait_sig+0x190()
snf_segmap+0x450()
sosendfile64+0x2a0()
sendvec64+0xf0()
sendfilev+0x178()
syscall_trap32+0xcc()
It didn't in our case and the dtrace command took forever. The process got cleared from process table after we fixed server load issue with some other processes.
Blog dedicated to Oracle Applications (E-Business Suite) Technology; covers Apps Architecture, Administration and third party bolt-ons to Apps
Thursday, June 5, 2008
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment