Fura (Grid Middleware): 1.5.5 Released


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Fura (Grid Middleware): 1.5.5 Released
# 1  
Old 12-03-2008
Fura (Grid Middleware): 1.5.5 Released

Fura is a self-contained grid middleware that allows the grid enablement and distribution of applications on heterogeneous computational resources. Fura features a web-based GUI, wizard-guided installation and configuration, and Web Services compliance.
ImageImage

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. UNIX and Linux Applications

Middleware Documentation and logs

Good evening: I need your help please, I am new in Unix/Linux apps like middleware Thare are thousands of documentation about middleware stuff but i would like to have a broader understanding about middleware apps, so i ask you the following questions: 1. In an Enterprise what i am working... (2 Replies)
Discussion started by: alexcol
2 Replies

2. HP-UX

Listing Middleware

I want to know if a server has J2EE application server installed, a webserver or any other middleware, is there a command to output a list or something like that. Thak you (1 Reply)
Discussion started by: eponcedeleonc
1 Replies

3. Shell Programming and Scripting

Shell Script for remote Middleware

Hi Experts, :confused: I need help in one of my bit complicated script (for me complicated for experts like you might be simple). I have 100+ Middleware servers and 200+ DB servers and 200+ application servers in my environment. What I’m looking is I have a script ready sitting on one JUMP... (12 Replies)
Discussion started by: shiv2001in
12 Replies
Login or Register to Ask a Question
Plack::Middleware::StackTrace(3pm)			User Contributed Perl Documentation			Plack::Middleware::StackTrace(3pm)

NAME
Plack::Middleware::StackTrace - Displays stack trace when your app dies SYNOPSIS
enable "StackTrace"; DESCRIPTION
This middleware catches exceptions (run-time errors) happening in your application and displays nice stack trace screen. The stack trace is also stored in the environment as a plaintext and HTML under the key "plack.stacktrace.text" and "plack.stacktrace.html" respectively, so that middleware futher up the stack can reference it. This middleware is enabled by default when you run plackup in the default development mode. You're recommended to use this middleware during the development and use Plack::Middleware::HTTPExceptions in the deployment mode as a replacement, so that all the exceptions thrown from your application still get caught and rendered as a 500 error response, rather than crashing the web server. Catching errors in streaming response is not supported. CONFIGURATION
force enable "StackTrace", force => 1; Force display the stack trace when an error occurs within your application and the response code from your application is 500. Defaults to off. The use case of this option is that when your framework catches all the exceptions in the main handler and returns all failures in your code as a normal 500 PSGI error response. In such cases, this middleware would never have a chance to display errors because it can't tell if it's an application error or just random "eval" in your code. This option enforces the middleware to display stack trace even if it's not the direct error thrown by the application. no_print_errors enable "StackTrace", no_print_errors => 1; Skips printing the text stacktrace to console ("psgi.errors"). Defaults to 0, which means the text version of the stack trace error is printed to the errors handle, which usually is a standard error. AUTHOR
Tokuhiro Matsuno Tatsuhiko Miyagawa SEE ALSO
Devel::StackTrace::AsHTML Plack::Middleware Plack::Middleware::HTTPExceptions perl v5.14.2 2011-07-08 Plack::Middleware::StackTrace(3pm)