Why does JNLP4 not work

[Jonathan Hodgson]

Hi,

I'm having some issues with my windows slave.. remote file operations are failing, also the connection is unreliable.

Now this may have no connection, but I notice that when I run the slave I get

Server reports protocol JNLP4-connect not supported, skipping

Server reports protocol JNLP4-plaintext not supported, skipping

Server reports protocol JNLP3-connect not supported, skipping

It finally succeeds with JNLP2

Why is this? Why would the slave (jenkins) ask for a protocol which the server (jenkins) doesn't support.

jenkins is running behind an Apache frontend running on a different machine, if that makes any difference.

regards

Jon

[Stephen Connolly]

Have you updated the agent jar file?

The agent jar file that supports JNLP4 does protocol discovery to only try protocols that are supported by the agent jar file... or alternatively have you updated Jenkins to a version that supports advertising supported protocols (which would be needed for Jenkins to support JNLP4)

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e1b31a03-da0f-4828-ae3c-1fbf2679bb98%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Sent from my phone

[Jonathan Hodgson]

I'm the latest version of jenkins (2.35), updated today via apt-get on debian, and downloaded slave.jar fresh from the server after a restart.

[Daniel Beck]

Any of these protocols disabled in Manage Jenkins » Configure Global Security?

> On 07.12.2016, at 20:10, Jonathan Hodgson <j.r.h...@gmail.com> wrote:
>
> I'm the latest version of jenkins (2.35), updated today via apt-get on debian, and downloaded slave.jar fresh from the server after a restart.
>
> On Wednesday, December 7, 2016 at 6:33:32 PM UTC, Stephen Connolly wrote:
> Have you updated the agent jar file?
>
> The agent jar file that supports JNLP4 does protocol discovery to only try protocols that are supported by the agent jar file... or alternatively have you updated Jenkins to a version that supports advertising supported protocols (which would be needed for Jenkins to support JNLP4)
>
>
>
> On Wednesday, 7 December 2016, Jonathan Hodgson <j.r.h...@gmail.com> wrote:
> Hi,
>
> I'm having some issues with my windows slave.. remote file operations are failing, also the connection is unreliable.
>
> Now this may have no connection, but I notice that when I run the slave I get
> Server reports protocol JNLP4-connect not supported, skipping
> Server reports protocol JNLP4-plaintext not supported, skipping
> Server reports protocol JNLP3-connect not supported, skipping
>
> It finally succeeds with JNLP2
>
> Why is this? Why would the slave (jenkins) ask for a protocol which the server (jenkins) doesn't support.
>
> jenkins is running behind an Apache frontend running on a different machine, if that makes any difference.
>
> regards
>
> Jon
>
>
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Users" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e1b31a03-da0f-4828-ae3c-1fbf2679bb98%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> Sent from my phone
>

> --
> You received this message because you are subscribed to the Google Groups "Jenkins Users" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/41e38094-9b51-4c9b-a6f1-920c21ee70aa%40googlegroups.com.

[Stephen Connolly]

Then What protocols have you enabled in global security settings and by the sound of it, you may need to check if Apache is filtering the headers (specifically blocking the header that reports enabled protocols)

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/41e38094-9b51-4c9b-a6f1-920c21ee70aa%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Jonathan Hodgson]

Thanks, I hadn't seen those setting on the security page.

JNLP4 now seems to be connecting, which is good (and I'm a little less confused than I was).

Unfortunately it hasn't made any difference to my problem with remote file operations, not that I had any real reason to think it would, I just hoped.

So I still have a largely useless slave, just one connected with JNLP4

[Stephen Connolly]

Sounds like you need to post some details of these "remote" (remote to where) file operations - in a new thread, as the JNLP4 issue is solved - if you want to get further.

Stack traces are usually helpful

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4eefa7de-ed60-4616-884c-286ffd054917%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Jonathan Hodgson]

I already did, before raising this question, I'll see if I can get some more examples.