-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ken,
On 3/8/18 11:31 AM, Kenneth Taylor wrote:
> To clarify: We were making changes to our webapp and re-deploying
> and the changes were not showing up. We think this was happening
> because of the shutdown problem I stated earlier. There was
Thanks for the pointers. I did not realize that I had setup Tomcat emails to
go to a folder and didn't see people's responses. Sorry about that.
To clarify: We were making changes to our webapp and re-deploying and the
changes were not showing up. We think this was happening because of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ken,
On 3/6/18 9:09 AM, Kenneth Taylor wrote:
> More troubleshooting revealed that our root context xml had been
> copied from another installation and had a wrong path in it.
Do I smell another Darwin Award nomination?
> However, I don’t think
Kenneth,
On 06.03.2018 15:09, Kenneth Taylor wrote:
More troubleshooting revealed that our root context xml had been
copied from another installation and had a wrong path in it. However,
I don’t think this was the problem since it was only a path to a Log4J
config. We re-installed Tomcat
Kenneth,
As MarkT suggested earlier, there is no such "Cache". If you are using
Tag/Cotext Pooling - it's a separate issue and you need to check tomcat's
documentation to check what options you need/don't need.
"The “-XX:+DisableAttachMechanism” JVM option does not work with Tomcat" -
what do
More troubleshooting revealed that our root context xml had been copied from
another installation and had a wrong path in it. However, I don't think this
was the problem since it was only a path to a Log4J config. We re-installed
Tomcat from scratch and it seems to have resolved it, but this
On 05/03/18 21:26, Kenneth Taylor wrote:
> We are having a serious problem with Tomcat (8.5). Twice it has decided
> to PERMANENTLY cache one of our webapps. We are unable to update that
> webapp. We’ve tried everything imaginable, short of uninstalling
> Tomcat, which is the next step.
>
>
I’m guessing that the OP’s configuration or user permissions are not allowing
war unpacking to update the webapps directory to the new version of the webapps.
This has happened to me on some of my installations in the past when an admin
starts as root vs. a special user like tomcat. This is
Hello,
can you explain what you mean by 'caching' ?
regards
Leon
On Mon, Mar 5, 2018 at 10:26 PM, Kenneth Taylor <
kenneth.tay...@dataexpress.com> wrote:
> We are having a serious problem with Tomcat (8.5). Twice it has decided
> to PERMANENTLY cache one of our webapps. We are unable to
