Bug 6063 – Hash collision issue in RFT connection caching

Bug 6063 - Hash collision issue in RFT connection caching

Summary:

Hash collision issue in RFT connection caching

Status:	RESOLVED FIXED

Product:	RFT
Component:	RFT
Version:	4.0.7
Platform:	All All

Importance:	P3 blocker
Target Milestone:	4.0.8
Assigned To:	John Bresnahan

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-05-06 16:44 by Raj Kettimuthu
Modified:	2008-06-03 16:21 (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

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

Description From Raj Kettimuthu 2008-05-06 16:44:32

There is a hash collision issue that results in RFT using a wrong cached
connection. There is NO security breach as collisions are confined to the
connections of an individual user. When file stagein and stageout are done
through GRAM, RFT attempts to use the stagein connection to do stageout (due
to hash collision) and that results in error.

------- Comment #1 From Raj Kettimuthu 2008-06-03 16:21:58 -------

This has been fixed.

An updated globus_wsrf_rft_service_java package is available at 
http://www.globus.org/toolkit/advisories.html