When executing our PowerBuilder EXE under a Window's service, timer events appear to stop running as expected and the application hangs because no more code is executed. This hang may occur shortly after launching the EXE or may take hours to appear. Our only recourse is to kill the Window's process and start a new one. We have experienced this issue since PB11.5 and continue to under PB17. Our workaround is to return to running our EXE in the foreground, which requires a user logged into the server at all times.
-
stewart gutoff
- PowerBuilder
- Friday, 16 February 2018 15:59 PM UTC
Comment
- stewart gutoff
- Friday, 16 February 2018 21:05 PM UTC
Chris,
We run PBNIServ.exe; our service app starts up multiple simultaneous instances of our EXE, which is an interactive user app that is unaltered except that our response windows are opened with a countdown timer.
Thanks,
Stew
We run PBNIServ.exe; our service app starts up multiple simultaneous instances of our EXE, which is an interactive user app that is unaltered except that our response windows are opened with a countdown timer.
Thanks,
Stew
- Chris Pollach @Appeon
- Friday, 16 February 2018 21:35 PM UTC
Hi Stewart;
You'll have to contact the author of PBNISEV and see if they can help you.
Personally, I have been using NSSM for my MS-Windows Service Apps for about a decade. Don't let the name fool you - its a serious utility .. and its free.
HTH
Regards ... Chris
You'll have to contact the author of PBNISEV and see if they can help you.
Personally, I have been using NSSM for my MS-Windows Service Apps for about a decade. Don't let the name fool you - its a serious utility .. and its free.
HTH
Regards ... Chris
- stewart gutoff
- Thursday, 22 February 2018 22:02 PM UTC
Chris,
Some more context .. As mentioned previously, our program uses PBNISERV to run a service which is a scheduler, which starts single-purpose, non-interactive instances of the executable (our issue isn't with this scheduler that is running as a Service). It's with the instances that get kicked off by the scheduler. Each instance is dedicated to one job, ex. printing a report; printing a batch of reports; running an HL7 interface, etc. They know they are running as Windows services but do open windows, even response windows (but with timeouts, so they will automatically close). We’ve found that on some servers, when the Agent Service starts multiple, simultaneous instances of the executable, one instance will hang (over time).
Some more context .. As mentioned previously, our program uses PBNISERV to run a service which is a scheduler, which starts single-purpose, non-interactive instances of the executable (our issue isn't with this scheduler that is running as a Service). It's with the instances that get kicked off by the scheduler. Each instance is dedicated to one job, ex. printing a report; printing a batch of reports; running an HL7 interface, etc. They know they are running as Windows services but do open windows, even response windows (but with timeouts, so they will automatically close). We’ve found that on some servers, when the Agent Service starts multiple, simultaneous instances of the executable, one instance will hang (over time).
There are no comments made yet.
Comment
- stewart gutoff
- Friday, 16 February 2018 21:02 PM UTC
Roland,
Thanks for the feedback. We'll give it a try.
Stew
Thanks for the feedback. We'll give it a try.
Stew
There are no comments made yet.
- Page :
- 1
There are no replies made for this question yet.
However, you are not allowed to reply to this question.
However, you are not allowed to reply to this question.
Some more context .. As mentioned previously, our program uses PBNISERV to run a service which is a scheduler, which starts single-purpose, non-interactive instances of the executable. Each instance is dedicated to one job, ex. printing a report; printing a batch of reports; running an HL7 interface, etc. They know they are running as Windows services but do open windows, even response windows (but with timeouts, so they will automatically close). We’ve found that on some servers, when the Agent Service starts multiple, simultaneous instances of the executable, one instance will hang (over time).