on 12-21-2015 7:39 PM
Hi Experts,
We are using SMP 3.0 sp09.
After the upgrade the when ever the production user are downloading the equipment complex table they are getting SMP Server error "Unexpected Disconnection from Server error (11)" in the client. The time out is happening exactly twenty minutes.
When we see the server logs this is the exception error we are getting.
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294########logException::Exception: com.sap.conn.jco.JCoRuntimeException: (132) JCO_ERROR_CONCURRENT_CALL: The context with the session id [session-53]
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294########logException::COM.SAP.CONN.JCO.JCORUNTIMEEXCEPTION: (132) JCO_ERROR_CONCURRENT_CALL: THE CONTEXT WITH THE SESSION ID [SESSION-53] SCOPE TYPE
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT COM.SAP.CONN.JCO.RT.CONTEXT.CHECKBUSY(CONTEXT.JAVA:635) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT COM.SAP.CONN.JCO.RT.CONTEXT.GETCONNECTION(CONTEXT.JAVA:153) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT COM.SAP.CONN.JCO.RT.RFCDESTINATION.EXECUTE(RFCDESTINATION.JAVA:1464) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT COM.SAP.CONN.JCO.RT.RFCDESTINATION.EXECUTE(RFCDESTINATION.JAVA:1435) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT COM.SAP.CONN.JCO.RT.ABAPFUNCTION.EXECUTE(ABAPFUNCTION.JAVA:300) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT COM.SYCLO.SAP.JCO.JCO3CONNECTION.EXECUTE(JCO3CONNECTION.JAVA:158) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT COM.SYCLO.SAP.BAPI.BAPI.EXECUTE(BAPI.JAVA:361) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT COM.SYCLO.SAP.BAPI.BAPI.RUN(BAPI.JAVA:252) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT COM.SYCLO.SAP.SESSIONMANAGER.DELETEREMOTEUSER(SESSIONMANAGER.JAVA:172) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT COM.SYCLO.SAP.SESSIONMANAGER.CLOSESESSION(SESSIONMANAGER.JAVA:139) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT COM.SYCLO.SAP.USER.CLOSESESSION(USER.JAVA:894) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT COM.SYCLO.SAP.USER.LOGGEDOUT(USER.JAVA:1156) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT COM.SAP.MOBILE.PLATFORM.SERVER.AGENTRY.IMPL.SERVERJAVA.NATIVEPROCESSCLUSTERMESSAGERECEIVERUSERLOGIN(NATIVE METHOD) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT COM.SAP.MOBILE.PLATFORM.SERVER.AGENTRY.IMPL.SERVERJAVA.PROCESSCLUSTERMESSAGERECEIVERUSERLOGIN(SERVERJAVA.JAVA:160) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT COM.SAP.MOBILE.PLATFORM.SERVER.AGENTRY.CLUSTER.CLUSTERMESSAGERECEIVERUSERLOGIN.PROCESSMESSAGE(CLUSTERMESSAGERECEIVERUSERLOGIN.JAVA:49) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT COM.SAP.MOBILE.PLATFORM.SERVER.CLUSTER.SERVICE.IMPL.CLUSTERCOMMUNICATIONSJGROUPIMPL.RECEIVE(CLUSTERCOMMUNICATIONSJGROUPIMPL.JAVA:96) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT ORG.JGROUPS.JCHANNEL.UP(JCHANNEL.JAVA:738) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT ORG.JGROUPS.STACK.PROTOCOLSTACK.UP(PROTOCOLSTACK.JAVA:1019) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT ORG.JGROUPS.STACK.PROTOCOL.UP(PROTOCOL.JAVA:409) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT ORG.JGROUPS.PROTOCOLS.FRAG2.UP(FRAG2.JAVA:182) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT ORG.JGROUPS.PROTOCOLS.FLOWCONTROL.UP(FLOWCONTROL.JAVA:434) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT ORG.JGROUPS.STACK.PROTOCOL.UP(PROTOCOL.JAVA:409) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT ORG.JGROUPS.PROTOCOLS.ENCRYPT.UP(ENCRYPT.JAVA:516) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT ORG.JGROUPS.PROTOCOLS.PBCAST.STABLE.UP(STABLE.JAVA:294) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT ORG.JGROUPS.PROTOCOLS.UNICAST3.UP(UNICAST3.JAVA:423) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT ORG.JGROUPS.PROTOCOLS.PBCAST.NAKACK2.REMOVEANDPASSUP(NAKACK2.JAVA:876) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT ORG.JGROUPS.PROTOCOLS.PBCAST.NAKACK2.HANDLEMESSAGES(NAKACK2.JAVA:831) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT ORG.JGROUPS.PROTOCOLS.PBCAST.NAKACK2.UP(NAKACK2.JAVA:655) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT ORG.JGROUPS.PROTOCOLS.BARRIER.UP(BARRIER.JAVA:132) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT ORG.JGROUPS.STACK.PROTOCOL.UP(PROTOCOL.JAVA:409) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT ORG.JGROUPS.PROTOCOLS.FD.UP(FD.JAVA:274) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT ORG.JGROUPS.STACK.PROTOCOL.UP(PROTOCOL.JAVA:409) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT ORG.JGROUPS.PROTOCOLS.MERGE2.UP(MERGE2.JAVA:226) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT ORG.JGROUPS.STACK.PROTOCOL.UP(PROTOCOL.JAVA:409) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT ORG.JGROUPS.PROTOCOLS.TP.PASSBATCHUP(TP.JAVA:1422) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT ORG.JGROUPS.PROTOCOLS.TP$BATCHHANDLER.RUN(TP.JAVA:1574) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT JAVA.UTIL.CONCURRENT.THREADPOOLEXECUTOR.RUNWORKER(THREADPOOLEXECUTOR.JAVA:1142) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT JAVA.UTIL.CONCURRENT.THREADPOOLEXECUTOR$WORKER.RUN(THREADPOOLEXECUTOR.JAVA:617) |
#INFO#System.out###Incoming-1,sapmppdb1-1521-MPP-gomobile:com.sap.mobile.platform.server.agentry.userlogin,sapmppap01-1294######## AT JAVA.LANG.THREAD.RUN(THREAD.JAVA:812) |
Message logs.
S, 622, 20, 28, 12/21/2015 10:46:30, 67,12814909, 1677, jkw0, ANGEL: 5FA5FF4C-B16F-4F8B-82FB-BC2B7D4CACF3
R, 622, 20, 28, 12/21/2015 10:46:30, 0,12814909, 1679, jkw0, ANGEL: 5FA5FF4C-B16F-4F8B-82FB-BC2B7D4CACF3
O, 5, 1, 26, 12/21/2015 11:06:30, , 0, 0, jkw0, >unknown<
T, 5, 1, 26, 12/21/2015 11:06:30, , 0, 0, jkw0, >unknown<
F, 5, 1, 26, 12/21/2015 11:06:30, , 0, 0, jkw0, >unknown<
C, 622, 20, 28, 12/21/2015 11:12:12, ,12890156, 1679, jkw0, >unknown<
Any help from the experts is very much appreciated.
I suspect that your connection is being timed out somewhere on the network (Router, Firewall, etc). Check with your networking team to see if that might be the case. You can also try testing from the server itself to try and eliminate some of the network but unless you also change the certificate to be localhost you would probably still be going out on the network.
The one Agentry area you can also look at is to increase the Server Inactive Timeout setting in the cockpit in case that is triggering it.
--Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bill,
Thanks for the quick reply.
It is not failing for all the users. This is happening for two or three users and others were able to sync successfully. We have set the SMP Server Inactive Timeout as 22 mins. and the Angel transmission Inactive timeout as 19 mins and 59 seconds. and the timeout is happening only during CTEquipment download.
I tried with the same user in my local server. He was able to sync successfully. The local server is 3.0 and SP08
Any help is much appreciated.
Hi,
Would you check the memory space of SMP server where you are getting this error, there is a possibility of not having enough space hence it doesn't proceed with complex table sync.
Since there is a memory space in your local server, the sync is going through.
You can try deleting some unwanted logs from SMP server directory and see whether it proceeds further or not. or may be you can disable unwanted complex tables and check whether sync goes through or not.
Regards,
Abhishek Wajge
Balamurgan,
If you have a huge amount of data coming from SAP as part of complex table this error will come. can you please check in SAP how long it is taking to execute equipment, floc ct table? if it is taking long time to execute then you have to prevent this table to get download.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ajitesh,
We are able to overcome the challenge of fetching data from SAP using staging concept. We see inn the SMP server log that 750K records are fetched in the packet size of 100,000 but when it tries to calculate the index before sending data to device and while doing this process it times out when its exactly 30 minutes.
In talking with some of the Engineering folks, during the initial sync the transmit configurations are not yet active so there is a default timeout used which they believe is 30 minutes and would explain the behavior you are seeing.
One thought would be to disable that table to complete the initial sync and then enable it for the second sync where the transmit config timeouts will then be in effect and allow for the additional time needed.
Perhaps you can create a pre-built client with the data already loaded to avoid this for your users on their initial sync.
--Bill
Are you connecting directly to the SMP server or going through a proxy or load balancer?
We also see this issue when the load balancer/proxy is timing out the connection. Be sure to take that into account as well.
--Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are connecting directly to SMP server and not using proxy or load balancer. Currently, we are connecting using Windows Agentry Client and within the network(no VPN/no Wi-Fi). We see the same error on iOS device as well and consistently after 30 minutes.
What is the maximum volume that you have seen other customers were able to download for the equipment complex table ?
Hi,
Please increase your JCO time out and no. of pooled shared connections.
How many equipments you have in SAP?
we are dealing with more than 7 millions equipments, we could able to download to mobile.
Thanks,
Sudhir.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Bill,
Thanks for the reply, as per the business requirement, we have already applied all the filters. After applying the filters business requirement is to view all 750k equipments on device. Hence, looking out for the option of downloading 75k equipments on device. We are able to get all the data from SAP back end but when SMP server is trying to send equipments to device, we are getting the server error(11) exactly after 30 minutes. We have already increased all the timeout settings, no luck yet.
Any suggestions ?
-Vishal.
Hi Vishal,
Please look into this SAP note given by Mark Pe.
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
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.