Directing Jenkins (Windows) to use 64bit Java (JRE)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
PF
Reply | Threaded
Open this post in threaded view
|

Directing Jenkins (Windows) to use 64bit Java (JRE)

PF
Hello,
I would like to check if it's safe (no potential side effects) of changing executable parameter jenkins.xml config file to the path of Java on the server itself. I know that Jenkins (on Windows) comes with its own Java out of the box, and it uses 32bit Java. The reason for this change is that I would like to increase memory used by Jenkins (JVM) to 2GB (-Xmx2048m) but found that I can only go up to 1.2GB on 32bit Java (provided out of the box). 

I've updated executable to "C:\Program Files (x86)\Common Files\Oracle\Java\javapath\java.exe" and performed some quick tests. I haven't seen any issues so far but wanted to confirm if this is an acceptable change and I won't see any conflicts/issues in the future.

Please let me know if you have any questions or need additional information.
Thank you
PF
 

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAKnF1n9ibDDZJb0L0WA9A5h-WFsY2vBR7a9yYngMZdAW8oNBTg%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Directing Jenkins (Windows) to use 64bit Java (JRE)

Mark Waite-2


On Sun, Oct 11, 2020 at 12:30 PM PersonFirst PersonLast <[hidden email]> wrote:
Hello,
I would like to check if it's safe (no potential side effects) of changing executable parameter jenkins.xml config file to the path of Java on the server itself. I know that Jenkins (on Windows) comes with its own Java out of the box, and it uses 32bit Java. The reason for this change is that I would like to increase memory used by Jenkins (JVM) to 2GB (-Xmx2048m) but found that I can only go up to 1.2GB on 32bit Java (provided out of the box). 


A 64 bit Java runs quite well on Windows.  The Windows installer stopped bundling Java with the Windows installer upgrades in Jenkins 2.235.3.  You can read about the Jenkins 2.249.1 testing on Windows in case you want to read Windows experiences from others.
 
I've updated executable to "C:\Program Files (x86)\Common Files\Oracle\Java\javapath\java.exe" and performed some quick tests. I haven't seen any issues so far but wanted to confirm if this is an acceptable change and I won't see any conflicts/issues in the future.

I don't expect any issues.  I've not seen any reports that were specific to the transition from 32 bit Java to 64 bit Java.

Mark Waite
 

Please let me know if you have any questions or need additional information.
Thank you
PF
 

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAKnF1n9ibDDZJb0L0WA9A5h-WFsY2vBR7a9yYngMZdAW8oNBTg%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHcZ7fk2%2BpOtLeXPDPJ%3DSt%3De3wF5nt8CGB_ziq2Ewj%3DCQ%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Directing Jenkins (Windows) to use 64bit Java (JRE)

slide
This is how I have run my Windows based Jenkins controller for some time. There are no issues with using a 64-bit JRE.

On Sun, Oct 11, 2020, 11:40 Mark Waite <[hidden email]> wrote:


On Sun, Oct 11, 2020 at 12:30 PM PersonFirst PersonLast <[hidden email]> wrote:
Hello,
I would like to check if it's safe (no potential side effects) of changing executable parameter jenkins.xml config file to the path of Java on the server itself. I know that Jenkins (on Windows) comes with its own Java out of the box, and it uses 32bit Java. The reason for this change is that I would like to increase memory used by Jenkins (JVM) to 2GB (-Xmx2048m) but found that I can only go up to 1.2GB on 32bit Java (provided out of the box). 


A 64 bit Java runs quite well on Windows.  The Windows installer stopped bundling Java with the Windows installer upgrades in Jenkins 2.235.3.  You can read about the Jenkins 2.249.1 testing on Windows in case you want to read Windows experiences from others.
 
I've updated executable to "C:\Program Files (x86)\Common Files\Oracle\Java\javapath\java.exe" and performed some quick tests. I haven't seen any issues so far but wanted to confirm if this is an acceptable change and I won't see any conflicts/issues in the future.

I don't expect any issues.  I've not seen any reports that were specific to the transition from 32 bit Java to 64 bit Java.

Mark Waite
 

Please let me know if you have any questions or need additional information.
Thank you
PF
 

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAKnF1n9ibDDZJb0L0WA9A5h-WFsY2vBR7a9yYngMZdAW8oNBTg%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHcZ7fk2%2BpOtLeXPDPJ%3DSt%3De3wF5nt8CGB_ziq2Ewj%3DCQ%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVfPF69gHc7uBgq9GU1ecaqp98T4K5xw9mLbLFZLK2g6DA%40mail.gmail.com.
PF
Reply | Threaded
Open this post in threaded view
|

Re: Directing Jenkins (Windows) to use 64bit Java (JRE)

PF
Thank you All for the confirmation and provided information!

On Sun, Oct 11, 2020 at 2:48 PM Slide <[hidden email]> wrote:
This is how I have run my Windows based Jenkins controller for some time. There are no issues with using a 64-bit JRE.

On Sun, Oct 11, 2020, 11:40 Mark Waite <[hidden email]> wrote:


On Sun, Oct 11, 2020 at 12:30 PM PersonFirst PersonLast <[hidden email]> wrote:
Hello,
I would like to check if it's safe (no potential side effects) of changing executable parameter jenkins.xml config file to the path of Java on the server itself. I know that Jenkins (on Windows) comes with its own Java out of the box, and it uses 32bit Java. The reason for this change is that I would like to increase memory used by Jenkins (JVM) to 2GB (-Xmx2048m) but found that I can only go up to 1.2GB on 32bit Java (provided out of the box). 


A 64 bit Java runs quite well on Windows.  The Windows installer stopped bundling Java with the Windows installer upgrades in Jenkins 2.235.3.  You can read about the Jenkins 2.249.1 testing on Windows in case you want to read Windows experiences from others.
 
I've updated executable to "C:\Program Files (x86)\Common Files\Oracle\Java\javapath\java.exe" and performed some quick tests. I haven't seen any issues so far but wanted to confirm if this is an acceptable change and I won't see any conflicts/issues in the future.

I don't expect any issues.  I've not seen any reports that were specific to the transition from 32 bit Java to 64 bit Java.

Mark Waite
 

Please let me know if you have any questions or need additional information.
Thank you
PF
 

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAKnF1n9ibDDZJb0L0WA9A5h-WFsY2vBR7a9yYngMZdAW8oNBTg%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHcZ7fk2%2BpOtLeXPDPJ%3DSt%3De3wF5nt8CGB_ziq2Ewj%3DCQ%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVfPF69gHc7uBgq9GU1ecaqp98T4K5xw9mLbLFZLK2g6DA%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAKnF1n_fCaMEWZwVXSNG0uiOWhSP_tEf%2BY_qrELUmNFBS6Qwdg%40mail.gmail.com.