[Swift-devel] Re: swift-falkon problem

[Michael Wilde]

as i backtrack looking at my svn trees, i see that indeed my memory was 
wrong and i do need to checkout deef explicitly.

- mike


On 3/17/08 8:34 AM, Michael Wilde wrote:
> I did a clean checkout to get the latest rev directly on the bblogin 
> machine (previously I copied the code).
> 
> Strange: this time provider-deef didnt show up in the modules directory. 
>  I *thought* last time it did, unless I'm imagining things.
> 
> Did something just change w.r.t provider-deef, or is my memory faulty?
> 
> - Mike
> 
> 
> 
> On 3/17/08 7:43 AM, Ioan Raicu wrote:
>>
>>
>> Ben Clifford wrote:
>>> So from the Swift log you paste, this line:
>>>
>>> 2008-03-16 16:43:44,213-0600 DEBUG TaskImpl 
>>> Task(type=JOB_SUBMISSION,           identity=urn:0-1-1-1205707420808) 
>>> setting status to Active                      2008-03-16 
>>> 16:43:44,213-0600 DEBUG TaskImpl Task(type=JOB_SUBMISSION,           
>>> identity=urn:0-1-1-1205707420808) setting status to Failed  
>>> suggests that provider-deef is reporting a failure up to the Swift 
>>> runtime. There may be some more logs that you can turn on at the 
>>> provider-deef or falkon layer, but I don't know what the likely ones 
>>> would be.
>>>   
>> iraicu at viper:~/java/svn/cog/modules/provider-deef/etc> cat 
>> log4j.properties.module
>> log4j.logger.org.apache.axis.utils.JavaUtils=ERROR
>> log4j.logger.org.globus.cog.abstraction.impl.execution.deef=DEBUG
>>
>> I have this log4j property, do you have this enabled?  This should 
>> enable more debug output from the Falkon provider.
>>> >From a process point-of-view, I'm concerned about this:
>>>
>>>  
>>>> - the deef-provider code that I get with a swift checkout seems to 
>>>> have out     of date falkon stubs (I get a runtime error on a 
>>>> missing xml element)           - if I grab a FalkonStubs jar from 
>>>> Zhao's bgp swift tree and use it in a        newly compiled swift 
>>>> tree, should that work? It seems to get further.      
>>>
>>> If provider-deef needs updating, those updates should be made in SVN; 
>>> if it doesn't need updating, then you have some other problem. Ioan 
>>> and Zhao, if you had to update something to make it work, please 
>>> commit that change.
>>>   
>> I know we should update SVN, we just haven't gotten around to it.  I 
>> just updated the stubs in the Swift SVN (R1727).  Mike, give it a try 
>> again from SVN.
>>
>> Ioan
>>
>> -- 
>> ===================================================
>> Ioan Raicu
>> Ph.D. Candidate
>> ===================================================
>> Distributed Systems Laboratory
>> Computer Science Department
>> University of Chicago
>> 1100 E. 58th Street, Ryerson Hall
>> Chicago, IL 60637
>> ===================================================
>> Email: iraicu at cs.uchicago.edu
>> Web:   http://www.cs.uchicago.edu/~iraicu
>> http://dev.globus.org/wiki/Incubator/Falkon
>> http://dsl-wiki.cs.uchicago.edu/index.php/Main_Page
>> ===================================================
>> ===================================================
>>
>>
>