Hm, that sounds weird. Can you try the simple client from http://www.globus.org/mail_archive/gram-user/2008/01/msg00034.html (adjust hardcoded values) and check if it works?
Martin > Hi Folks, > > we have serious problems to submit ineractive jobs via the gramjob Java > API > (ws-gram). > > First of all we create a FactoryEndpointReferenceType as suggested by > www.ibm.com/developerworks/grid/library/gr-wsgram/index.html > > However, it doesn't work. The method gramjob.submit doesn"t throw any > exception, isn't blocked, but the job is never executed. We have tried to > get > an fault and error code, but we fault of null, and an error of 0 (see end > of > the sniplet. > > [snip] > > Address: > https://xx.xx.xx.xx:8443/wsrf/services/ManagedExecutableJobService > Reference property[0]: > <ns1:ResourceID > xmlns:ns1="http://www.globus.org/namespaces/2004/10/gram/job";>ffc69550-cf50-11dc-b209-91714a565505</ns1:ResourceID> > > 5108 [main] DEBUG org.globus.exec.client.GramJob - Job Endpoint: > Address: > https://xx.xx.xx.xx:8443/wsrf/services/ManagedExecutableJobService > Reference property[0]: > <ns1:ResourceID > xmlns:ns1="http://www.globus.org/namespaces/2004/10/gram/job";>ffc69550-cf50-11dc-b209-91714a565505</ns1:ResourceID> > > after job.submit > null > 0 > [snip] > > In the attachments you can find the parts of the source code. > > Any ideas? All what we want is to submit jobs using gt wsgram, and the GT4 > Java API, and we like to be able to retrieve the job state, get the exit > status, and so on... > > Cheers > > Alexander and Roelof >
