# Problem after java-Update in CentOS 6 **URL:** \ **Category:** Gateway\ **Created:** [May 17, 2016, 4:02pm UTC](https://community.ciphermail.com/t/problem-after-java-update-in-centos-6/504 "2016-05-17T16:02:16Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Testuser\_SST](https://avatars.discourse-cdn.com/v4/letter/t/bc79bd/32.png) [@Testuser\_SST](https://community.ciphermail.com/u/Testuser_SST)\ **Post date:** [May 17, 2016, 4:02pm UTC](https://community.ciphermail.com/t/problem-after-java-update-in-centos-6/504/1 "2016-05-17T16:02:16Z")
Hi, I`m using a ciphermail on a CentOS 6 fully patched and it worked fine for quite a while, but after an update to java-1.6.0-openjdk-1.6.0.39-1.13.11.0.el6\_7.x86\_64 today, I found this in the /var/log/djigzo.log: ...ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall] JVM process is gone. JVM exited while loading the application. Launching a JVM... JVM received a signal UNKNOWN (6). java version "1.6.0\_39" OpenJDK Runtime Environment (IcedTea6 1.13.11) (rhel-1.13.11.0.el6\_7-x86\_64) OpenJDK 64-Bit Server VM (build 23.25-b01, mixed mode) \*\*\* glibc detected \*\*\* /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86\_64/jre/bin/java: double free or corruption (!prev): 0x0000000001e5ac c0 \*\*\* ======= Backtrace: ========= /lib64/libc.so.6(+0x75f4e)[0x7fc450e82f4e] /lib64/libc.so.6(+0x78cf0)[0x7fc450e85cf0] /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86\_64/jre/bin/java[0x402fbb] /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86\_64/jre/bin/java(JavaMain+0x51c)[0x40373c] /lib64/libpthread.so.0(+0x7aa1)[0x7fc4515b0aa1] /lib64/libc.so.6(clone+0x6d)[0x7fc450ef593d] .... There were 10 failed launches in a row, each lasting less than 300 seconds. Giving up.   There may be a configuration problem: please check the logs. \<-- Wrapper Stopped On the Weblogin-page I got the message about a not fully started background problem. Any suggestions are welcome Kind regards fatcharly ---
**Author:** ![martijn](https://dub1.discourse-cdn.com/flex017/user_avatar/community.ciphermail.com/martijn/32/127_2.png) [@martijn](https://community.ciphermail.com/u/martijn)\ **Post date:** [May 17, 2016, 4:16pm UTC](https://community.ciphermail.com/t/problem-after-java-update-in-centos-6/504/2 "2016-05-17T16:16:36Z")
> Hi, I`m using a ciphermail on a CentOS 6 fully patched and it worked > fine for quite a while, but after an update to > java-1.6.0-openjdk-1.6.0.39-1.13.11.0.el6\_7.x86\_64 today, I found > this in the /var/log/djigzo.log: ...ffffffffff600000-ffffffffff601000 > r-xp 00000000 00:00 0 [vsyscall] JVM process is > gone. JVM exited while loading the application. Launching a JVM... > JVM received a signal UNKNOWN (6). java version "1.6.0\_39" OpenJDK > Runtime Environment (IcedTea6 1.13.11) (rhel-1.13.11.0.el6\_7-x86\_64) > OpenJDK 64-Bit Server VM (build 23.25-b01, mixed mode) > > \*\*\* glibc detected \*\*\* > /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86\_64/jre/bin/java: double > free or corruption (!prev): 0x0000000001e5ac c0 \*\*\* ======= > Backtrace: ========= /lib64/libc.so.6(+0x75f4e)[0x7fc450e82f4e] > /lib64/libc.so.6(+0x78cf0)[0x7fc450e85cf0] > /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86\_64/jre/bin/java[0x402fbb] /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86\_64/jre/bin/java(JavaMain+0x51c)[0x40373c] > /lib64/libpthread.so.0(+0x7aa1)[0x7fc4515b0aa1] > /lib64/libc.so.6(clone+0x6d)[0x7fc450ef593d] .... > > There were 10 failed launches in a row, each lasting less than 300 > seconds. Giving up. There may be a configuration problem: please > check the logs. \<-- Wrapper Stopped > > On the Weblogin-page I got the message about a not fully started > background problem. > > Any suggestions are welcome This looks like a bug in Java 6. A similar bug was reported last week: [https://jira.djigzo.com/browse/GATEWAY-101](https://jira.djigzo.com/browse/GATEWAY-101) For now the best solution is to upgrade to Java 6. See bug report #GATEWAY-101 for more information. A possible workaround is to add the following line to the file djigzo.wrapper.conf wrapper.debug=true Let me know whether this work around works for you. It looks like some interaction between Java wrapper (which starts the Java process) and Java 6 update. I will investigate this further. Kind regards, Martijn > **···** > > On 05/17/2016 06:02 PM, fatcharly(a)gmx.de wrote: > > -- > CipherMail email encryption > > Email encryption with support for S/MIME, OpenPGP, PDF encryption and > secure webmail pull. > > > **[CipherMail email encryption and digital signatures](https://www.ciphermail.com)** > > > > Easy to use server-side email encryption for automatic encryption and digital signing of email. > > Twitter: [http://twitter.com/CipherMail](http://twitter.com/CipherMail) > > -- > CipherMail email encryption > > Email encryption with support for S/MIME, OpenPGP, PDF encryption and > secure webmail pull. > > > **[CipherMail email encryption and digital signatures](https://www.ciphermail.com)** > > > > Easy to use server-side email encryption for automatic encryption and digital signing of email. > > Twitter: [http://twitter.com/CipherMail](http://twitter.com/CipherMail) ---
**Author:** ![martijn](https://dub1.discourse-cdn.com/flex017/user_avatar/community.ciphermail.com/martijn/32/127_2.png) [@martijn](https://community.ciphermail.com/u/martijn)\ **Post date:** [May 18, 2016, 8:43am UTC](https://community.ciphermail.com/t/problem-after-java-update-in-centos-6/504/3 "2016-05-18T08:43:56Z")
As a workaround (instead of installing Java 7), you can add wrapper.disable\_console\_input=FALSE to the Java wrapper config. You can add this option by editing the file /etc/init.d/djigzo Change WRAPPER\_OPTS="wrapper.daemonize=TRUE" To: WRAPPER\_OPTS="wrapper.daemonize=TRUE wrapper.disable\_console\_input=FALSE" I'll contact the java wrapper developers. It might be some interaction bug between changes in Java 6 and java wrapper. Kind regards, Martijn Brinkers > **···** > > On 05/17/2016 06:16 PM, Martijn Brinkers wrote: > > > On 05/17/2016 06:02 PM, fatcharly(a)gmx.de wrote: > > > > > Hi, I`m using a ciphermail on a CentOS 6 fully patched and it worked > > > fine for quite a while, but after an update to > > > java-1.6.0-openjdk-1.6.0.39-1.13.11.0.el6\_7.x86\_64 today, I found > > > this in the /var/log/djigzo.log: ...ffffffffff600000-ffffffffff601000 > > > r-xp 00000000 00:00 0 [vsyscall] JVM process is > > > gone. JVM exited while loading the application. Launching a JVM... > > > JVM received a signal UNKNOWN (6). java version "1.6.0\_39" OpenJDK > > > Runtime Environment (IcedTea6 1.13.11) (rhel-1.13.11.0.el6\_7-x86\_64) > > > OpenJDK 64-Bit Server VM (build 23.25-b01, mixed mode) > > > > > > \*\*\* glibc detected \*\*\* > > > /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86\_64/jre/bin/java: double > > > free or corruption (!prev): 0x0000000001e5ac c0 \*\*\* ======= > > > Backtrace: ========= /lib64/libc.so.6(+0x75f4e)[0x7fc450e82f4e] > > > /lib64/libc.so.6(+0x78cf0)[0x7fc450e85cf0] > > > /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86\_64/jre/bin/java[0x402fbb] > > > > /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86\_64/jre/bin/java(JavaMain+0x51c)[0x40373c] > > > > > /lib64/libpthread.so.0(+0x7aa1)[0x7fc4515b0aa1] > > > /lib64/libc.so.6(clone+0x6d)[0x7fc450ef593d] .... > > > > > > There were 10 failed launches in a row, each lasting less than 300 > > > seconds. Giving up. There may be a configuration problem: please > > > check the logs. \<-- Wrapper Stopped > > > > > > On the Weblogin-page I got the message about a not fully started > > > background problem. > > > > > > Any suggestions are welcome > > > > This looks like a bug in Java 6. A similar bug was reported last week: > > > > [https://jira.djigzo.com/browse/GATEWAY-101](https://jira.djigzo.com/browse/GATEWAY-101) > > > > For now the best solution is to upgrade to Java 6. See bug report > > #GATEWAY-101 for more information. > > > > A possible workaround is to add the following line to the file > > djigzo.wrapper.conf > > > > wrapper.debug=true > > > > Let me know whether this work around works for you. It looks like some > > interaction between Java wrapper (which starts the Java process) and > > Java 6 update. > > > > I will investigate this further. > > -- > CipherMail email encryption > > Email encryption with support for S/MIME, OpenPGP, PDF encryption and > secure webmail pull. > > > **[CipherMail email encryption and digital signatures](https://www.ciphermail.com)** > > > > Easy to use server-side email encryption for automatic encryption and digital signing of email. > > Twitter: [http://twitter.com/CipherMail](http://twitter.com/CipherMail) ---
**Author:** ![Testuser\_SST](https://avatars.discourse-cdn.com/v4/letter/t/bc79bd/32.png) [@Testuser\_SST](https://community.ciphermail.com/u/Testuser_SST)\ **Post date:** [May 18, 2016, 9:37am UTC](https://community.ciphermail.com/t/problem-after-java-update-in-centos-6/504/4 "2016-05-18T09:37:58Z")
> Gesendet: Mittwoch, 18. Mai 2016 um 10:43 Uhr > Von: "Martijn Brinkers" \ > An: users(a)lists.djigzo.com > Betreff: Re: Problem after java-Update in CentOS 6 > > \>\> Hi, I`m using a ciphermail on a CentOS 6 fully patched and it worked > \>\> fine for quite a while, but after an update to > \>\> java-1.6.0-openjdk-1.6.0.39-1.13.11.0.el6\_7.x86\_64 today, I found > \>\> this in the /var/log/djigzo.log: ...ffffffffff600000-ffffffffff601000 > \>\> r-xp 00000000 00:00 0 [vsyscall] JVM process is > \>\> gone. JVM exited while loading the application. Launching a JVM... > \>\> JVM received a signal UNKNOWN (6). java version "1.6.0\_39" OpenJDK > \>\> Runtime Environment (IcedTea6 1.13.11) (rhel-1.13.11.0.el6\_7-x86\_64) > \>\> OpenJDK 64-Bit Server VM (build 23.25-b01, mixed mode) > \>\> > \>\> \*\*\* glibc detected \*\*\* > \>\> /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86\_64/jre/bin/java: double > \>\> free or corruption (!prev): 0x0000000001e5ac c0 \*\*\* ======= > \>\> Backtrace: ========= /lib64/libc.so.6(+0x75f4e)[0x7fc450e82f4e] > \>\> /lib64/libc.so.6(+0x78cf0)[0x7fc450e85cf0] > \>\> /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86\_64/jre/bin/java[0x402fbb] > \>\> > \>\> > \> /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86\_64/jre/bin/java(JavaMain+0x51c)[0x40373c] > \>\> /lib64/libpthread.so.0(+0x7aa1)[0x7fc4515b0aa1] > \>\> /lib64/libc.so.6(clone+0x6d)[0x7fc450ef593d] .... > \>\> > \>\> There were 10 failed launches in a row, each lasting less than 300 > \>\> seconds. Giving up. There may be a configuration problem: please > \>\> check the logs. \<-- Wrapper Stopped > \>\> > \>\> On the Weblogin-page I got the message about a not fully started > \>\> background problem. > \>\> > \>\> Any suggestions are welcome > \> > \> This looks like a bug in Java 6. A similar bug was reported last week: > \> > \> [https://jira.djigzo.com/browse/GATEWAY-101](https://jira.djigzo.com/browse/GATEWAY-101) > \> > \> For now the best solution is to upgrade to Java 6. See bug report > \> #GATEWAY-101 for more information. > \> > \> A possible workaround is to add the following line to the file > \> djigzo.wrapper.conf > \> > \> wrapper.debug=true > \> > \> Let me know whether this work around works for you. It looks like some > \> interaction between Java wrapper (which starts the Java process) and > \> Java 6 update. > \> > \> I will investigate this further. > > As a workaround (instead of installing Java 7), you can add > wrapper.disable\_console\_input=FALSE to the Java wrapper config. You can > add this option by editing the file /etc/init.d/djigzo > > Change > > WRAPPER\_OPTS="wrapper.daemonize=TRUE" > > To: > > WRAPPER\_OPTS="wrapper.daemonize=TRUE wrapper.disable\_console\_input=FALSE" > > I'll contact the java wrapper developers. It might be some interaction > bug between changes in Java 6 and java wrapper. Hi Martin, thank you very much for your fast support. Mailencrypt and decrypt works fine with the last workaround. But we are running in a new problem with the weblogin. I always get an ssl-error (ERR\_SSL\_FALLBACK\_BEYOND\_MINIMUM\_VERSION -\> Chrome) messages in FF and Chrome when I try to open the login page. Kind regards fatcharly > **···** > > > On 05/17/2016 06:16 PM, Martijn Brinkers wrote: > > \> On 05/17/2016 06:02 PM, fatcharly(a)gmx.de wrote: > > > Kind regards, > > > > Martijn Brinkers > > > > -- > > CipherMail email encryption > > > > Email encryption with support for S/MIME, OpenPGP, PDF encryption and > > secure webmail pull. > > > > [https://www.ciphermail.com](https://www.ciphermail.com) > > > > Twitter: [http://twitter.com/CipherMail](http://twitter.com/CipherMail) > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > Users mailing list > > Users(a)lists.djigzo.com > > [https://lists.djigzo.com/lists/listinfo/users](https://lists.djigzo.com/lists/listinfo/users) ---
**Author:** ![martijn](https://dub1.discourse-cdn.com/flex017/user_avatar/community.ciphermail.com/martijn/32/127_2.png) [@martijn](https://community.ciphermail.com/u/martijn)\ **Post date:** [May 18, 2016, 9:55am UTC](https://community.ciphermail.com/t/problem-after-java-update-in-centos-6/504/5 "2016-05-18T09:55:34Z")
> > Gesendet: Mittwoch, 18. Mai 2016 um 10:43 Uhr Von: "Martijn > > Brinkers" \ An: users(a)lists.djigzo.com > > Betreff: Re: Problem after java-Update in CentOS 6 > > > > > > Hi, I`m using a ciphermail on a CentOS 6 fully patched and it > > > > worked fine for quite a while, but after an update to > > > > java-1.6.0-openjdk-1.6.0.39-1.13.11.0.el6\_7.x86\_64 today, I > > > > found this in the /var/log/djigzo.log: > > > > ...ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 > > > > [vsyscall] JVM process is gone. JVM exited while loading the > > > > application. Launching a JVM... JVM received a signal UNKNOWN > > > > (6). java version "1.6.0\_39" OpenJDK Runtime Environment > > > > (IcedTea6 1.13.11) (rhel-1.13.11.0.el6\_7-x86\_64) OpenJDK 64-Bit > > > > Server VM (build 23.25-b01, mixed mode) > > > > > > > > \*\*\* glibc detected \*\*\* > > > > /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86\_64/jre/bin/java: > > > > double free or corruption (!prev): 0x0000000001e5ac c0 \*\*\* > > > > ======= Backtrace: ========= > > > > /lib64/libc.so.6(+0x75f4e)[0x7fc450e82f4e] > > > > /lib64/libc.so.6(+0x78cf0)[0x7fc450e85cf0] > > > > /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86\_64/jre/bin/java[0x402fbb] /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86\_64/jre/bin/java(JavaMain+0x51c)[0x40373c] > > > > /lib64/libpthread.so.0(+0x7aa1)[0x7fc4515b0aa1] > > > > /lib64/libc.so.6(clone+0x6d)[0x7fc450ef593d] .... > > > > > > > > There were 10 failed launches in a row, each lasting less than > > > > 300 seconds. Giving up. There may be a configuration problem: > > > > please check the logs. \<-- Wrapper Stopped > > > > > > > > On the Weblogin-page I got the message about a not fully > > > > started background problem. > > > > > > > > Any suggestions are welcome > > > > > > This looks like a bug in Java 6. A similar bug was reported last > > > week: > > > > > > [https://jira.djigzo.com/browse/GATEWAY-101](https://jira.djigzo.com/browse/GATEWAY-101) > > > > > > For now the best solution is to upgrade to Java 6. See bug > > > report #GATEWAY-101 for more information. > > > > > > A possible workaround is to add the following line to the file > > > djigzo.wrapper.conf > > > > > > wrapper.debug=true > > > > > > Let me know whether this work around works for you. It looks like > > > some interaction between Java wrapper (which starts the Java > > > process) and Java 6 update. > > > > > > I will investigate this further. > > > > As a workaround (instead of installing Java 7), you can add > > wrapper.disable\_console\_input=FALSE to the Java wrapper config. You > > can add this option by editing the file /etc/init.d/djigzo > > > > Change > > > > WRAPPER\_OPTS="wrapper.daemonize=TRUE" > > > > To: > > > > WRAPPER\_OPTS="wrapper.daemonize=TRUE > > wrapper.disable\_console\_input=FALSE" > > > > I'll contact the java wrapper developers. It might be some > > interaction bug between changes in Java 6 and java wrapper. > > Hi Martin, > > thank you very much for your fast support. Mailencrypt and decrypt > works fine with the last workaround. But we are running in a new > problem with the weblogin. I always get an ssl-error > (ERR\_SSL\_FALLBACK\_BEYOND\_MINIMUM\_VERSION -\> Chrome) messages in FF > and Chrome when I try to open the login page. Works for me with CipherMail 2.10.0-3 on CentOS 6 with Java 6 and Firefox and Chrome. Which version of CipherMail are you using? Kind regards, Martijn Brinkers > **···** > > On 05/18/2016 11:37 AM, fatcharly(a)gmx.de wrote: > > > > On 05/17/2016 06:16 PM, Martijn Brinkers wrote: > > > > > > > On 05/17/2016 06:02 PM, fatcharly(a)gmx.de wrote: > > -- > CipherMail email encryption > > Email encryption with support for S/MIME, OpenPGP, PDF encryption and > secure webmail pull. > > > **[CipherMail email encryption and digital signatures](https://www.ciphermail.com)** > > > > Easy to use server-side email encryption for automatic encryption and digital signing of email. > > Twitter: [http://twitter.com/CipherMail](http://twitter.com/CipherMail) > > -- > CipherMail email encryption > > Email encryption with support for S/MIME, OpenPGP, PDF encryption and > secure webmail pull. > > > **[CipherMail email encryption and digital signatures](https://www.ciphermail.com)** > > > > Easy to use server-side email encryption for automatic encryption and digital signing of email. > > Twitter: [http://twitter.com/CipherMail](http://twitter.com/CipherMail) ---
**Author:** ![martijn](https://dub1.discourse-cdn.com/flex017/user_avatar/community.ciphermail.com/martijn/32/127_2.png) [@martijn](https://community.ciphermail.com/u/martijn)\ **Post date:** [May 18, 2016, 10:59am UTC](https://community.ciphermail.com/t/problem-after-java-update-in-centos-6/504/6 "2016-05-18T10:59:42Z")
> > Gesendet: Mittwoch, 18. Mai 2016 um 10:43 Uhr Von: "Martijn > > Brinkers" \ An: users(a)lists.djigzo.com > > Betreff: Re: Problem after java-Update in CentOS 6 > > > > > > Hi, I`m using a ciphermail on a CentOS 6 fully patched and it > > > > worked fine for quite a while, but after an update to > > > > java-1.6.0-openjdk-1.6.0.39-1.13.11.0.el6\_7.x86\_64 today, I > > > > found this in the /var/log/djigzo.log: > > > > ...ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 > > > > [vsyscall] JVM process is gone. JVM exited while loading the > > > > application. Launching a JVM... JVM received a signal UNKNOWN > > > > (6). java version "1.6.0\_39" OpenJDK Runtime Environment > > > > (IcedTea6 1.13.11) (rhel-1.13.11.0.el6\_7-x86\_64) OpenJDK 64-Bit > > > > Server VM (build 23.25-b01, mixed mode) > > > > > > > > \*\*\* glibc detected \*\*\* > > > > /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86\_64/jre/bin/java: > > > > double free or corruption (!prev): 0x0000000001e5ac c0 \*\*\* > > > > ======= Backtrace: ========= > > > > /lib64/libc.so.6(+0x75f4e)[0x7fc450e82f4e] > > > > /lib64/libc.so.6(+0x78cf0)[0x7fc450e85cf0] > > > > /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86\_64/jre/bin/java[0x402fbb] /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86\_64/jre/bin/java(JavaMain+0x51c)[0x40373c] > > > > /lib64/libpthread.so.0(+0x7aa1)[0x7fc4515b0aa1] > > > > /lib64/libc.so.6(clone+0x6d)[0x7fc450ef593d] .... > > > > > > > > There were 10 failed launches in a row, each lasting less than > > > > 300 seconds. Giving up. There may be a configuration problem: > > > > please check the logs. \<-- Wrapper Stopped > > > > > > > > On the Weblogin-page I got the message about a not fully > > > > started background problem. > > > > > > > > Any suggestions are welcome > > > > > > This looks like a bug in Java 6. A similar bug was reported last > > > week: > > > > > > [https://jira.djigzo.com/browse/GATEWAY-101](https://jira.djigzo.com/browse/GATEWAY-101) > > > > > > For now the best solution is to upgrade to Java 6. See bug > > > report #GATEWAY-101 for more information. > > > > > > A possible workaround is to add the following line to the file > > > djigzo.wrapper.conf > > > > > > wrapper.debug=true > > > > > > Let me know whether this work around works for you. It looks like > > > some interaction between Java wrapper (which starts the Java > > > process) and Java 6 update. > > > > > > I will investigate this further. > > > > As a workaround (instead of installing Java 7), you can add > > wrapper.disable\_console\_input=FALSE to the Java wrapper config. You > > can add this option by editing the file /etc/init.d/djigzo > > > > Change > > > > WRAPPER\_OPTS="wrapper.daemonize=TRUE" > > > > To: > > > > WRAPPER\_OPTS="wrapper.daemonize=TRUE > > wrapper.disable\_console\_input=FALSE" > > > > I'll contact the java wrapper developers. It might be some > > interaction bug between changes in Java 6 and java wrapper. > > Hi Martin, > > thank you very much for your fast support. Mailencrypt and decrypt > works fine with the last workaround. But we are running in a new > problem with the weblogin. I always get an ssl-error > (ERR\_SSL\_FALLBACK\_BEYOND\_MINIMUM\_VERSION -\> Chrome) messages in FF > and Chrome when I try to open the login page. It looks like Chrome, FF (and Java 6?) removed support for certain ciphers. In the latest release of CipherMail (3.0.5) the list of supported ciphers was optimized for security reasons (check with ssllabs). However Java 6 does not support all those ciphers. The best for now is to remove the ciphers lists setting from /etc/tomcat6/server.xml. This way Tomcat will provide support for all ciphers Java 6 supports. After changing server.xml, restart tomcat (service tomcat6 restart) Kind regards, Martijn Brinkers > **···** > > On 05/18/2016 11:37 AM, fatcharly(a)gmx.de wrote: > > > > On 05/17/2016 06:16 PM, Martijn Brinkers wrote: > > > > > > > On 05/17/2016 06:02 PM, fatcharly(a)gmx.de wrote: > > -- > CipherMail email encryption > > Email encryption with support for S/MIME, OpenPGP, PDF encryption and > secure webmail pull. > > > **[CipherMail email encryption and digital signatures](https://www.ciphermail.com)** > > > > Easy to use server-side email encryption for automatic encryption and digital signing of email. > > Twitter: [http://twitter.com/CipherMail](http://twitter.com/CipherMail) > > -- > CipherMail email encryption > > Email encryption with support for S/MIME, OpenPGP, PDF encryption and > secure webmail pull. > > > **[CipherMail email encryption and digital signatures](https://www.ciphermail.com)** > > > > Easy to use server-side email encryption for automatic encryption and digital signing of email. > > Twitter: [http://twitter.com/CipherMail](http://twitter.com/CipherMail)