I’ve recently started getting this problem on 2 different servers when launching the hmi from jnlp files. (Apologies for creating a new topic on this as I just noticed there is another with similar title further down the screen)
It is possible it is our network or internal firewall software but I’ve started getting complaints from operations regarding this occurring when starting the hmi. Sometimes it takes multiple attempts before it link works.
Error launching application:
ConnectionException: Connection refused: connect
HttpResponseException: 404: Not Found
I can reproduce the latter sometimes but not always on my laptop. The latest report is that the former occurred after logging out and then immediately trying reopen the HMI.
On my own machine when the 404 response occurs and I connect wireshark and monitor the network, I see it contacting the wrong server for information in the middle of the process. We are not using clustering on these machines and the gateway name is different. I was also starting the JNLP files manually by running javaws directly on jnlp files which have the correct server information. Really I do not know how the the production server knows about the development server in this context but it does. I did find reference in the xopcua module configuration keystore but assume that should not be related.
The projects are being transfered from one server to another by downloading and uploading to another server. It sounds like some sort of javaws caching problems on my local machine if I am interpretting this correctly. It is not 100% consistent so not clear what is going on.
Anyway, I suspect this is not adequate information to investigate but is there anything I can do to enable better logging when starting up.