AW: Settings for pooled datasources, timeout errors

2001-03-12 Thread Jens Stutte
Hi -Ursprngliche Nachricht- Von: Falk Langhammer [mailto:[EMAIL PROTECTED]] Gesendet am: Freitag, 9. Mrz 2001 17:07 An: Orion-Interest Betreff: Re: Settings for pooled datasources, timeout errors Hi From: "Jens Stutte" [EMAIL PROTECTED] no, it is a SAP DB kern

AW: Settings for pooled datasources, timeout errors

2001-03-09 Thread Jens Stutte
Hi, -Ursprngliche Nachricht- Von: Falk Langhammer [mailto:[EMAIL PROTECTED]] Gesendet am: Donnerstag, 8. Mrz 2001 19:21 An: Orion-Interest Betreff: Re: Settings for pooled datasources, timeout errors Hi Jens, interesting posting! I think You still could get the JDBC source

Re: Settings for pooled datasources, timeout errors

2001-03-09 Thread Falk Langhammer
Hi From: "Jens Stutte" [EMAIL PROTECTED] no, it is a SAP DB kernel problem. Does it mean this problem exists for R/3 installations - I mean they need a reboot after a couple of million SQL statements? Hard to believe! Do all SAP customers only have toy problems? ;-)) Never used Firebird

HELP: Settings for pooled datasources, timeout errors

2001-03-08 Thread Jens Stutte
Hello all, i have a problem with my datasource settings (timeout etc.). To give you a picture of my environment, i am using orion together with a SAP DB database and bean managed persistence (all under linux, orion 1.4.7, jdk 1.3.1 beta). My settings looked as follows: data-source

Re: HELP: Settings for pooled datasources, timeout errors

2001-03-08 Thread Robert Krueger
snip I'd like to know if i did not get something regarding the configuration of datasources and if others had problems with the timeout settings. Hi Jens, I believe your observations are correct and your not doing something wrong. We have also had a number of strange effects in that area

Re: Settings for pooled datasources, timeout errors

2001-03-08 Thread Falk Langhammer
Hi Jens, interesting posting! I think You still could get the JDBC source code (since it is open source now and there is a download option for it). Maybe, the bug is in jdbc, not the sapdb itself. Then You could fix it (maybe running a 36h debug session ;-) and post the fix. I mean, isn't it