cancel
Showing results for 
Search instead for 
Did you mean: 

SSL/HTTPS issue

Former Member
0 Kudos

Hi All,

Currently we are using the SAP application server to host a J2EE webapp we made. In one of our servlets we do an http post to a location hosted by a webserver.

Our problem is the following; when we post http things seem to work well. When we try to post via https the application occasionally gets in a state where the above mentioned post requests hangs. Strange thing is that this problem seems intermittent, so we don't think it's a certificate issue. Also we've insured that there are no firewalls sitting between the hosts. We've tried using both the standard java apis (URL.connect()) and the SAP apis (SecureConnectionFactory).

We've narrowed the problem down to SSL and only the SAP Web Application Server because when we put our code in another container (eg. tomcat) things work well with https.

Has anybody experienced anything similar to this before? We are utterly stumped.

Thanks in Advance!

Ray Siu

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi again,

Well we have tried with posting to several different web servers we have here in our network, which is part of the reason why we belive it's a Application server thing.

Another funny thing we just discovered: when our application is in a state where the HTTPS connection hangs, we noticed that none of our post requests were getting logged by the requestee's web server's access logs. Weird, looks like the request never leaves the WAS box.

Thanks,

Ray Siu

Former Member
0 Kudos

Have you thought about checking the policy file to make sure you have the right rights setup? Are the right classes represented for the setup. Do you have connect, resolve permissions?...

Enjoy

Former Member
0 Kudos

Thanks very much for your help.

Yes, we've tried with FireFox and IE with the same results.

As I mentioned, the hanging POST connection is made from java code in our servlet. The client's browser is unlikely the problem because the client's request never directly interacts with this.

When we pulled our webapp out to Tomcat we were using the same JRE and same java keystore... so the same certificates were being used. Yet we did not see the hanging in Tomcat. This makes it unlikely that it's a certificate issue.

Thanks!

Ray Siu