Web access job priority

["Clapham, Paul" <pclapham@xxxxxxxxxxxxx>]

We are running a web server (on a Windows NT box) that communicates with our
AS/400s via RMI.  Each AS/400 has several RMI server jobs running on it that
are responsible for controlling the data flow between the web server and the
AS/400 database.

I have a couple of questions, I think.  First of all, how should the server
jobs be configured?  At present they are configured as if they were batch
jobs (priority 50, time slice 2 seconds, and so on).  Since they usually
transfer relatively small amounts of data, should they be configured like
interactive jobs (priority 20) or somewhere between batch and interactive?

Second, the logs tell me that the first time a particular transaction is
executed after the server job starts, it takes several seconds (e.g. 20) to
complete, whereas subsequent instances of the same transaction take only
fractions of a second.  Presumably this has something to do with loading all
the classes for the first call; is there some way to deal with this?

PC2
+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---