Hi Steve,
Globus 4.2 web services (primarily for compatibility with many of our
European collaborators) adopted the final WS-RF (1.2), and WS-N (1.3)
specifications and these are not compatible with Globus 4.0 web services.
One
suggested migration strategy (that will be adopted by the TeraGrid for
example) is to encourage provider sites to temporarily host both GT 4.0 & GT
4.2 containers to help facilitate the transition.
Some background: We started on this path over a year ago when we held public
discussions both on email (gt-user & gt-dev) and as a community wide
dial up phone discussion. At this time we discussed issues of
incompatibility and even explored the option of maintaining compatibility by
allowing both specifications to run in the same container. This option was
deemed to be too complex and error prone and would jeopardize the stability
of the Globus software base that we have been fighting so hard to create and
maintain. Still, there was a clear consensus to upgrade the specifications,
knowing that the community would need to eventually migrate their servers in
order to maintain compatibility. For more background see
http://dev.globus.org/wiki/Java_WS_Core/SpecificationUpgrade. Also, in case
it may be helpful, here is a guide for transitioning GRAM services to 4.2:
http://www.globus.org/toolkit/docs/4.2/4.2.0/execution/gram4/mig/gram4-migrating-gt40.html.
One piece of good news is that there are no more wire protocol changes
anticipated for Globus.
Hope this helps,
Dan Fraser
Director, Community Development & Improvement of Globus Software
----- Original Message -----
From: "Steve White" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, July 17, 2008 4:13 AM
Subject: [gt-user] 4.2.0 job submission to older servers
Hi,
We have just discovered the disturbing fact that Globus job submission
from a Globus 4.2.0 installation to a Globus 4.0.x server fails.
Please explain how we are to make this work. Are we doing something
wrong, misunderstanding something?
We have a network of many resouces being administered under many
different institutions.
We do not want to hear that every resource in the network has to update
together. "Impractical" would not be strong enough a word for that.
Cheers!
=======================================================================
$ globusrun-ws -submit -b -F <<4.0.7-server>> -S -o job.epr -c /bin/sleep
60
Submitting job...Failed.
globusrun-ws: Error submitting job
globus_soap_message_module: Failed receiving response
http://www.globus.org/name
spaces/2008/03/gram/job/ManagedJobFactoryPortType/createManagedJobResponse.
ws_addressing: Addressing header is a draft version of WS Addressing:
"http://sc
hemas.xmlsoap.org/ws/2004/03/addressing". This could be a GT version
mismatch, c
lient is GT 4.2.x and response is from GT 4.0.x server
=======================================================================
See
http://www.globus.org/toolkit/docs/4.2/4.2.0/user/errors.html#gram4-errors-table
search for
ws_addressing: Addressing header is a draft version of WS
Addressing
- - - - - - - - - - - - - - - - - - - - - - - - -
| Steve White +49(331)7499-202
| e-Science / AstroGrid-D Zi. 35 Bg. 20
- - - - - - - - - - - - - - - - - - - - - - - - -
| Astrophysikalisches Institut Potsdam (AIP)
| An der Sternwarte 16, D-14482 Potsdam
|
| Vorstand: Prof. Dr. Matthias Steinmetz, Peter A. Stolz
|
| Stiftung privaten Rechts, Stiftungsverzeichnis Brandenburg: III/7-71-026
- - - - - - - - - - - - - - - - - - - - - - - - -
