Hi – since starting up my Tomcat 8.0.12 server, I get tons of logs in
catalina.out stating org.apache.catalina.webresources.Cache.getResource Unable
to add the resource at [variousURLs] to the cache because there was
insufficient free space available after evicting expired cache entries -
On 2014-12-08 21:22, Ameer Mawia wrote:
Hi Theo,
Since you are using static membership and NOT dynamic(multi-cast) which
auto-detect members, my current understanding says that you will have
to
add entry of all the members of your cluster in each of nodes
server.xml.
Example:
My cluster has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Kevin,
On 12/9/14 8:58 AM, Kevin McKee wrote:
Hi – since starting up my Tomcat 8.0.12 server, I get tons of logs
in catalina.out stating
org.apache.catalina.webresources.Cache.getResource Unable to add
the resource at [/variousURLs/] to the
Thanks Chris. Yes - I want to fix whatever is causing that warning to
appear, and thus stop it from appearing in my logs. I’m not an expert on
Tomcat config so please help me what settings I should remove or add in
order to fix this issue.
Do I want to disable the cache to eliminate the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Kevin,
On 12/9/14 11:01 AM, Kevin McKee wrote:
Thanks Chris. Yes - I want to fix whatever is causing that warning
to appear, and thus stop it from appearing in my logs. I’m not an
expert on Tomcat config so please help me what settings I
Greetings!
I’ve got a problem using Tomcat 7.0.47 NioConnector with nginx 1.6.2 and
atmosphere 2.2.3.
It happens when nginx and atmosphere close the same comet connection
concurrently.
In NioEndpoint.Poller thread(A) the SocketChannel becomes ready for read when
nginx closes it. Poller
On Tue, Dec 9, 2014 at 9:16 AM, Théo Chamley theo...@mley.fr wrote:
On 2014-12-08 21:22, Ameer Mawia wrote:
Hi Theo,
Since you are using static membership and NOT dynamic(multi-cast) which
auto-detect members, my current understanding says that you will have to
add entry of all the members
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/9/2014 9:48 AM, Daniel Mikusa wrote:
On Tue, Dec 9, 2014 at 9:16 AM, Théo Chamley theo...@mley.fr
wrote:
On 2014-12-08 21:22, Ameer Mawia wrote:
Hi Theo,
Since you are using static membership and NOT
dynamic(multi-cast) which
I examined the code of ClusterSingleSignOn.
This behavior seems to be bug.
There seems to be some other problems.
a) When a new node is started, SingleSignOnEntry of cache is not
replicated. (you mentioned.)
b) ClusterSingleSignOn does not implement ClusterValve.
c) Unsupported to BackupManager.
