2508032 - Agentry 0 byte logs created with new application defined - crashes SMP 3.0 server

• On creating an Agentry application in the SAP Mobile Platform 3.0 cockpit, the SMP server/log/agentry folder produces 0 byte logs
• The SMP 3.0 continues to produce these 0 byte logs until the server crashes or dies 
• Some of the errors that are seen in the logs:
  
  ~~~~~~~~~Error 1~~~~~~~~~~~
  

  2017 05 23 16:06:54#0-500#ERROR#com.sap.espmprocessing.util.DataLoader###Start Level Event Dispatcher#########Exception occured java.lang.NullPointerException: while trying to invoke the method javax.persistence.EntityManager.getTransaction() of a null object loaded from local variable 'em'

  at com.sap.espmprocessing.util.DataLoader.loadCustomers(DataLoader.java:92)

  at com.sap.espmprocessing.util.DataLoader.loadData(DataLoader.java:426)

  at com.sap.espmprocessing.util.Activator.start(Activator.java:52)

  at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)

  at java.security.AccessController.doPrivileged(Native Method)

  at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
  
  ~~~~~~~~Error 2~~~~~~~~~~~~~
  
  

  2017 05 17 11:57:20#0-500#ERROR#System.err###Start Level Event Dispatcher#########SLF4J: The following logge

  rs will not work because they were created |

  2017 05 17 11:57:20#0-500#ERROR#System.err###Start Level Event Dispatcher#########SLF4J: during the default

  configuration phase of the underlying logging system. |

  2017 05 17 11:57:20#0-500#ERROR#System.err###Start Level Event Dispatcher#########SLF4J: See also http://www

  .slf4j.org/codes.html#substituteLogger |

  2017 05 17 11:57:20#0-500#ERROR#System.err###Start Level Event Dispatcher#########SLF4J: System.out |
  
  ~~~~~~~Error N~~~~~~~~~~~~~~
  
  The error could be just a lot of errors from different business logic problems from different users and overloaded the system:
  
  Example of different types of errors:
  
  - Authentication issue (like SSO or invalid users or expired users or unauthorized users)
  - Transaction issue (problem with the transactions that the backend dislikes)
  - and others

• SAP Work Manager 6.4.1
• SAP Mobile Platform 3.0 SP12 PL04

"Agentry 0 bytes","SMP 3.0 server crashing","Cannot publish Work Manager","SMP Agentry publish cannot work","No logs seen in Agentry","DEV DEF LOAD 0 bytes" , KBA , MOB-ONP-AGS , SAP Mobile On Premise Agentry Server , MOB-SYC-SAP , Syclo Mobility for SAP backend , Problem