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

Re: [Condor-users] SOAP in 6.7.5


I was writing C# :)

The config file says 9618 for Collector, 6914 for Negotiator and everything else is random.
Collector's queryScheddAds() gives the required info for the scheduler.

Either way, I'll follow Derek's advice and wait for 6.7.6


Matthew Farrellee <matt@xxxxxxxxxxx>
Sent by: condor-users-bounces@xxxxxxxxxxx

03/16/2005 02:45 PM
Please respond to Condor-Users Mail List

        To:        Pawel.Micun@xxxxxxxxxxxxxxxx
        cc:        Condor-Users Mail List <condor-users@xxxxxxxxxxx>
        Subject:        Re: [Condor-users] SOAP in 6.7.5

For the Collector I believe this is an issue with .Net. I'm told people
have had better luck with the most bleeding edge .Net with all patches
applied. If you are not writing C# code you might want to try a
different library, gSOAP or Axis C++ come to mind.

For the Scheduler, is the Schedd actually running on port 9614 or is
that where the Negotiator is running? All daemon, including the
Negotiator, have a basic SOAP interface containing getVersion().


On Mar 16, 2005, at 11:09 AM, Pawel.Micun@xxxxxxxxxxxxxxxx wrote:

> Hello,
> I've been trying to get the SOAP interface working with Condor 6.7.5,
> but ran into some issues and
> I'm wondering if anyone else is willing to share their experiences.
> I installed Condor 6.7.5, downloaded the .wsdl's from the birdbath
> page, placed them in
>  RELEASE_DIR/web, and followed the rest of the installation
> instructions.
> Collector:
> This seems to work correctly with Axis and Java, but fails under .net.
> Under Axis queryAnyAds() returns ClassAdStructArray, which is an array
> of ClassAdStruct's, which
> are wrappers for ClassAdStructAttr[] ... this works fine and gives me
> results.
> Under .net queryAnyAds() is marked to return ClassAdStructAttr[][],
> but when I run it, it returns an empty
> array. The fact that I get something under Axis suggests I should also
> be getting something under .net.
>  Is there a problem with MS's wsdl parser or is it just trying to be
> "helpful" and messes up as usual?
> I am no wsdl guru :(
> Sheduler:
> I was a little less successfull with this one. I gathered that I
> should be using port 9614 for this.
> Most methods, including beginTransaction(), error out with
> "Method 'beginTransaction' not implemented: method name or namespace
> not recognized", under
> both Axis and .net. Surprisingly enough getVersionString() works.
> Also, when I try this, entries show up in NegotiatorLog rather than
> SchedLog.
> Am I contacting the wrong daemon ? If so, what port should I be using?
> Thanks for any feedback,
> Pawel

PRIVILEGED AND CONFIDENTIAL: This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited. If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.