During synchronization between client and server, one may see communications fail, usually resulting in a communication error 13 (in some rare instances 14). Investigating the Agentry Server log files may reveal a JCO error of unkown origin. Please note the actual error displayed here and on the client itself can be somewhat unpredictable. What needs to be done is to monitor the JVM to see if it is failing during transmit. If it is, review the JVM logs and determine if there is an error message that looks similar to:
Exception in thread "EventQueue-0" java.lang.OutOfMemoryError: Java heap space
Then this is the indicative that you are encountering an issue similar to this.
Note again, that the error message can change, but if at any point the JVM log states that it is out of memory in any capacity, this article is a good place to start addressing the issue.
Java heap error, JVM out of memory , KBA , java heap error , jvm out of memory , MOB-SYC-SAP , Syclo Mobility for SAP backend , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.