Bug 6518 – GLOBUS_GRAM_PROTOCOL_ERROR_PROTOCOL_FAILED loses error information

Bug 6518 - GLOBUS_GRAM_PROTOCOL_ERROR_PROTOCOL_FAILED loses error information

Summary:

GLOBUS_GRAM_PROTOCOL_ERROR_PROTOCOL_FAILED loses error information

Status:	RESOLVED FIXED

Product:	GRAM
Component:	gt2 Gram client
Version:	4.2.0
Platform:	All All

Importance:	P3 enhancement
Target Milestone:	4.2.2
Assigned To:	Joe Bester

URL:
Keywords:	usability

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-11-04 12:44 by Joe Bester
Modified:	2008-11-04 17:02 (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 Joe Bester 2008-11-04 12:44:10

When GRAM returns GLOBUS_GRAM_PROTOCOL_ERROR_PROTOCOL_FAILED it may mean a few
different things:
- SSL signature validation errors
- bad HTTP message framing
- bad GRAM protocol message body

We ran through a long bit of mail to debug an issue related to this:
http://lists.globus.org/pipermail/gt-user/2008-November/000028.html

It would be good to add a way for error-specific information to be set for the
error 10 (similar to what we do for error 7).

------- Comment #1 From Joe Bester 2008-11-04 17:02:46 -------

Added a new function globus_gram_protocol_error_10_hack_replace_message() which
is analogous to the error_7_hack function. It uses the same
thread-local-storage technique as the error 7 one does after fixing bug #6519.
Fix committed to 4.2 branch and trunk.