Karakun Support Forums

I am encountering a problem with OpenWebStart in which the manual proxy settings appear to be recognised, yet subsequent communications are performed directly (no proxy). I would appreciate your guidance on possible causes and troubleshooting steps.

Configuration
I set the manual proxy in deployment.properties as follows:
deployment.proxy.type=1
deployment.proxy.http.host=xxx.xxx.xxx.xxx
deployment.proxy.http.port=8080
deployment.proxy.https.host=xxx.xxx.xxx.xxx
deployment.proxy.https.port=8080
deployment.proxy.ftp.host=xxx.xxx.xxx.xxx
deployment.proxy.ftp.port=8080
deployment.proxy.same=true

Evidence that the configuration is read
The OpenWebStart logs indicate that the manual provider and proxy addresses have been created:
[com.openwebstart.proxy.WebStartProxySelector] Selected ProxyProvider : MANUAL_HOSTS
[com.openwebstart.proxy.ProxyProviderType] Manual proxy created
[com.openwebstart.proxy.config.ConfigBasedProvider] Http proxy congfig: host xxx.xxx.xxx.xxx - port 8080
[com.openwebstart.proxy.config.ConfigBasedProvider] Https proxy congfig: host xxx.xxx.xxx.xxx - port 8080
[com.openwebstart.proxy.config.ConfigBasedProvider] Ftp proxy congfig: host xxx.xxx.xxx.xxx- port 8080
[com.openwebstart.proxy.config.ConfigBasedProvider] Socks proxy congfig: host null - port -1
[com.openwebstart.proxy.config.ConfigBasedProvider] proxy bypass list: []
...
[com.openwebstart.proxy.config.ConfigBasedProvider] Proxies found for 'https://xxxxxx' : [HTTP @ /xxx.xxx.xxx.xxx:8080]

Problem observed
Despite the above, later logs show that system proxy properties are null and the provider repeatedly reports "No proxy found" for the socket endpoints, falling back to NO_PROXY:
[net.sourceforge.jnlp.Launcher] Invoking main() with args: [-jsessionid ..., -soapURL https://xxxxx, ..., -axisClientStubSetTimeout -1, -language ja]
[sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)] ■http.proxyHost=null-
[sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)] ■proxyHost=null-
[sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)] ■javaplugin host=null-
[sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)] ---> http.proxyHost=null-
[sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)] ■http.proxyPort=null-
[sun.nio.cs.StreamEnoder.writeBytes(StreamEncoder.java:221)] ■proxyPort=null-
[sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)] ■javaplugin port=null-
[sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)] ---> http.proxyPort=null-
[sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)] ■https.proxyHost=null-
[sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)] ■javaplugin sHost=null-
[sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)] ---> https.proxyHost=null-
[sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)] ■https.proxyPort=null-
[sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)] ■javaplugin sPort=null-
[sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)] ---> https.proxyPort=null-
[com.openwebstart.proxy.config.ConfigBasedProvider] No proxy found for 'socket://xxxxxx:443'. Falling back to NO_PROXY
[com.openwebstart.proxy.config.ConfigBasedProvider] No proxy found for 'socket://xxxxxx:443'. Falling back to NO_PROXY
... No proxy found for 'socket://xxxxxx:443'. Falling back to NO_PROXY

Actions already taken

I toggled the "Use the same proxy server for all protocol(s)" option both on and off.
I explicitly entered proxy addresses for each protocol separately.
The outcome remained the same.
Additional note
This issue does not occur with the legacy Java Web Start in our environment ? Java Web Start used the proxy as expected for the same application.

Request
Could you advise on:

Why OpenWebStart would detect and create manual proxy entries yet still use NO_PROXY?
Whether any additional OpenWebStart or JVM system properties need to be set so that JNLP-launched applications actually route through the proxy?

Which version OWS are you using?

Did you set the proxy using the itw-settings tool?

From the logs below , it seems OWS is starting your app. OWS must be downloading Jnlp and Jars through the proxy. What happens if you cut off access to the proxy? Does OWS throw an error while downloading Jnlp and Jars? Can you try this?

Can you please share your OWS logs on openwebstart@karakun.com for now? However, we recommend that you buy support and post it on you own private support channel on the forum?

The OWS version is 1.12.0.
I have configured the settings via OpenWebStart’s “Proxy Settings.”

The download of JNLP and JAR files is going through the proxy as expected (working according to the configuration).
No issues occur up to the point where JNLP and JAR files are being downloaded.

I will share the logs separately.

I had a look at the logs which you have copied in your email. I would have preferred if you had sent me the stage 1 and stage 2 log files after masking the sensitive data.

Jars and Jnlp are downloaded through the configured proxy. The application is started successfully. The application is making SOAP requests. It is using https protocol "soapURL https://[MASKED]/... "

It seems your application is logging the proxy properties.

Is the application trying to set some proxy related jvm properties?

For the SOAP related URLs the Proxy is not found.

Need to know what kind of URL is this and figure out why the Proxy is not found.

Is there a way for you to set the same proxy on your machine and test this SOAP url outside of your application?

In the mean time can you send me the zip of entire stage1 and stage 2 files ?