Using the JT Open connection in java to have one job for each user on the AS400

[emo]

Hi,
We have a JSF project (java) and we are making connections to a AS400 using the connections from JT Open.
We are NOT using the connection pooling because we want that every request from one user appears in its own job and joblog.
But apparently sometimes requests from one user are executed by the job of an other user and that can give some strange results on the Java side.

At logon time we create a connection which is re-used through the whole application. Is it maybe a parameter in our WAS server that controles this? Or someting on the AS400 itselfs that needs to be set properly? Or has it to do something with the garbage collection of the JVM which didn't took place before connecting with the new user?

Thanks already in advance for your help

[kpmac]

Re: Using the JT Open connection in java to have one job for each user on the AS400

Where are you storing the connection? Are you storing the connection in the session or the servlet?

l

[emo]

Re: Using the JT Open connection in java to have one job for each user on the AS400

The connection is stored in the session

[emo]

Re: Using the JT Open connection in java to have one job for each user on the AS400

It is at the moment that we execute the automatic generated PCML code
that in the *pgm*Services Bean two AS400 connection objects exists in the _programCallCommand = WebIntProgramCall


(1) one in the _connSpec = AS400ConnectionSpec
(2) one in the _pgmcallCmd = ProgramCallCommand --> and it is this object
that contains the data of the first user who logged in and executed an
invoke to a pgm

The first contains the logon info of the user that logged in on this IE session.
The second contains the logon data of the first user who logged in and executed an invoke to a rpg pgm. This is the user that logged in as first on an other IE session on the same PC using the internal test environment WAS V6.0 in WDSC V6