We are developing a Java API which reads/pulls incidents from DLP Vontu (v 14.5)and writes in to another system. When ever we start that API our vontu system gets overloaded and start giving authentication errors. (Unable to authenticate user) if API is stopped there is no such error in system and users are able to login. I am trying to understand what wrong we are doing here:
Follwing is the sequence of task which API performs:
A) Put web service request getIncidentList() with Get Connection to Vontu using (username, pwd) --> To retrive list of incidents in particular report (usually 50 to 100)
Then for each incidenst in report following actions are performed (parallelly for 5 incidents using threads with same username password):
1) Put web service request updateIncidentCustomAttributes with Get Connection to Vontu using (username, pwd) --> To change one custom attribute to mark transfer in progress.
2) Put web service request getIncidentDetails() with Get Connection to Vontu using (username, pwd)
3) Put web service request getIncidentBinaries() with Get Connection to Vontu using (username, pwd) --> To retrive attachments
4) Put web service request getIncidentViolations with Get Connection to Vontu using (username, pwd)
5) Put web service request updateIncidentCustomAttributes with Get Connection to Vontu using (username, pwd) --> To change one custom attribute to mark transfer is completed.
Activity 1 to 5 happends for each incidnet and 5 incidents in parallel (at same time). I want to understand if using same username and password and loggin in before each request is right approach or not ? Does vontu support multi threading using session token ? i.e. if I create one session token at the start of my request and use same to do for all above activities till the time token is valid will that help in this case ?
.
