167275 – Invalid initial connectivity test using GetResourcePropertyDocument

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 167275 - Invalid initial connectivity test using GetResourcePropertyDocument

Summary: Invalid initial connectivity test using GetResourcePropertyDocument

Status:	RESOLVED DUPLICATE of bug 167535

Alias:	None

Product:	z_Archived
Classification:	Eclipse Foundation
Component:	TPTP.monitoring (show other bugs)
Version:	unspecified
Hardware:	PC Mac OS X - Carbon (unsup.)

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	Mark Weitzel
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2006-12-08 14:28 EST by davidmelgar
Modified:	2010-06-03 15:03 EDT (History)
CC List:	0 users

See Also:

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 davidmelgar

2006-12-08 14:28:19 EST

When MAX starts up, it attempts a GetResourcePropertyDocument request to determine if the resource is alive. This is not a good operation to attempt. GetResourcePropertyDocument is an optional operation of WSDM resources. GetResourceProperty would be a better request since it is the only required WS-RP operation.
If this operation fails, MAX fails and does not attempt further communication. Its not clear why this step is necessary at all.

Comment 1 Balan Subramanian

2007-01-15 22:44:02 EST


*** This bug has been marked as a duplicate of bug 167535 ***

Comment 2 Dave Smith

2007-01-17 16:31:09 EST

Resolved in iteration 1.

Comment 3 Eclipse Webmaster

2007-07-29 09:21:16 EDT

Changing OS from Mac OS to Mac OS X as per bug 185991