francishsu
29th July 2002, 16:40
Running Baan IVc4 on HP-UX 11.00...
We have a C program that uses the Baan C interface to execute a function in a Baan DLL, which prints some Baan reports.
On our production server, the program will sometimes hang when the DLL calls spool.open(). When this happens, a zero length spool file is left. No fatal error gets generated, but we get the following list of the bshell processes running when the hanging occurs:
$ bshcmd6.1 -p -l -w 2 -u 4 23331
/baan/tmp/bshell.23331
$ cat /baan/tmp/bshell.23331
Received wakeup call
Command 1 (arg '') issued by user us10556
PID PPID PGRP SESSION TICKS FLAGS S CMP MEM
1 0 1 ottstpciserve 1248 00000010 S 150 243848
object: ottstpciserver
oic:
ottstpciserver
ottstp_stddll
otcmcsdllo410
2 0 2 ottstpstdlib 1059 00020000 S 000 235384
object: ottstpstdlib
oic:
ottstpstdlib
6 1 1 ttstpsplopen 1193 00000000 R 150 272360
object: ttstpsplopen
oic:
ottstpsplopen
ottstp_stddll
ottstpstandard
forms:
fttstpsplopen
fttstpsplopen2
fttstpsplopen3
fttstpsplopen4
Baan support has not been able to reproduce our problem in their environment. We have installed the latest portingset, standard and splopen/close solutions for them to no avail. So I am getting desperate, and wondering if anyone has any insight as to what might be happening.
The hanging occurs on roughly 1% of the spool.open() calls, and the frequency of the hanging might be related to server load (e.g. hangs more often during peak usage). So it has been very diffulcult to reproduce in a test environment, although I have been successful in doing so. Another interesting fact is that the DLL opens and closes the spooler multiple times, but the hanging always occurs on the first spool.open call in the DLL. That is, if the first call succeeeds, the DLL will not hang for the rest of the spool.open calls.
I welcome any ideas!
Thanks,
Francis
We have a C program that uses the Baan C interface to execute a function in a Baan DLL, which prints some Baan reports.
On our production server, the program will sometimes hang when the DLL calls spool.open(). When this happens, a zero length spool file is left. No fatal error gets generated, but we get the following list of the bshell processes running when the hanging occurs:
$ bshcmd6.1 -p -l -w 2 -u 4 23331
/baan/tmp/bshell.23331
$ cat /baan/tmp/bshell.23331
Received wakeup call
Command 1 (arg '') issued by user us10556
PID PPID PGRP SESSION TICKS FLAGS S CMP MEM
1 0 1 ottstpciserve 1248 00000010 S 150 243848
object: ottstpciserver
oic:
ottstpciserver
ottstp_stddll
otcmcsdllo410
2 0 2 ottstpstdlib 1059 00020000 S 000 235384
object: ottstpstdlib
oic:
ottstpstdlib
6 1 1 ttstpsplopen 1193 00000000 R 150 272360
object: ttstpsplopen
oic:
ottstpsplopen
ottstp_stddll
ottstpstandard
forms:
fttstpsplopen
fttstpsplopen2
fttstpsplopen3
fttstpsplopen4
Baan support has not been able to reproduce our problem in their environment. We have installed the latest portingset, standard and splopen/close solutions for them to no avail. So I am getting desperate, and wondering if anyone has any insight as to what might be happening.
The hanging occurs on roughly 1% of the spool.open() calls, and the frequency of the hanging might be related to server load (e.g. hangs more often during peak usage). So it has been very diffulcult to reproduce in a test environment, although I have been successful in doing so. Another interesting fact is that the DLL opens and closes the spooler multiple times, but the hanging always occurs on the first spool.open call in the DLL. That is, if the first call succeeeds, the DLL will not hang for the rest of the spool.open calls.
I welcome any ideas!
Thanks,
Francis