Re: [Archive-access-discuss] Wayback works with tomcat cluster?

[Brad T. <br...@ar...>]

Hi Natalia,

Sorry about the delayed response. I'm not sure I understand your 
question/problem. Are you trying to run multiple tomcat 
instances(processes) using the same BDB index? In this case, I don't 
think it will work - the BDBJE code wants only a single process to write 
to an environment, and currently the wayback always tries to open the 
BDB read-write. If this is something that really needs to happen, we 
mightbe able to change the way the software opens the databases, but I'm 
not sure if BDBJE supports this.

You may be able to solve this problem using multiple AccessPoints, using 
wayback 1.0 or later.

Can you elaborate on how you're trying to set up the wayback in this 
deployment?

Brad

Natalia Torres wrote:
> Hello
>
> I installed wayback 0.8 following the instructions on web page and 
> customizing it for using the wayback machine in timeline access
> mode.
>
> When I upgrade to use 2 tomcat v.5.5  on cluster, wayback doesn't work. 
> I get this message from log file:
>
> INFO: new org.archive.wayback.resourceindex.LocalResourceIndex created.
> org.archive.wayback.exception.ConfigurationException: A je..lckfile 
> exists in /mywaybackdata/index The environment can not be locked for 
> single writer access.
>
> When I search on UI I get this message:
>
> Configuration Error
>
> A je..lckfile exists in /paditest/wayback/index The environment can not 
> be locked for single writer access.
>
>
> Each tomcat must have his own indexes? They can't share it? Exist any 
> setting for this in configuration files=
>
> Thanks
>
> N.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Archive-access-discuss mailing list
> Arc...@li...
> https://lists.sourceforge.net/lists/listinfo/archive-access-discuss
>