Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
servletd deadlock state
chicka
Hi guys,
I am receiving below error in
/logs/iwui/error.log
Details:
TS 6.7.1
Solaris 10
[Fri Feb 06 14:33:21 2009] [error] [client 192.168.254.27] (45)Deadlock situation detected/avoided: apr_global_mutex_lock(rewrite_log_lock) failed, referer:
http://139.163.7.229/iw-cc/ccpro/workflow/main.jsp
[Fri Feb 06 14:33:35 2009] [error] [client 192.168.254.27] (45)Deadlock situation detected/avoided: apr_global_mutex_lock(rewrite_log_lock) failed, referer:
http://139.163.7.229/iw-cc/ccpro/workflow/main.jsp
[Fri Feb 06 14:33:45 2009] [error] [client 192.168.254.27] (45)Deadlock situation detected/avoided: apr_global_mutex_lock(rewrite_log_lock) failed, referer:
http://139.163.7.229/iw-cc/ccpro/workflow/main.jsp
Could you please tell me what could be the root cause for this error?
Also after this error is thrown my UI fails to functiona and upon performing iwreset -a, application resumes to normal.
Please shed input on this case.
Find more posts tagged with
Comments
Adam Stoller
I've no idea, but if you haven't already done so - you should open a case with IWOV Support.
chicka
I've no idea, but if you haven't already done so - you should open a case with IWOV Support.
Thank you Ghoti
I have raised the case with support team.
Will post the details if I get any update from them.
sumitkatre
Hi Chicka,
Did you get any responce from support team?
Thanks & Regards
SUMIT KATRE
amu
Hi chika,
I have also faced the similar dead lock issue in my machine. The scenario i have followed is as below,
1. The user was already a master, and we removed the access for the user in all the groups and branches except basic groups like iweveryone.
2. Then the user account is verified the user has not allowed to login.
3.We got ERROR MESSASE AS YOU MENTIONED IN THE ERROR LOG
3.We checked for the locked file of the user.
4.Some files are already locked by the user.
5.We unlocked the files in another login.
6.Once we try to login with the user ID it was working with out any issue.
So please check for the locked files before removing the permissions or user roles.
Regards,
Amu