Alexander,

There's no obvious reason for crash. I'd recommend to set number of
threads greater than maximum number of concurrent connections and
re-try. If bug persists I'd like to get some environment to reproduce
the problem locally, say, a database and client.

Best Regards,

Ivan Mikhailov,
OpenLink Software
http://virtuoso.openlinksw.com


On Tue, 2008-09-16 at 16:49 +0400, lasa...@lvk.cs.msu.su wrote:
> Hello Ivan,
> 
> On Tue, Sep 16, 2008 at 11:45:33AM +0700, Ivan Mikhailov wrote:
> > Alexander,
> > 
> > Well, usually it does not crash. It's hard to tell the reason without
> > hardware/OS details, content of virtuoso.ini file, some description of
> > load (say, sample queries). It would be nice to have an output of
> > status() call made under less-than-critical load.
> > 
> 
> Hardware:
>  - CPU: Intel Pentium 4 at 2.60GHz with HyperThreading enabled
>  - RAM: 2GB
>  - disk: IDE 40GB disk with DMA enabled
> 
> OS: Debian lenny
> 
> /proc/cpuinfo, lspci and virtuoso.ini attached.
> The output of status() one second before crash attached.
> I see a lot of uncommitted transactions. Seems to me it is a cause of
> the crash.
> 
> --
>   Alexander


Reply via email to