SAP Knowledge Base Article - Preview

1925352 - Check P4 port/access points being used by a live SAP JAVA server


The aim of this document is to specify the options available to SAP system administrators have check the access points (or ports) being used by a live SAP application server java engine.
This is particularly useful in cases where the default traces are populated with errors like:

javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is Connection to <hostname>:50004 is closed]
Caused by: Connection to <hostname> : <P4 port> is closed url=<hostname>: 50004 protocol=p4 (None); Reason: Check if server is started, access point for the protocol is available, and IP/Host name is accessible on network.] Caused by: Cannot establish connection with any of the available profiles: url= <hostname> : <P4 port> protocol=p4 (None); Reason:



  • Release Independent
  • SAP NetWeaver


SAP Composition Environment all versions ; SAP NetWeaver all versions ; SAP Process Integration all versions ; SAP Solution Manager all versions


SAP Management Console SAPMMC ,SAP Production ERP SRM CRM ERP PPM SEM APO XI PI PORTAL issue access points LSP command sapcontrol -function GetAccessPointList msgserver/text/logon?version=1.2,,,,,access point for the protocol is available, telnet not working, message server, -334,-333,-335 , KBA , kde , BC-JAS-ADM-MON , Monitoring , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , 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.