I have a new application in a test mode at a few retail outlets.
The user opens a web page and creates transactions.
Under the covers I am using a single db2 profile for the connection to the System i. The connection happens as they open the application.
When multiple sites enter data at the same time it is getting crossed.
I use stored procedures that are executed when they click submit for new transactions or for updates.
This just hit and I thought I would ask here as my mind starts to digest and come up with ideas.
My initial ideas are they are all using the same profile and that is causing the issue. I would have expected each connection to be a separate session.
I do not want separate profiles, but could go that route as a last resort.
Any tips or leads would be appreciated.
The user opens a web page and creates transactions.
Under the covers I am using a single db2 profile for the connection to the System i. The connection happens as they open the application.
When multiple sites enter data at the same time it is getting crossed.
I use stored procedures that are executed when they click submit for new transactions or for updates.
This just hit and I thought I would ask here as my mind starts to digest and come up with ideas.
My initial ideas are they are all using the same profile and that is causing the issue. I would have expected each connection to be a separate session.
I do not want separate profiles, but could go that route as a last resort.
Any tips or leads would be appreciated.
Comment