Bugzilla – Bug 3533
notification not fired in Tomcat
Last modified: 2005-08-03 17:16:47
You need to
before you can comment on or make changes to this bug.
When Tomcat is started without GLOBUS_LOCATION env. variable set, the
notification are never fired. From what I can tell so far I think the process
that watches the log file is not properly started.
This depedency on G_L env. variable is bad in the first place since gram code
pulls the globus location setting from its configuration. So potentially the
environment variable and the configuration bit can point to two different
locations. Also, we don't want to require G_L to be set in Tomcat becuase it
will prevent from running different versions of GRAM in Tomcat.
This looks like a call to globus_common_get_attribute_from_config_file() in
seg_fork_module() requires G_L to be set. So I think the G_L either has to be
explicitely passed through cmd line or set as a env. property when the seg
process is started from Java.
I made the SEG exec() call set GLOBUS_LOCATION to the value configured in the
service configuration. If you could test this with either an updated HEAD or
globus_4_0_branch then I can close this out.
Works for me. Thanks!