<?xml version="1.0" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugzilla.globus.org/bugzilla/bugzilla.dtd">

<bugzilla version="3.2.3"
          urlbase="http://bugzilla.globus.org/bugzilla/"
          maintainer="bacon@mcs.anl.gov"
>

    <bug>
          <bug_id>4787</bug_id>
          
          <creation_ts>2006-10-17 09:20</creation_ts>
          <short_desc>no lifetime management for WS Rendezvous</short_desc>
          <delta_ts>2012-09-05 11:43:27</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>GRAM</product>
          <component>wsrf rendezvous</component>
          <version>4.0.3</version>
          <rep_platform>All</rep_platform>
          <op_sys>All</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>WONTFIX</resolution>
          
          
          
          
          <priority>P3</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Scott Koranda">skoranda@univa.com</reporter>
          <assigned_to name="Stuart Martin">smartin@mcs.anl.gov</assigned_to>
          <cc>bacon@mcs.anl.gov</cc>
    
    <cc>smartin@mcs.anl.gov</cc>

      

      
          <long_desc isprivate="0">
            <who name="Scott Koranda">skoranda@univa.com</who>
            <bug_when>2006-10-17 09:20:01</bug_when>
            <thetext>Olle Mulmo first pointed this out to me, but don&apos;t blame him if this bug is incorrect...

A cursory reading of the source for WS Rendezvous seems to indicate that there is no lifetime management for resources created by invoking the createSync operation of the WS Rendezvous service.

I think it would be useful if there was a default lifetime that could be changed when invoking createSync, and then also the customary destroy operation that one could use to completely destroy the resource when appropriate.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who name="Charles Bacon">bacon@mcs.anl.gov</who>
            <bug_when>2007-09-19 11:38:04</bug_when>
            <thetext>Reassigning to current GRAM developer to close/fix as appropriate.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who name="Stuart Martin">smartin@mcs.anl.gov</who>
            <bug_when>2012-09-05 11:43:27</bug_when>
            <thetext>Doing some bugzilla cleanup...  Resolving old GRAM3 and GRAM4 issues that are no longer relevant since we&apos;ve moved on to GRAM5.  Also, we&apos;re now tracking issue in jira.  Any new issues should be added here:

http://jira.globus.org/secure/VersionBoard.jspa?selectedProjectId=10363</thetext>
          </long_desc>
      
      

    </bug>

</bugzilla>