DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=42416>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=42416 Summary: Tomcat startup hangs and AJP13 connector port 8009 and control connector on port 8005 never start - confluence appears to lock up when permissions set incorrectly in confluence.home subdir(s) Product: Tomcat 5 Version: 5.5.23 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Environment: Linux 2.6.9-42.0.10.ELsmp Java 1.5.0_10 Apache Tomcat 5.5.23 Confluence-2.4.5 (from ear/war distribution w/out source-confluence-2.4.5.tar.gz) Issue: In the directory defined by confluence.home, after running and setting up confluence, there is a directory created on confluence.home called bundled-plugins. We accidentally started up tomcat as root instead of the regular user that tomcat runs under in our environment. After doing this, we shutdown tomcat, cleared the work directory, and reset permissions recursively throughout Tomcat, but we failed to reset permissions recursively in confluence.home, and confluence's <confluence.home>/bundled-plugins directory was set with only read access for the user that runs the tomcat application (basically it was incorrectly set as owned by root). When this is the case, it seems to lock up the confluence and tomcat startup process, which is apparent because the AJP13 port 8009 is not listening and the shutdown port 8005 is not listening after startup. We turned on full debug logging (after trying ajp and coyote debug logging) in tomcat but there was nothing about AJP or any coyote connectors trying to start when this occurs. I imagine that any web application that locks up in whatever manner confluence is getting locked up in this particular situation (sorry for the lack of detail) will keep the AJP13 and control ports from opening in tomcat. After removing all files and directories in confluence.home and restarting tomcat, all is fine. Probably resetting permissions on that directory would have worked just as well, but we didn't test that. We requested to atlassian that they consider adding code to potentially keep this from happening. Since I found no documentation of this rare situation anywhere, I thought I'd log it as it would appear that a webapp can keep tomcat from starting up normally, and I would think potentially there could be a better way that tomcat could insulate itself from similar lock-ups. (Note: I logged this issue to confluence's support as well, and yes I know that apps typically don't like having non-standard permissions set in critical places; just hoping that this info may help make tomcat better or may help someone else.) Thanks! -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
