SAP Mobile Platform SDK Client (Agentry) slow transmit times
- Using Agentry system connection = SQL-SQLSystemConnection the commit database transaction shows:
User * is busy. Skipping keep alive message. Retry attempt in 1 second.
Note: This message is showing on events that the transmit is slow in a database server using SQL connection. If this message is not shown then the transmit is normal without issue.
- Issue may also show slower Complex Table synching wherein the following error may show up:
Java exception occurred: java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
- Due to slowness, the following error may also show up:
SAP Mobile Platform 3.0 SP 11
SAP Mobile Platform 3.0 SDK SP13 PL01 (Agentry client 184.108.40.206)
"SAP Mobile Platform Agentry client slow","Transmit slow with Agentry","Agentry transmit takes 1 second too long","SMP 3.0 Agentry backend server transmit slow","Oracle database transmit with Agentry slow","Users taking too long to transmit with Agentry","..\agentry\netmsg.cpp#280:NetMessage::respond","User * is busy. Skipping keep alive message. Retry attempt in 1 second","Java exception occurred: java.net.SocketException: Connection reset by peer: socket write error" , KBA , MOB-ONP-AGS , SAP Mobile On Premise Agentry Server , MOB-SYC-OTH , Syclo Mobility for other backend , MOB-SYC-IBM , Syclo Mobility for IBM backend , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.