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
