Browse Prior Art Database

Fast full file locking for multi-tenancy cloud Java platform Disclosure Number: IPCOM000238161D
Publication Date: 2014-Aug-06
Document File: 2 page(s) / 35K

Publishing Venue

The Prior Art Database


On multi-tenancy Java cloud platform, multiple Java applications run in one Java virtual machine instance, which provides high-density Java application deployment and resource control over resource like networking, CPU, thread, etc. But tenant applications run in one JVM still uses traditional Java file locking mechanism provided by conventional Java SE class library, which is based on operating system's file locking infrastructure and is not friendly with cloud environment especially from performance perspective. This idea is to provide aparatus of using Java SE language level locking facility to substitute whole file locking between tenant applications, which significantly improves performance of file locking.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 58% of the total text.

Page 01 of 2

Fast full file locking for multi

Fast full file locking for multi-

Multi-tenancy Java platform accommodates multiple Java applications in one JVM instance and provides fine-grain control over resource consumption, which significantly improves application density of cloud platform and startup time of Java application. But for the Java developers, one important mechanism for inter-process synchronization is to lock one file between applications, even on multitenancy cloud Java platform this synchronization still has to be done via operating systems' file locking API, such as fcntl, which introduces flexibility over partial locking but also lose performance for the common case of full-file locking.

the drawbacks would be:

- Inconsistent locking behavior between underlying OS platforms, primarily for mandatory / advisory locking style.
- Performance overhead of communicating underlying OS function via JNI calls.

- Waste of naming spaces in virtual file system, names is more expensive in cloud environment.

The idea here is to leverage J2SE locking APIs to replace JNI based file locking implementation for full file locking scenarios for multitenancy cloud Java applications.

The partial file locking is not included in this idea, due to the very much of complexity.


- Consistent locking behavior comparing to the platform dependant way.

- Significant performance improvement over locking / unlocking.

- Java memory model based locking behavior.

- Ability to lockin...