Hello Ivan,
On Wednesday 17 September 2008 20:31:42 you wrote:
> 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 prob
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,
Op
On Tue, Sep 16, 2008 at 04:49:56PM +0400, lasa...@lvk.cs.msu.su wrote:
> /proc/cpuinfo, lspci and virtuoso.ini attached.
Didn't actually send virtuoso.ini so attached it here.
--
Alexander
;
; virtuoso.ini
;
; Configuration file for the OpenLink Virtuoso VDBMS Server
;
; To learn more about
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 out
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.
Best Regards,
Ivan Mikhailov
Hi All!
I did some stress testing and it made virtuoso crash. Here are some messages
I've gathered:
1. error message on console
virtuoso.jdbc3.VirtuosoException: SR214: Out of server threads. Server
temporarily unavailable. Transaction rolled back.
2. syslog
Sep 15 21:00:52 ws2502 kernel: [4091
