ENTRY

"“Secret” Jenkins jnlp option. Jenkins slave fails to connect with MalformedByteSequenceException"

Date:May 18th, 2015
Tags:
Comments: 0
  • Join date: 11-30-99
  • Posts: 23
View Counter:
  • 522 views
Rate it
Ad
Poll
  • What build management tool does your project or firm use?

    View Results

    Loading ... Loading ...
Feeds:
  • bodytext bodytext bodytext

“Secret” Jenkins jnlp option. Jenkins slave fails to connect with “. MalformedByteSequenceException: Invalid byte 2 of 3-byte UTF-8 sequence .”. What solved it in my case.

1

JNLP -secret parameter in jenkins-slave.xml

“Secret” option supposed to ensure that Jenkins slave which connects is friendly. Makes sense in internet instances, in enterprise may be not useful.

My jenkins-slave.xml has args. With “secret” parameter

<service>
..
<arguments>-d64 -Dorg.jenkinsci.plugins.gitclient.Git.timeOut=900 -Xrs -jar "%BASE%slave.jar" -jnlpUrl http://mymaster:8081/computer/myslave123/slave-agent.jnlp -secret 212121qw...</arguments>
..
</service>

2

Slave start

Now, by coping Jenkins slave config file jenkins-slave.xml I have seen it fail to start on some PC’s, especially win 8.1 versions.

When I look through logs, I see

com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 2 of 3-byte UTF-8 sequence.

3

Removing -secret from jenkins-slave.xml allows slave to start

Try to run without secret at all, especially if you are in trusted env. It shall be ok.

Have fun!


Be Sociable, Share!
 
Interesting entry?
VN:F [1.8.5_1061]
Rating: 0 (from 0 votes)
0 votes 'YES'  0 votes 'NO'


TAGS

RELATED
Pages
Posts

SOCIAL
Be Sociable, Share!

INCOMING SEARCH TERMS



Responces

Leave a Reply