Hi Thomas, In case it's importlant, I an rumming 7.0.3.25 on RedHat 7.3. I had hacked together a special version (a bit ugly) to do these tests and I have make a special tarball at:
http://www.osdl.org/archive/markw/sapdb/dbt2-0.5standalone.tar.gz Here's a list of steps that will hopefully get you running: 1. build the source a. 'make' in dbt2/ b. 'make -f Makefile.standalone clean' in dbt2/client/ then 'make -f Makefile.standalone' c. 'make -f Makefile.standalone clean' in dbt2/terminal/ then 'make -f Makefile.standalone' 2. edit build scripts a. edit dbt2/scripts/sapdb/db_setup_sample.sh line 15: ./datagen -w $WAREHOUSES -d /tmp/data change '/tmp/data' to where you want data files to be generated b. edit dbt2/scripts/sapdb/create_db_sample.sh for all the database parameters 3. database setup a. cd 'dbt2/scripts/sapdb/' b. execute 'db_setup_sample.sh 1' this will build the database and load it. 4. running my test a. cd 'dbt2/terminal' b. execute example: './sdriver -wmin 1 -wmax 1 -w 1 -ktd 0 -ktn 0 -kto 0 -ktp 0 -kts 0 -ttd 0 -ttn 0 -tto 0 -ttp 0 -tts 0 -q 0 -r 0 -e 0 -t 0 -dbname dev8-004:DBT2 -tpw 3 -l 60' summary of the flags that you may need to change: -dbname <odbc data source name> -tpw # where # is the number of threads started. must be <= 10, hopefully you can reproduce the problem with 4 or 5, as I do. notes: This will make stored procedure calls only to storedproc/sapdb/new_order.sql, in case you want to take a look at that. The output from sdriver to stdout it not useful when the application is executed in this way. Something you may find helpful is the output to the file mix.log. The format of it is "time(),transaction,response time,pthread_self()", which I use to see which threads are doing anything. Let me know if you have any questions. Thanks, Mark On Wed, 2002-09-18 at 01:51, Koetter, Thomas Theodor wrote: > Hi Mark > > > -----Original Message----- > > From: Mark Wong [mailto:[EMAIL PROTECTED]] > > Sent: Dienstag, 17. September 2002 20:27 > [snip] > > I have a situation where I see some number of threads in a > > multi-threaded ODBC program waiting in libc_recv. I have used gdb to > > attach to my program and produce a back trace, which is copied at the > > end of the message. > > > > The issue is fairly easy to reproduce by having only a 4 or 5 threads > > repeatedly call a stored procedure in a tight loop. I can > > provide more > > information if it will help. > > Yes, more info in order to reproduce the behaviour is very welcomed. > Please send me all I need to run into this problem at our site. > It seems that the thread-handling is not proper working, at least > under Linux. > > TIA Thomas > > > ---------------------------------------------- > Dr. Thomas K�tter > SAP DB, SAP Labs Berlin > > > SAP DB is open source. Get it! www.sapdb.org > > > -- Mark Wong - - [EMAIL PROTECTED] Open Source Development Lab Inc - A non-profit corporation 15275 SW Koll Parkway - Suite H - Beaverton OR, 97006 (503)-626-2455 x 32 (office) (503)-626-2436 (fax) http://www.osdl.org/archive/markw/ _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
