3059695 - TCP/IP ports missing when supplying Java system to SLD

The TCP/IP port info (e.g. httpPort, p4Port and telnetPort etc.) is missing when a Java system is supplied to the SLD application.

You have collected raw traces from Note "1143398 - Recording SLD data supplier raw data" and the ports are missing in the collected payload too.


In the default traces of the supplying system you see one of these two types of exception:

Case1:

#BC-JAS-COR-CLS #kernel.sda#C000A02E594E01720000000F0000B1C0#318590350000000004#sap.com/tc~lm~itsam~ui~mainframe~wd#com.sap.engine.core.cluster.impl6.ClusterMonitorImpl.getAccessPoint(int, String)#ADMIN#254##2916BF2FA89611EBAD9B000012FD4D8E#2d92d0faa89611eba7a5000012fd4d8e##0#Thread[HTTP Worker [@2062422737],5,Dedicated_Application_Thread]#Plain##
org.w3c.www.protocol.http.HttpException: Peer certificate rejected by ChainVerifier
iaik.security.ssl.SSLCertificateException: Peer certificate rejected by ChainVerifier
at iaik.security.ssl.y.a(SourceFile:946)
at iaik.security.ssl.n.b(SourceFile:1081)
at iaik.security.ssl.n.a(SourceFile:1569)
at iaik.security.ssl.y.d(SourceFile:798)
at iaik.security.ssl.SSLTransport.startHandshake(SourceFile:592)
at iaik.security.ssl.SSLTransport.getOutputStream(SourceFile:671)
at iaik.security.ssl.SSLSocket.getOutputStream(SourceFile:412)
at org.w3c.www.protocol.http.HttpBasicConnection.a(SourceFile:463)
at org.w3c.www.protocol.http.HttpBasicServer.getConnection(SourceFile:449)
at org.w3c.www.protocol.http.HttpBasicServer.runRequest(SourceFile:1211)
at org.w3c.www.protocol.http.HttpManager.runRequest(SourceFile:1191)
at org.w3c.www.protocol.http.HttpURLConnection.connect0(SourceFile:343)
at org.w3c.www.protocol.http.HttpURLConnection.a(SourceFile:175)
at org.w3c.www.protocol.http.HttpURLConnection.getInputStream(SourceFile:571)
at com.sap.engine.httpdsrclient.protocols.instrumented.https.DSRHttpsURLConnection.getInputStream(DSRHttpsURLConnection.java:123)
at java.net.URL.openStream(URL.java:1119)
at com.sap.engine.core.cluster.impl6.ClusterMonitorImpl.getAccessPoint(ClusterMonitorImpl.java:168)
at com.sap.sldserv.data.GetJ2EEEngineInfo.getData(GetJ2EEEngineInfo.java:285)

• In this case the problem is with the HTTPS connection to the Message Server/Central Service Instance. Usually certificates are issued to the FQDN of the host, but in the DEFAULT.PFL of the system the Central Service Instance host is specified by its short name. 

Case2:

#BC-JAS-COR-CLS#kernel.sda#C0000A202E8C000A0000008E000021FE#712971350025323647##com.sap.engine.core.cluster.impl6.ClusterMonitorImpl.getAccessPoint(int, String)####F17AF2CB3CFA11EBCAC11458D057A120#f17af2cb3cfa11ebcac11458d057a120##0#Timeout Event Processor, id [1], invocation [219]#Plain##
java.io.IOException: Server returned HTTP response code: 504 for URL: http://example:8170/msgserver/text/logon

#Error#com.sap.engine.core.cluster.impl6.ClusterMonitorImpl#
#BC-JAS-COR-CLS#kernel.sda#C0000A202E8C000A0000008F000021FE#712971350025323647##com.sap.engine.core.cluster.impl6.ClusterMonitorImpl.getAccessPoint(int, String)####F17AF2CB3CFA11EBCAC11458D057A120#f17af2cb3cfa11ebcac11458d057a120##0#Timeout Event Processor, id [1], invocation [219]#Plain##
java.io.IOException: Server returned HTTP response code: 504 for URL: http://example:8170/msgserver/text/logon
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1876)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474)
at com.sap.engine.httpdsrclient.protocols.http.DSRHttpURLConnection.getInputStream(DSRHttpURLConnection.java:133)
at java.net.URL.openStream(URL.java:1072)
at com.sap.engine.core.cluster.impl6.ClusterMonitorImpl.getAccessPoint(ClusterMonitorImpl.java:168)
at com.sap.sldserv.data.GetJ2EEEngineInfo.getData(GetJ2EEEngineInfo.java:264)
at com.sap.sldserv.DataCollector.collectJ2EEData(DataCollector.java:467)
at com.sap.sldserv.DataCollector.timeout(DataCollector.java:245)
at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:83)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

• In this case the connection to the Message Server/Central Service Instance is prevented by a configured Proxy for outgoing requests. Note "1507174 - Proxy settings for the J2EE engine" could be applied on the system.
  The result on page <host>:<port>/proxy_setting.jsp will show the proxy configuration. Parameter 'http.nonProxyHosts' (or 'https.nonProxyHosts') shows which hosts will be bypassed by the proxy.
  Usually, the Central Service Instance host is included here by FQDN.
  And again, like in case 1, the Central Service Instance host is specified by its short name in DEFAULT.PFL.
  
  
  

• SAP Netweaver release independent;
• System Landscape Directory.

  Collect and send data, TCP/IP, ports, missing, empty, java system, httpPort, p4Port, telnetPort, payload, misleading,Peer certificate rejected by ChainVerifier. , KBA , BC-CCM-SLD , System Landscape Directory / Component Repository , BC-CCM-SLD-JAV , System Landscape Directory Java Client & Server , How To