From: Dido Sevilla Date: 2007-05-03T14:19:55+09:00 Subject: Re: threads, dRuby... On 5/3/07, Andy Koch wrote:> Not sure where to start, so I'll just jump in...> Here's the weird thing about this. When I start the dRuby server, it> always throws a FireRuby exception when the libxml opens an xml file for> xsl transformation. But, it only does this the first time the server is> called. All subsequent calls to the dRuby server run all code as> designed without any trouble. Have you tried running the code locally, i.e. not remotely via druby?Distributed Ruby tends to mask exceptions thrown by the called processin many cases in my experience, and the error you get tends to getobscured by the time it gets to the remote caller. All you know isthat there was an error of some kind, just not what error it was. Ihave a couple of very large projects that use druby extensively, andthis sort of behavior was so frustrating that I've made it a point totest any code intended to be run via drb by executing it locallyfirst, and making sure that error handling is as bulletproof androbust as I can make it. It seems highly unlikely to me that libxml isreally throwing your fireruby exception, more likely it's throwingsome other exception that winds up getting masked as one by the timeit gets to the druby client. -- 普通じゃないのが当然なら答える私は何ができる？普通でも普通じゃなくて感じるまま感じることだけをするよ！http://stormwyrm.blogspot.com