Re: [Opaltoolkit-users] problem launching opal jobs

[Malcolm T. <mt...@wu...>]

Sriram,

On Sunday 28 June 2009 12:59:04 pm Sriram Krishnan wrote:

> > It wasn't clear to me whether this needs to be set when doing the 'ant
> > install' stage, or when starting Tomcat so I did both.  
>
> The Tomcat server is the one that needs the libdrmaa to be in its
> LD_LIBRARY_PATH because it needs to launch the jobs via DRMAA. The
> client doesn't need this property to be set. Make sure that that this
> environment variable is set correctly before starting Tomcat (and also
> that this environment variable is available to Tomcat as well). I am
> assuming that you are starting up Tomcat from a bash shell - so an
> export LD_LIBRARY_PATH before running the Tomcat start script on the
> same shell should do the trick.

I tried to make it clear in my email that a) I had set LD_LIBRARY_PATH b) it 
included libdrmaa (i.e. 'ls $LD_LIBRARY_PATH') and c) I was using the same 
shell to start Tomcat.  Even after that, I'm still seeing the error.

Maybe it would help if I understood Java better.  If I was building a 
Fortran/C program with autoconf, I'd expect to have to pass configure some 
option to use DRMAA.  This would either produce a staticly-linked binary that 
would produce a compile-time error if it couldn't find the library, or a 
dynamically-linked binary that would produce a run-time error if it couldn't 
find the library.

With Tomcat, I haven't done anything to tell it to use DRMAA.  There doesn't 
seem to be the equivalent of a binary that I could run 'ldd' on to verify it 
was going to use libdrmaa.  Maybe that's because the support for DRMAA is in 
the Opal stuff (e.g. /webapps/opal2/WEB-INF/lib/drmaa.jar)?  How can I debug 
whether Tomcat is failing to find the library?  Why wouldn't Tomcat/Opal 
complain if it couldn't find libdrmaa rather than fail silently?

Malcolm

-- 
Malcolm Tobias
314.362.1594