Summary: | www-servers/tomcat-6.0.14-r1 - manager silently fails to deploy unpacked webapp with bad symlink | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Owen Kaser <o.kaser> |
Component: | [OLD] Server | Assignee: | William L. Thomson Jr. (RETIRED) <wltjr> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | java |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Owen Kaser
2007-12-11 16:53:42 UTC
From the sounds of this I believe this is a Tomcat bug, not specific to Tomcat running on Gentoo Linux. Or a result of how it's packaged or etc. It might be, if it's our fault the broken symlink is created in the first place. Otherwise Tomcat is pretty notorious, at least from my experience, on dealing with broken symlinks horribly. I haven't tried it with 6.0.x, but any 5.x version if you place a broken symlink in any of Tomcat's lib dirs with jars, like common/lib or server/lib. Tomcat will fail to start, and give pathetic, if any log output. Most always nothing even hinting at a cnfe, or broken link, or etc. Unless we can determine the broken symlink is caused by something we do to Tomcat on gentoo as part of it being packaged. Or as a result of running on this distro/OS, etc specifically. Then it's an upstream bug for them to resolve. No comment or response from reporter, assuming problem is not specific to tomcat on Gentoo. Closing as invaild, please reopen if problem persists and is specific to Tomcat on Gentoo. |