Capturing traffic between local webservice and external ssl based webservice

[Sachin_Sawe__Pr]

Hi Robert,

Consider a case where I am issuing a HTTP request to my webservice running on localhost:8080. This webservice then in turn sends HTTPS request to an external webservice. I want to monitor traffic between our localhost:8080 and external webservice. I am trying to do this by setting up soapui monitor as a proxy running at localhost:8081. My local webservice is configured to send request to endpoint, say, https://www.abcd.com/soap/externalService using security certificate. My local service also uses concept of a proxy server and that is where I register localhost:8081 as a proxy server. I have setup soapui monitor at localhost:8081 using Http proxy method (not the tunnel method). When I set up this monitor I also gave it an incoming-ws config where I specify by signature certificate that is required by external web service.

Here is the problem:
When I issue the request to my local web service at localhost:8080, my webservice internally sends request to the proxy at localhost:8081. But then I receive a response back from localhost:8081 saying:

- I/O error: Connection has been shutdown: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?; nested exception is javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
org.springframework.ws.client.WebServiceIOException: I/O error: Connection has been shutdown: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?; nested exception is javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?

I feel that proxy is having a plain socket and not able to send ssl message coming from my local web service on plain http proxy connection.

I also tried using http tunnel for this purpose where tunnel listens on localhost:8081 and my webservice is still configured to use localhost:8081 as proxy. In that case I get "connection refused error".

Any thoughts in getting this running?

Thanks in advance,

Sachin

[Sachin_Sawe__Pr]

Robert,

I figured this one out. Basically there is a bug underlying soapui monitor with http tunnel functionality. This bug is such that if there is anything wrong with http keystore or truststore then it throws error on console but does not actually start the monitor. It however shows you the monitor in UI so user feels monitor has started but actually it has not. That is why I was getting Connection refused because the monitor was not at all running on port 8081. Please note this bug for future references so you guys can fix it.

I do have another follow up questions as I progressed further on this. But I shall create a separate topic for that

Thanks,
Sachin

[SmartBear_Suppo]

Hello,

Ok. I'm on it..Did not you get any pop up with message that there is a problem with monitor and that it will not be started? Maybe we should not bring its panel after that...

robert