[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] python soap issue



Do you go through the same cycle you describe bellow when adding
the new job?  If not, you'll need to do so, because you need a
new cluster before a new job can be added.  This is a limitation
of the current implementation.  Try doing it this way and see if
you still run into problems.

Regards,
-B

> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-
> bounces@xxxxxxxxxxx] On Behalf Of Leandro Martelli
> Sent: Tuesday, January 13, 2009 11:25 AM
> To: condor-users@xxxxxxxxxxx
> Subject: [Condor-users] python soap issue
> 
> Dear All,
> 
> I'm using the SOAP interface to remotely control my condor jobs. I
> tried
> following this reference:
> 
> http://www.cs.wisc.edu/condor/birdbath/JobSubmissionAPI-R2.pdf
> 
> I tried to follow the "NewCluster() -> NewJob() -> Submit() -> NewJob()
> -> Submit()" cycle. The detail is that a have a "createJobTemplate"
> before "submit". With only one job, I can submit just fine. If I try to
> execute "createJobTemplate" again after a previous "submit", I receive:
> 
> ZSI.EvaluateException: Element "_jobAd" missing from complexType
> [Element trace:
> /SOAP-ENV:Envelope/SOAP-
> ENV:Body/condor:createJobTemplateResponse/response]
> 
> What's interesting is that the REQUESTs are the same (changing only
> IDs). Can anyone give a hint to what I'm missing here? Should I only
> change parameters in the classAd object and submit again? I also tried
> do re-use the jobAd object with a new job, but no luck.
> 
> Thanks a lot,
> 
> </Martelli>
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with
> a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> 
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/