Mailing List Archives

Authenticated access

 		[Computer Systems Lab]

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

Re: [Condor-users] Condor-WS Job sumit issue " UNKOWNJOB"

Different versions of Axis appear to generate different java source files. It's annoying. The birdbath.jar was generated a major release of Axis ago, so I'd suggest you just recompile the source for birdbath.jar with your newly generated java source files. That should show you if there is a version mismatch. The source for birdbath.jar is in the jar itself.
A little background, the main goal of the Condor SOAP interface was to provide all the functionality needed to write robust applications. It isn't the simplest API, because it is not tailored to a specific application. The hope was if people wanted to use it they would write their own helper library on top of it. We never intended to support those libraries, for reasons such as Axis changing generated source files across version. The birdbath.jar was provided as a guide to make the API a bit easier to use for a common case, people who want to mostly just "submit everything in a single operation." If someone is willing to keep it more up to day, please feel free. Also, please let me know how it goes. 

Best,


matt

daobgong wrote:

Thank you, Matt.

I still encounter error by using the birdbath.jar with the follwing error:

Exception in thread "main" java.lang.NoSuchMethodError:
condor.ClassAdStructAndStatus.getClassAd()[Lcondor/ClassAdStructAttr;
        at birdbath.Transaction.submit(Transaction.java:127)
        at birdbathtest.Main.main(Main.java:56)
Java Result: 1

I think my problem is my condor java package. it is somehow different from
others. I did try to compile your birdbath java file based on my condor
package, it shows some of the data type mismatch.

what could be the cause of the different auto-generated java files(wsdl,
axis, or anything else?)? Is there a existing condor.jar ready for
download?

Thanks for your help.

best regards,
David




You should look at the Condor Week Tutorial about APIs. It is much more
current than the IBM document, or at least the example code is.

Best,


matt

daobgong wrote:

Hi,

I am trying to test the Java Code posted by Jeff from IBM ("Manage grid
resources with Condor Web service"). All the functions work perfectly,
except for the Job Submittion with response from server "UNKOWNJOB"

my configuration:
Server:
     condor-6.8.6
     JDK1.6.0_03
     JRE1.6.0_03
Client:
     JDK1.5

while doing debug at the following statement:
      RequirementsAndStatus reqs_s = schedd.submit(transaction,
clusterId,
jobId, jobAd);
jobAd shows perfect record of all the properties to me. I just cannot
monitor what the server receives :-(

May be Srinivasan had a similar problem in Febuary, I could not find out
how he solved his problem.
please help.

cheers,
David

--------condor_config-------
RELEASE_DIR             = /usr/local/condor-6.8.6
WEB_ROOT_DIR            = /usr/local/condor-6.8.6/web
ENABLE_SOAP             = TRUE
ENABLE_WEB_SERVER       = TRUE
ALLOW_SOAP              = */*
HOSTALLOW_READ = *
HOSTALLOW_WRITE = *

----------condor_q result------
-- Submitter: UGDExxx.xxx.xxx.CA : <142.104.61.85:9697> :
UGDEV01.phys.UVic.CA
 ID      OWNER            SUBMITTED     RUN_TIME ST PRI SIZE CMD
 --- ???? ---
 --- ???? ---
  94.0   daobgong       11/9  10:44   0+00:00:19 R  0   9.8  test.sh
** job submitted through condor_submit shows normal status
** job submitted through condorWS java code shows unknown status
** unkown jobs can still deleted by clusterID and jobID if I know the
IDs.


 -------------job_queue.log
***** the unkown status job always has very few entries
103 0.0 NextClusterNum 93
101 092.-1 Job Machine
101 92.0 Job Machine
103 92.0 GlobalJobId "UGDxxx.xxx.xxx.CA#1194629483#92.0"
106
105
******the normal one has many more entries
103 0.0 NextClusterNum 94
101 093.-1 Job Machine
101 93.0 Job Machine
103 93.0 GlobalJobId "UGDExxx.xxxx.xxx.CA#1194631899#93.0"
103 093.-1 ClusterId 93
103 093.-1 QDate 1194631899
103 093.-1 CompletionDate 0
103 093.-1 User "daobgong@xxxxxxxxxxxx ugdev01"
103 093.-1 Owner "daobgong"
103 093.-1 RemoteWallClockTime 0.000000
103 093.-1 LocalUserCpu 0.000000
103 093.-1 LocalSysCpu 0.000000
103 093.-1 RemoteUserCpu 0.000000
103 093.-1 RemoteSysCpu 0.000000

----------Scheduler Log
11/7 09:22:08 (pid:7536) About to serve HTTP request...
11/7 09:22:08 (pid:7536) Completed servicing HTTP request
11/7 09:22:08 (pid:7536) Received HTTP POST connection from
<142.xx.xx.xx:44580>
11/7 09:22:08 (pid:7536) About to serve HTTP request...
11/7 09:22:08 (pid:7536) Completed servicing HTTP request
11/7 09:22:21 (pid:7536) Job has no JobStatus attribute.  Ignoring...
                         ********************************************

11/7 09:22:21 (pid:7536) Job has no JobStatus attribute.  Ignoring...
11/7 09:22:21 (pid:7536) Job has no JobStatus attribute.  Ignoring...
11/7 09:22:21 (pid:7536) Job has no JobStatus attribute.  Ignoring...
11/7 09:22:21 (pid:7536) Job has no JobStatus attribute.  Ignoring...
11/7 09:22:21 (pid:7536) Job has no JobStatus attribute.  Ignoring...
11/7 09:22:21 (pid:7536) Job has no JobStatus attribute.  Ignoring...
11/7 09:22:21 (pid:7536) Job has no JobStatus attribute.  Ignoring...
11/7 09:22:21 (pid:7536) Sent ad to central manager for
daobgong@localdomain localhost
11/7 09:22:21 (pid:7536) Sent ad to 1 collectors for
daobgong@localdomain
localhost
11/7 09:23:30 (pid:7536) Received HTTP POST connection from
<142.xx.xx.xx:40826>
11/7 09:23:30 (pid:7536) About to serve HTTP request...
11/7 09:23:30 (pid:7536) Timer 1095 not found
                         **********************

11/7 09:23:30 (pid:7536) Completed servicing HTTP request
11/7 09:27:21 (pid:7536) Job has no JobStatus attribute.  Ignoring...
11/7 09:27:21 (pid:7536) Job has no JobStatus attribute.  Ignoring...
11/7 09:27:21 (pid:7536) Job has no JobStatus attribute.  Ignoring...
11/7 09:27:21 (pid:7536) Job has no JobStatus attribute.  Ignoring...
11/7 09:27:21 (pid:7536) Job has no JobStatus attribute.  Ignoring...




_______________________________________________
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/

_______________________________________________
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/






_______________________________________________
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/