On 06.06.2018 21:36, Mark Thomas wrote:
On 06/06/18 20:30, Jan Tosovsky wrote:
Dear All,
I use tomcat as a Liferay portal engine. It is usually stopped in two steps.
There is Shutdown button available in Liferay Control panel, which stops the
webapp. Once this is finished, it is safe to stop tomcat via the standard
shutdown script.
If tomcat is stopped differently:
* tomcat is shutdown without shutting down the Liferay
* java crashes (out of memory)
* tomcat is killed
* OS is rebooted (driven by server hosting)
it sometimes (not always) deletes some web content, usually JSP pages, to my
experience especially of the ROOT app (in case of Liferay the default Tomcat
ROOT app is replaced with the core Liferay app).
After the last incident even the core config file ROOT/WEB-INF/web.xml was
missing. And without it tomcat was not able to launch the portal properly.
When you know what has happened it is 'easy' to fix.
But I am quite curious why anything is even deleted in such 'crash'
scenarios.
I met this in various tomcat versions, let say 7.0.xx- 8.0.xx running on
Oracle JDK 7-8 on both Windows 7-10 and CentOS 6-7.
Any idea why this happen?
There is no way I can think of that Tomcat would do this. I'd suggest
two things:
1. Talk to Liferay support
2. Change the file permissions
Indeed - I'd also recommend to bring this to the Liferay forums (or
Liferay support, if you have a support (Enterprise) contract). I've
never heard such behavior from Liferay, and shutdown in two steps is not
typically necessary.
In case your shutdown processes run out of memory, it might be as simple
as allocating a bit more memory, or to validate your custom plugins for
their memory requirements during shutdown. I'm not aware that Liferay
uses excessive memory during shutdown.
To add a few more pointers to look at: If you're on a 6.x version of
Liferay, there's the possibility to deploy hooks that physically
overwrite JSPs. These might get undeployed and redeployed, but there are
some caveats to pay attention to - specifically to only overwrite a
single JSP from a single hook. Technically, you'd be able to overwrite
Liferay's web.xml from such a hook, but this is utterly useless and
shouldn't be done. Only in case you're doing this, I could imagine a
case where web.xml disappears.
But, Mark's recommendation is solid: Check the Liferay forums, this
doesn't look like a tomcat issue. Send me the link to the forum post and
I'll take a look at it there.
Olaf
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
