Soap 2.3.1, SSL, Java 1.3-1.4.x and a proxy.

["Gill, John" <Jo...@tgslc.org>]

I've run into a bit of a snag with Soap 2.3.1, SSL, Java 1.3-1.4.x and a
proxy.  The application in question accesses soap services both outside the
proxy and internally.  It works through all these devices quite nicely if
there is only one connection type (through the proxy, or internal).  If the
application attempts to access both types of connection types on separate
threads, it's hit or miss if we will be able to access both systems.  The
problem seems to be with the way that the Java SSL client system works.
Without making the whole threading system dependent on a synchronous
connection model, where each call happens in it a FIFO type queue, is there
any way to solve this problem?  

 

For right now, we are embedding the internal non-proxy connection in a
synchronous call, but this will potentially double the time it takes to get
the responses back.

 

John W Gill
TG

Re: Soap 2.3.1, SSL, Java 1.3-1.4.x and a proxy.

[Martin <mg...@hotmail.com>]

John-

If I was to attempt to answer the question the answer would be "it depends"
1)Does the internal SSL connection continously try and then times out when
there is no SOAP SSL response?
If so does it then attempt to SSL connect outside where the proxy would
intercept it?
else the connections are separate and distinct connections (see 3)
2)What type of Proxy are you running?
Is the Proxy configured for SSL if the Proxy is not configured you want to
look at the proxy documentation
3)Are the SOAP SSL requests for internal SSL SOAP Request and proxy SSL SOAP
Request related..
i.e. I must fulfill Request1 before attempting Request2 or are they
independent of each other?
If they are independent requests I would establish separate connections
Perhaps if we had more information I could make a better educated stab at
the situation.

-Martin

----- Original Message -----
From: "Gill, John" <Jo...@tgslc.org>
To: <so...@ws.apache.org>
Sent: Monday, March 03, 2003 1:58 PM
Subject: Soap 2.3.1, SSL, Java 1.3-1.4.x and a proxy.


> I've run into a bit of a snag with Soap 2.3.1, SSL, Java 1.3-1.4.x and a
> proxy.  The application in question accesses soap services both outside
the
> proxy and internally.  It works through all these devices quite nicely if
> there is only one connection type (through the proxy, or internal).  If
the
> application attempts to access both types of connection types on separate
> threads, it's hit or miss if we will be able to access both systems.  The
> problem seems to be with the way that the Java SSL client system works.
> Without making the whole threading system dependent on a synchronous
> connection model, where each call happens in it a FIFO type queue, is
there
> any way to solve this problem?
>
>
>
> For right now, we are embedding the internal non-proxy connection in a
> synchronous call, but this will potentially double the time it takes to
get
> the responses back.
>
>
>
> John W Gill
> TG
>
>