Re: [Bug] Deadlock in shark occurs

Occured only once for now, i'll check first if i can repoduce :)
Perhaps I'll run the unit test in loop for the whole week-end to see.
I just transmitted problem for information purpose, now sure it is possible the 
deadlock occurs inside hsql.

If it's sql related, then i won't care much as hsql is used only for our unit tests.

But i'll check.

Thanks
Le Mercredi 7 Septembre 2005 16:30, [email protected] a écrit :
> David Delbecq <[email protected]> wrote on 09/07/2005 09:59:33 AM:
> 
> > Hello
> > 
> > While running some unit testing to use the shark corba api, i 
> > noticed a test was taking
> > quite a big amount of time to finish. In fact, it didn't seem keen 
> > on finishing.
> > I suspended the whole test using the eclipse debug interface.
> > The client part is stuck in a call to get_next_object():
> > 
> >       WfAssignmentIterator iterator = resource.
> > get_iterator_work_item(); // specs
> > iterator.set_query_expression("activityId.equals(\""+activity+"\")");
> >       return iterator.get_next_object();
> > 
> > This is not called in a loop nor is it reproducable after stopping /
> > rerunning unit test.
> > The unit test always start on a fresh new hsql database, so 
> > environnemental conditions
> > of test are well controlled and always the same. 
> 
> David, just one thing: can you reproduce your problem with a database 
> other than HSQL?  Becaues I know I ran into several problems with hsql 
> which went away when i used a "real" database.. Just a thought..
> 
> Geeta
> 

-- 
David Delbecq
Royal Meteorological Institute of Belgium

-
Is there life after /sbin/halt -p?

--
You receive this message as a subscriber of the [email protected] mailing list.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws