[kepler-dev] Question regarding LastObjectId

[Aaron Schultz]

Madhu,

Yes that is correct, the LastObjectId file is a serialized Java Integer 
and is incremented (read and written) every time a particular instance 
of Kepler assigns a new KeplerLSID to an object.  Under heavy server 
loads there is currently the possibility of collisions when 
reading/writing that file.  It does not currently get locked.  Using 
java.nio.channels.FileLock would be a good enhancement for a server 
environment but has not yet been implemented.

Aaron

madhu wrote:
>  Hi there,
>
>     We are using  Kepler for CAMERA project at SDSC and kepler is run through Sun Grid  engine via a web interface. I have two questions
>
>   Do the kepler installation directory which contains LastObjectId should be writable?
>
>   Secondly, Since multiple users could run multiple workflows from web interface at same time, LastObjectId would be constantly be overwritten?
>
>   I remember first issue was discussed couple of months ago though I do not remember the resolution. I would greatly appreciate if someone could point me to the right direction. 
>
> Thanks
> --Madhu
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at kepler-project.org
> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>