Bug 3544 – globusrun-ws using null service path

Bug 3544 - globusrun-ws using null service path

Summary:

globusrun-ws using null service path

Status:	RESOLVED

Product:	GRAM
Component:	wsrf gram clients
Version:	development
Platform:	PC Linux

Importance:	P3 blocker
Target Milestone:	4.0.1
Assigned To:	Joe Bester

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-07-07 13:52 by Peter Lane
Modified:	2006-08-17 09:44 (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 Peter Lane 2005-07-07 13:52:10

A simple globusrun-ws submit (globusrun-ws -submit -s -c /bin/date) gives me
the
following error:

Delegating user credentials...Failed.
globusrun-ws: Error trying to delegate
Error querying delegation factories
globus_soap_message_module: SOAP Fault
Fault code: ns1:Server.NoService
Fault string: The AXIS engine could not find a target service to invoke! 
targetService is null

------- Comment #1 From Peter Lane 2005-07-07 14:26:11 -------

I should mention that this is from the trunk.  I have yet to rebuild the 4.0
branch for testing this.  Thus it might be premature to target this for 4.0.1 if
the branch is unaffected.

------- Comment #2 From Joe Bester 2005-07-07 15:52:48 -------

I haven't been able to duplicate this with the gt4 branch.

joe

------- Comment #3 From Peter Lane 2005-07-07 17:25:20 -------

My rebuild on ruly also doesn't show this. I'm resolving the bug.

------- Comment #4 From Techkd 2006-08-17 05:54:20 -------

i am submitting condor job to GT 4... 
executable = /bin/ls
universe = grid
grid-type = gt4
#globusscheduler = i2it:8443
JobManager_type = Fork
#universe = globus
grid_resource = gt4
https://192.168.7.131:8443/wsrf/service/urn:ManagedJobFactoryService Fork
output = test_env3.out
log = test_env3.log
error = test_env3.err
notification = error
#requirements = (OpSys == "LINUX")
queue 1

and in the log i found the following...
018 (080.000.000) 08/17 15:57:03 Globus job submission failed!
    Reason: 0 The AXIS engine could not find a target service to invoke! 
targetService is null
...
012 (080.000.000) 08/17 15:57:07 Job was held.
        Globus error: The AXIS engine could not find a target service to
invoke!  targetService is null

any clues to its solution..........

------- Comment #5 From Peter Lane 2006-08-17 09:44:24 -------

Techkd,

You'll need to get debugging information from Condor-G showing that something
is suspicious with it's interaction with GRAM before we look at this. I'd also
encourage you to post such questions on the gram-user mailing list. That said,
I don't see a service URL in your Condor job description that is assigned to
any variable. I'm not terribly familiar with how these things are done, but I
would assume that you'd have to set the service URL somewhere. If I were to
guess I'd say that was your problem.