This content has been marked as final. Show 6 replies
Is the job stopped everytime after processing exactly 3000 users or is it randomly stopping after some users being processed.
Is it stopping exactly after specific time for each run?
There is no defined users count after which job is stopping nor time .
But in mostly all cases job executed for 7 mins and some seconds (except 1-2 times)
So, it stops for every 7 mins and some sec - 400+ seconds.
The exception should have been logged in <oim_server1>.out file.
Also, Could you please check the transaction timeout parameter in your application server configuration.
Edited by: Vamsi Krishna on 21-Mar-2013 05:53
There are no errors seen for connection timeout in logs (both connector server and oimdiagnostic and oimserver.ou1) .In my weblogic->services->JTa timeout session is 600 seconds
8*60=480 seconds < 600 seconds .
No i cannot see any error in logs checked OIMDiagnostic logs , oimserver.out and connector server.log file .
In my weblogic console->services->JTA ->timeout =600 seconds.
My job is running for less tham 8 mins and 8*60=480 second <600 seconds
Check the connector server load when you are running the recon. Last time I checked the connector, the way it was written is that it loads all the users from AD into the connector server memory and then sends them to OIM. So if the number was huge, then the connector server errored out and did not send data to OIM. We then did recon based on OUs to load/link all the users into OIM. Check the connector server system logs and check for memory usage etc.