Java Parallel Processing Framework 1.3 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Java Parallel Processing Framework 1.3 (Default branch)
# 1  
Old 06-17-2008
Java Parallel Processing Framework 1.3 (Default branch)

Image JPPF is a computational grid framework for Java focused on performance and ease of use. It provides a set of tools and APIs to enable the parallelization of CPU intensive applications, and distribute their execution over a network of heterogenous nodes. It features platform independence thanks to Java 1.5, does not require you to deploy your application classes to a server, scales up to millions of nodes, has a built-in fail-over mechanism on all the framework's components, and has a monitoring and administration GUI tool to enable remote monitoring of the server health and server shutdown/restart operations. License: The Apache License 2.0 Changes:
A critical bug that caused the server to freeze unexpectedly was resolved. A packaging issue was fixed for the Tomcat port. The administration and monitoring console now comes as a separate standalone package. The server now stores on file any data too large to fit in memory. A new abstraction model for IO operations brings a smaller footprint and a performance gain up to 15%. JPPF library files now include version and build information.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
DACS.JAVA(7)						  DACS Miscellaneous Information					      DACS.JAVA(7)

NAME
dacs.java - DACS Java support DESCRIPTION
This document describes support for Java provided by DACS. To enable Java support, DACS must be configured using the --enable-java flag. It may also be necessary to specify the location of the Java commands and include files. See dacs.install(7)[1]. Note Java support is currently very limited and should be considered experimental. It is currently only possible to call dacsauth(1)[2] and dacscheck(1)[3] using the Java Native Interface (JNI) provided. The command line arguments to both of these commands are exactly as documented in their manual pages. Each argument is passed as a String. The code is not thread-safe and is probably not suitable for being called many times within a particular process due to assumptions it makes about dynamic memory allocation. There are no immediate plans to improve or extend Java support. Using the existing capability to build the JNI layer, however, it should not be difficult for an experienced Java programmer to build upon the example Java code provided. With Java support enabled, building DACS will copy the JNI shared library and a .jar file to the library directory (default: /usr/local/dacs/lib), and the JNI include files to the include directory (default: /usr/local/dacs/include). The tools/java/jni distribution directory contains a simple script called javarun that demonstrates how to run dacsauth or dacscheck as a Java application. For example, to validate the Unix password for user somebody, run (as root): ./javarun dacsauth -m unix suff -user somebody -prompt DIAGNOSTICS
The return codes are as documented in the command's manual page. AUTHOR
Distributed Systems Software (www.dss.ca[4]) COPYING
Copyright2003-2012 Distributed Systems Software. See the LICENSE[5] file that accompanies the distribution for licensing information. NOTES
1. dacs.install(7) http://dacs.dss.ca/man/dacs.install.7.html 2. dacsauth(1) http://dacs.dss.ca/man/dacsauth.1.html 3. dacscheck(1) http://dacs.dss.ca/man/dacscheck.1.html 4. www.dss.ca http://www.dss.ca 5. LICENSE http://dacs.dss.ca/man/../misc/LICENSE DACS 1.4.27b 10/22/2012 DACS.JAVA(7)