Hi,
sounds very much like the reason for the instability. Current LINUX pthread library 
creates lots of 'spurious' signals, which are not handled correctly. The client 
runtime of SAPDB is completely dumb according to its signal handling. But we cannot 
wait until the current pthread library is replaced
by POSIX complient RedHat or IBM solution....
SAPDB client runtime simply expects, that signals are used only for killing a running 
program and not for internal dispatching of pthreads. We have to wrap all the system 
calls, to have a stable multithreaded client runtime on LINUX. Not a small job, but a 
necessary one to get it stable.

> -----Original Message-----
> From: Flemming Frandsen [mailto:ff@;partyticket.net]
> Sent: Sonntag, 10. November 2002 18:13
> To: SAPDB
> Subject: Re: First failiure of the "fixed" odbc interface on Linux
> 
> 
> Flemming Frandsen wrote:
> > [SAP AG][LIBSQLOD SO][SAP DB]Unable to connect to data source;-709 
> > CONNECT: (cannot create reply fifo). (SQL-08001)(DBD: 
> > db_login/SQLConnect err=-1)
>  >
> > This means that the script connected to the database around 
> 4300 times 
> > without anything going wrong, so it's not like this bug 
> shows up a lot.
> 
> This sounds a lot like what happens when people forget to 
> handle EINTR, 
> and the process suddenly gets a signal for some reason.

see above...

> 
> sql41_create_fifo, the routine that seems to fail, contains calls to 
> mknod and chown, both may return EINTR and there is no sign 
> of re-trying 
> the system calls in that case.
> 
see above...

> There is also no trace of trying to report the actual 
> errorcode (errno), 
> something that would make it a lot easier to debug this problem...

That is true. I currently can only suggest to use 'strace' to pin down the problem...

> 
> As a bonus, who is UKP?

UKP is an acronym for UserKernelProcess. A UKP contained kernel tasks. The new name of 
UKP is UKT (UserKernelThreads)...

CU
jrg
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to