AW: [geclipse-dev] Release testing

["Stuempert, Mathias IWR" <mathias.stuempert@xxxxxxxxxx>]

Hi Pawel,

Just testing things again and here are my results. I tested with three VOs (gLite, GRIA and AWS) and three corresponding projects in a new workspace from the very beginning to be sure to catch up any cross-correlations.

> gLite - working submission, output files, LFC->SRM copy

Confirmed! Furthermore file transfers SRM<->GSIFTP works.

> - First I had problems with adding services to GRIA VO. NoClassDefFound
> from GRIA classes:

Cannot confirm this. GRIA worked really fine for me this time. Job submission, data management, everything green from my point of view.

> Restart helped. Cannot reproduce it. I got similar exception also on 
> another occasion, but also not repruducible.
> Some strange side effect. It looks that GRIA libraries are referenced in 
> strange places. e.g. I had exception NoClassDefFound just after adding new 
> AWS VO project. And also somewhere from gLite project. Looks like 
> infosystem refreshes all other projects when adding new project?

Strange indeed. So either somehow your workspace got messed up or there is really a cross-correlation problem. As I said I tested especially for such correlations but cannot confirm your problems here. But you're right, the info system is the only part where all types of VOs/projects are connected somehow. So maybe Nick you should test more exhaustively for such correlations, but not for this release any more. 

> - during next try g-Eclipse completely hung while trying to add jobService 
> to GRIA VO

I had such a behaviour yesterday morning with the nightly build. This always occures when accessing networks. Still I do not believe that this is really g-Eclipse related. From time to time I also realise such behaviour with pure Eclipse, i.e. CVS, SVN, always network-related. It may occur more often within g-Eclipse because everything we do is about networking, right ;-)

> - cannot submit job - timeout. I am not sure if it is server problem or 
> not.
> - cannot acces data service - unspecified I/O? - server problem ??

gLite? GRIA? FZK-services? I had a lot of problems with FZK services yesterday and I am not sure if and when they were solved. If your tests involved any FZK infrastructure (i.e. GridKa or even the GRIA installation on iwr-geclipse.fzk.de) then these problems may most likely be caused by the network problems.

> - sometimes GRIA asks for keystore in strange places. e.g. create project 
> with GRIA plugin, add services, delete project(also from disk) restart 
> gEclipse. Now try to create new project. Dialog is shown "GRIA key store 
> is needed to start GRIA plug-in". This is even before I had a chance to 
> select kind of project. Create token or not, effect is the same, nothing 
> happend. This usecase works often, but not always. One time I got keystore 
> request dialog later, when I clicked edit button for GRIA VO. In general 
> it is not showstoper, but definitely to be solved ASAP.

I agree, we already have an action item for this. The GRIA AAI is completely messed up somehow.

> mo voting is 0. It means +1, but -1 for GRIA now. As I am not sure if it 
> is server problem or gEclipse problem must be checked and confirmed by 
> others.

So I cannot confirm the problems you had with GRIA. Therefore I stay with +1 for the release.

Cheers, Mathias