Bug 3533 - notification not fired in Tomcat
: notification not fired in Tomcat
Status: RESOLVED FIXED
: GRAM
wsrf managed execution job service
: unspecified
: PC Windows XP
: P3 blocker
: 4.0.1
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2005-06-29 14:18 by
Modified: 2005-08-03 17:16 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2005-06-29 14:18:28
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.
------- Comment #1 From 2005-06-29 15:19:04 -------
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.
 
------- Comment #2 From 2005-07-05 18:09:00 -------
Jarek,

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.
------- Comment #3 From 2005-07-07 00:37:30 -------
Works for me. Thanks!