on 01-23-2015 9:14 AM
Hi;
We are experiencing very long synchronization times, longer than the normal times. This is on a customised version of the standard SAP Work Manager 6.0. Our environment is on SMP 2.3 SP4 PL1 and the Agentry client version is v6.1.4.443. When going through the logs, we see the following exceptions :
- com.syclo.agentry.BusinessLogicException: Concurrent call. Connection currently used in another thread
- User 'XXXXXX' is busy. Skipping keep alive message. Retry attempt in 1 second.
What could possibly be causing these long sync times?
Much appreciated!
Thanks and Regards;
Sizo Ndlovu
Hi,
in one of the latest releases, the logging behavior has changed (every line is flushed I think). Try to set your log level to "fatal". (I do not recall that particular error message but we also had extremely long sync times.)
Regards, Daniel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
You could verify the delta sync - transmit window - where its taking long time, from the logs I could see the update (ZQM_UPD_INSP_ORDERS_BAPI) is keep on trying eg: from 2015/01/26 08:05:11.615 till 2015/01/26 08:13:22.156 and then its throwing the exception
"+ BackEnd=Java-1
2015/01/26 08:13:22.158: Exception while running transaction update step for step '': Java Business Logic Error: com.syclo.agentry.BusinessLogicException: InspectionPointUpdateSteplet - Concurrent call. Connection currently used in another thread".
Thanks
Resmi
Sizo,
Please attach a user transmit log so we can look for the bottlenecks.
Jason latko - Senior Product Developer at SAP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.