From: Malcolm T. <mt...@wu...> - 2009-06-29 17:52:07
|
Sriram, On Monday 29 June 2009 12:44:47 pm Sriram Krishnan wrote: > Whether it is using DRMAA or not is defined in the opal.properties > file. You can verify that it is using DRMAA by looking at your Tomcat > logs. If it is indeed using DRMAA, Opal should print the following to > the log - "Using job manager class: job manager class being used". Gotcha. > Ideally, it should really throw an exception. In fact, most errors are > indeed logged by Opal/Tomcat. However, the DRMAA support is provided > by using a 3rd party package that uses the Java Native Interface. We > have noticed that it sometimes dies silently, rather than throwing a > useful exception (however, this doesn't happen once DRMAA has been > properly configured). In any case, do you have a line in your Tomcat > log like - "Can't initialize DRMAA session:". Nope, all I'm seeing is: catalina.out:2009-06-26 13:18:12,515 INFO edu.sdsc.nbcr.opal.AppServiceImpl.launchApp(AppServiceImpl.java:579) - Using job manager class: edu.sdsc.nbcr.opal.manager.DRMAAJobManager Is there an easy way for me to test whether the 3rd party package is configured/working properly? Is there some way for me to increase the verbosity of the debugging? Malcolm -- Malcolm Tobias 314.362.1594 |