SujithKumar
20th November 2007, 22:44
We are facing a problem with orphan baan processes on the server. These process leave orphan connection on the server and the database, sucking up memory and other resources
To be precise, we use vertex as tax software, integrated to Baan. When ever baan makes a call to vertex, it uses an excutable api.exe. This executable is started on the server. In normal situations when the user log out of baan api.exe proces is terminated. All fine!
However, if the user connection is lost (this happens some times, laptop user pull their latop out with an open baan connection. Also it can happen with any glitch in network). At this point ntbshell.exe is terminated also sh_server.exe is terminated , but the associated api.exe is not terminated and sits there as orphan, sucking up system resources
If any of you faced this problem? Any ideas? or point me in some direction?
I was wondering if there is some utilities avialable, which can run on the server and periodically look for orphan and kill them??
Even if you are not using vertex, any ideas in this direction would help
Thanks much
To be precise, we use vertex as tax software, integrated to Baan. When ever baan makes a call to vertex, it uses an excutable api.exe. This executable is started on the server. In normal situations when the user log out of baan api.exe proces is terminated. All fine!
However, if the user connection is lost (this happens some times, laptop user pull their latop out with an open baan connection. Also it can happen with any glitch in network). At this point ntbshell.exe is terminated also sh_server.exe is terminated , but the associated api.exe is not terminated and sits there as orphan, sucking up system resources
If any of you faced this problem? Any ideas? or point me in some direction?
I was wondering if there is some utilities avialable, which can run on the server and periodically look for orphan and kill them??
Even if you are not using vertex, any ideas in this direction would help
Thanks much