On 06.07.15 15:37, Tim Cronin wrote:
is there any documentation on migrating from 1.3 to 2?
Not yet. I started to write something, but I have yet to finish it.
the JCSAdmin.jsp the FAQ link is broken. moved due to package change
On 06.07.15 17:06, Tim Cronin wrote:
I added the following before calling the composite cache shutdown.
this should be called via the composite cache shutdown code i think
ThreadPoolManager poolMgr = ThreadPoolManager.getInstance();
for(String poolName :
will there be another release cut soon?
how close to non beta release?
On Fri, Jul 10, 2015 at 1:48 AM, Thomas Vandahl t...@apache.org wrote:
On 06.07.15 17:06, Tim Cronin wrote:
I added the following before calling the composite cache shutdown.
this should be called via the composite
yes is see it there, but nothing about it being changed in 2.x.
On Fri, Jul 10, 2015 at 4:12 PM, Thomas Vandahl t...@apache.org wrote:
On 06.07.15 16:33, Tim Cronin wrote:
MaxLifeSeconds has been changed to MaxLife, didn't find anything in the
docs about this change.
See
On 06.07.15 16:33, Tim Cronin wrote:
MaxLifeSeconds has been changed to MaxLife, didn't find anything in the
docs about this change.
See http://commons.apache.org/proper/commons-jcs/RegionProperties.html
Bye, Thomas
-
To
i understand that 1.3 is old and the 2 branch will be the way going forward
but...
this happens on our production server and really don't want to run beta
code on it.
i've played with the beta code and it requires code changes on our side as
well.
On Sun, Jul 5, 2015 at 10:25 AM, Thomas Vandahl
is there any documentation on migrating from 1.3 to 2?
the JCSAdmin.jsp the FAQ link is broken. moved due to package change
http://svn.apache.org/viewvc/commons/proper/jcs/trunk/commons-jcs-core/src/main/java/org/apache/commons/jcs/admin/JCSAdmin.jsp?view=log
On Mon, Jul 6, 2015 at 7:37 AM, Tim
I added the following before calling the composite cache shutdown.
this should be called via the composite cache shutdown code i think
ThreadPoolManager poolMgr = ThreadPoolManager.getInstance();
for(String poolName : poolMgr.getPoolNames()) {
try {
AuxDiskCache is throwing error that it can't create the directory but it
already exists.
localhost-startStop-1 2015-07-06 14:01:30,006 ERROR
org.apache.commons.jcs.auxiliary.disk.AbstractDiskCacheAttributes - Failed
to create directory C:\java\tomcat\temp\oeserver-cache
I tested mkdirs and it
MaxLifeSeconds has been changed to MaxLife, didn't find anything in the
docs about this change.
What is the proper way to shutdown jsc now?
this i how it was recomended to it in 1.3
CompositeCacheManager.getInstance().shutDown();
I'm getting the following errors in tomcat when
thanks for the reply.
looking at trunk there's an added check isDirectory.
On Mon, Jul 6, 2015 at 9:30 AM, sebb seb...@gmail.com wrote:
On 6 July 2015 at 15:15, Tim Cronin t...@outboundengine.com wrote:
AuxDiskCache is throwing error that it can't create the directory but it
already
On 6 July 2015 at 15:15, Tim Cronin t...@outboundengine.com wrote:
AuxDiskCache is throwing error that it can't create the directory but it
already exists.
localhost-startStop-1 2015-07-06 14:01:30,006 ERROR
org.apache.commons.jcs.auxiliary.disk.AbstractDiskCacheAttributes - Failed
to create
On 02.07.15 15:13, Tim Cronin wrote:
JCS 1.3
i periodically get the above error.
what do i need to do to recover from this?
First of all I'd suggest to try out commons-jcs 2.0-beta1. It contains
numerous fixes and cleans up the lifecycle of most of the JCS manager
classes. If that
13 matches
Mail list logo
