AppServerProcess used as a processQueue service

I'm with Mike in that I think that a batch process is more suited towards queue processing. An appserver is more like having 'extra power', keeping away db connections from client processes and that sort of thing. Does not mean you couldn't do it I guess, but what makes you think an AS is the best solution for this? Multi threading?

Earlier I have used a window process or a batch process, but I was thinking that it could be easy implementing this kind of process. It is supposed to check a table for jobs, and run the job. I understand that it would be kind of wrong doing this, since the process is locked to one kind of task. I was just curious if it was possible. Either with a repeat: pause n. loop, or a wait-for with a pause n.

I would probably be bether of using a process runing as a window service.

We did something simular with an AS for the same reason. Except we ran our .p as part of the "Startup procedure" for the agent. The AS status was always in the "Starting" state, which didn't concern us. Like Goo, we had it scan a table for jobs to process. we got it to terminate by placing a spceific record in the table.

Not the best approach, but it avioded havng someone being responsible for maintaining scheduled tasks or services.

We used the AS for something similar. Basically, process spinning on JMSMessage table that was responsible for sending the messages to SonicMQ. Instead of our startup procedure calling the process on the same session it would connect to another AS broker and call the process ASYNC. This way the startup broker would show that it had started.

We recently toyed with a windows service that was responsible for starting/stopping an OE session via ZeroMQ. While this worked the OE session could not interact with the desktop as it was started from a windows service. This means that we were not able to use Notify Icons, etc.

 I understand that it would be kind of wrong doing this, since the process is locked to one kind of task.

You’ll get an application server in a ’starting’ state that will essentially just do the same thing you can do with a plain do loop in progress to start a number of batch processes, there are certainly better ways to use an application server especially if the number of licenses are scarce :)

Yep, we found that out the hard way. I believe in 11.7.2 something was added to allow for the same type of functionality. We discussed with Mike Jacobs and he has sent us a write up on it...just have not tried it yet.

No, and yes. Stop thinking about the AppServer processing the queue (BAD) and start thinking about the AppServer processing the queue message (GOOD).  I disagree with the consensus on batch mode, I like to integrate queue (and such) listeners into all sorts of things, including live console apps, so I design all my listeners (queue, socket, sonic, ... ) to be event driven. For times when it really is running in background, I use a headless UI wrapper.