SAP Knowledge Base Article - Preview

2311864 - PI ESR connection to server lost when editing large objects


  • You are working with large objects in the Process Integration (PI) or Process Orchestration (PO) Enterprise Services Repository (ESR)
  • This could involve editing, saving, activating, opening etc the objects
  • The error below is thrown:
    Connection Interrupted
    Connection to server lost
    You can log on again once the server is available again

    Connection to server lost.png

  • In the defaultTrace file you may notice an entry similar to below:

    #2.0#2016 01 31[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]#Plain##
    System exception
    javax.ejb.EJBException: ASJ.ejb.005043 (Failed in component:, BC-XI-IBD) Exception raised from invocation of public void com.idsscheer.aris.cltech.common.ejb.aris.ILoginContextBean.terminateDbSession(java.lang.String,long) method on bean instance com.idsscheer.aris.cltech.common.ejb.aris.ILoginContextBean@15892ag2for bean*xml|aris-ejb.jar*xml|aris.ILoginContextBean in application; nested exception is: The server is not properly initialized (the bean implementation is null) The server is not properly initialized (the bean implementation is null)
     at com.idsscheer.aris.cltech.common.ejb.aris.ILoginContextBean._delegate(
     at com.idsscheer.aris.cltech.common.ejb.aris.ILoginContextBean.terminateDbSession(
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  • If you run a Java Console trace as per SAP KBA 1891480 How to enable logging in Java WebStart console, you will find a stacktrace similar to below:

    #21:34:59 [AWT-EventQueue-2] ERROR MessageID=IBF.lib_gui.007593#Failed to initialize Exception Dialog
    Thrown: Logon terminated
    ...Caused by: Unexpected exception
    ...Caused by: No alive connection. Check state of the server
  • In the dev_icm trace file, you see an entry similar to below:

    [Thr 18086] *** ERROR => NiIShutdownHandle: SiShutdown failed for hdl 206/sock 4791
        (SI_ESYSCALL/10054; I4; ST) [nixxi.cpp    4879]
    [Thr 15489] Jan 31 21:35:21 2016
    [Thr 15489] *** WARNING => P4RecvRequest(id=10/4558): fatal message length: 27355809 (max: 12582912) [p4_plg.c     1843]
    [Thr 15489] *** WARNING => P4PlugInReadHandler(id=10/4558): P4RecvRequest failed: Protocol error(-21) [p4_plg.c     1719]
  • In a Java console log, you may see the below error: Connection to system REPOSITORY using application REPOSITORY lost. Detailed information: Error accessing " http://server:port/rep/query/int?container=any" with user "PIDIR<SID>". Response code is 500, response message is "Internal Server Error"



  • PI Release Independent
  • SAP NetWeaver
  • SAP Process Integration


SAP NetWeaver all versions ; SAP Process Integration all versions


Process Integration 7.0, PI 7.0, PI 7.01, PI 7.02, Process Integration 7.10, PI 7.10, Process Integration 7.11, PI 7.11, Process Integration 7.30, PI 7.30, Process Integration 7.31, PI 7.31, Process Orchestration 7.4, PI 7.4, PO 7.4, Process Orchestration 7.5, PI 7.5, PO 7.5, NetWeaver, XI, Business System, Integration Process, Communication Channel, Receiver Determination, Interface Determination, Sender Agreement, Receiver Agreement, BPM, Business Process Model, Message Mapping, Operation Mapping , KBA , BC-XI-IBD , Integration Builder - Design , BC-XI-IBC , Integration Builder - Configuration , Problem

About this page

This 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.