I have a webapplication that re-uses database connections across web-requests, in general it works ok.

The database server is:
Kernel = Kernel 7.3.0 Build 029-000-087-800
Runtime Environment = X32|LINUX 7.3.0 Build 029-000-087-800

I tried the odbc interface lib that came with that build, but I found that it started failing during connect with "Unable to create communication semaphore" (or some such) after only 1-2 hours of light load, to clear the error I had to stop the x_server and start it again.

Stopping and starting the clients didn't do any good at all.

The DSN used with the 7.3.0.25 version of the driver, was 127.0.0.1:ZDB, using :ZDB or localhost:ZDB caused a segfault during connect.


I've gone back to using an extremely old (7.3.0.17) version that was compiled with debug, it seems to be stable, but after a while, typically 24h of fairly light load, new connections to the database start to fail with:

[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)

The DSN used was :ZDB not 127.0.0.1:ZDB as used with the new version, so that might be a source of the differences.


Everything runs on x86 Linux.

I'm not using a driver manager, the DBD::ODBC driver was compiled directly against the sapdb odbc lib, so if I'm the only one doing this then that may the reason for the instability I'm seeing here.

Have anyone seen errors like these?


It may be a good idea to make it possible to build sapdb with electric fence: ftp://ftp.perens.com/pub/ElectricFence/ElectricFence-2.1.tar.gz it's an implementation of malloc that places the end of the memory allocated just before an inaccessible page, so that any overflowing writes will cause a segfault on the exact instruction that caused the error, this is great for debugging.

--
Regards Flemming Frandsen - http://dion.swamp.dk
PartyTicket.Net co founder & Yet Another Perl Hacker

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

Reply via email to