Given that, you might try increasing the amount of time that alfserver waits before escalating to SIGKILL. One second is a long time for a process to be unresponsive. Try small increments, for example, in alfserver.ini change this line:
SetPref timerAlfserverSignalEscalation 3
Also, the log indicates that you are running the server as root, which would be ok if you were causing the actually-launched apps to run as a different user. I think you've got "AlfProcessOwnerConfig login root" set in your alfserver.ini ? There is a chance that the "login" mode is adding an extra layer of complexity to this issue.
Usually we suggest you run your alfserver in one of two modes:
mode A:
- run alfserver as root
- use "AlfProcessOwnerConfig setuid $dispatcherUser"
- set up env configuration in alfserver.ini
mode B:
- run alfserver as some other user (like create an "alfserver" account), with a well-defined operating environment
- use "AlfProcessOwnerConfig server" in alfserver.ini
The above is a quote from Pixar's replying to alfserver's configuration.