Showing results for 
Search instead for 
Did you mean: 

WARNING: cannot determine PID of process using port 8443

Former Member
0 Kudos

I recently installed and configured HCC successfully. Everything was working great.

After a reboot, I see the following:

C:\SAP\scc20>"java" -server  "

tils.PropertyDigester" "-XX:+HeapDumpOnOutOfMemoryError" "-XX:+DisableExplicitGC" "-Xms512m" "-Xmx10

24m" "-XX:PermSize=256M" "-XX:MaxPermSize=256M" "-Dosgi.requiredJavaVersion=1.6" "-Dosgi.install.are

a=." "-DuseNaming=osgi" "-Dorg.eclipse.equinox.simpleconfigurator.exclusiveInstallation=false" "-Dco" "-Declipse.ignoreApp=true" "-Dosgi.noShutdown=true" "-Dosgi.framework.a

ctiveThreadType=normal" "-Dosgi.embedded.cleanupOnSave=true" "-Dosgi.usesLimit=30" "-Djava.awt.headl

ess=true"  -jar plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar  -console

osgi> ERROR: shell command for retrieving PID of process bound to SCC port failed -- java.lang.NullP


WARNING: cannot determine PID of process using port 8443

ERROR: checking SAP HANA Cloud Connector on port 8443 failed -- org.apache.http.conn.HttpHostConnect

Exception: Connection to https://localhost:8443 refused

ERROR: stopping SAP HANA Cloud Connector since port 8443 appears to be used by another process

I've done a netstat but cannot find any other processes that are running on port 8443.

I'm running windows 7 SP1.

Any suggestions appreciated.

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos


I had the same issue!

In the ljs_trace.log (/opt/sap/scc/log/ljs_trace.log) I found following error :

2015-03-18 15:21:11,096#ERROR#org.apache.coyote.http11.Http11Protocol#Start Level Event Dispatcher#          #Failed to initialize end point associated with ProtocolHandler ["http-bio-8443"] Cannot recover key

I deleted the tomcat key in the keystore and recreated it, and then I was able to start the Cloud Connector again!

Go to the config folder: /opt/sap/scc/config

1. Find the keystore password to be used in step 2., 3. and 4. :

java -cp /opt/sap/scc/plugins/*.jar -Djava.library.path=/opt/sap/scc/auditor -path /opt/sap/scc/scc_config -p

2. Delete the tomcat key:

keytool -delete -alias tomcat -keystore -storepass <password>

3. Generate a new tomcat certificate:

keytool -genkey -v -keyalg RSA -alias tomcat -keypass <password> -keystore -storepass <password> -dname "CN=SCC, OU=<YourCompany>, O=<YourCompany>"

4. Self-sign it (Not mandatory I think...)

keytool -selfcert -v -alias tomcat -storepass <password> -keystore

Hopefully this solves your issue as well!

Best Regards

Sveinung Ryland

Former Member
0 Kudos

Thank you very much Sveinung.

As I'm working towards a deadline, I had to reinstall HCC which seems to have resolved the issue but I've flagged your answer in case it happens again (and hopefully this will help others in the future).

Thanks also Markus....

Answers (1)

Answers (1)

Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Jonathan,

for some reason the port check verifiying that this port is not blocked by some other process failed for some reason with a NullPointerException. Could you please attach the ljs_trace.log to this post? I'd like to know what exactly is null. In order to identify this nicely, it would be good if you could run the SCC with SAPJVM 7 as it will provide more info in the message of the NullPointerException.

Best regards,