ReportServer Forum

reportserveruser

Member

Registered: 2020-11-02

Scheduler error: Could not convert socket to TLS

Hi,

I've been using the report server for quite sometime now and it is a wonderful tool that you folks have created. I'm trying to configure email for the reports which I'm unfortunately unable to do so.

The mail.cf file is as below

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
   <smtp>
      <host>smtp.gmail.com</host>
      <port>587</port>
      <username>randomxxx@gmail.com</username>
      <password>*</password>
      <ssl>false</ssl>
      <tls>
         <enable>true</enable>
         <require>false</require>
      </tls>
   </smtp>
   <mail>
      <sender>randomxxx@gmail.com</sender>
      <senderName>ReportServer</senderName>
      <forceSender>false</forceSender>
      <encryptionPolicy>allow_mixed</encryptionPolicy>
   </mail>
</configuration>

The stack trace is as below

java.lang.RuntimeException: javax.mail.MessagingException: Could not convert socket to TLS;
  nested exception is:
    java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)
        at net.datenwerke.rs.scheduler.service.scheduler.mail.MailReportAction$1.handleException(MailReportAction.java:149)
        at net.datenwerke.rs.core.service.mail.MailServiceImpl.sendMailSync(MailServiceImpl.java:247)
        at net.datenwerke.rs.scheduler.service.scheduler.mail.MailReportAction.doExecute(MailReportAction.java:140)
        at net.datenwerke.scheduler.service.scheduler.entities.AbstractAction.execute(AbstractAction.java:59)
        at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.executeAction(SchedulerTask.java:614)
        at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.executeActions(SchedulerTask.java:502)
        at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.safeCall(SchedulerTask.java:211)
        at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.call(SchedulerTask.java:103)
        at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.call(SchedulerTask.java:1)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:834)
    Caused by: javax.mail.MessagingException: Could not convert socket to TLS;
  nested exception is:
    java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)
        at com.sun.mail.smtp.SMTPTransport.startTLS(SMTPTransport.java:1918)
        at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:652)
        at javax.mail.Service.connect(Service.java:317)
        at javax.mail.Service.connect(Service.java:176)
        at javax.mail.Service.connect(Service.java:125)
        at javax.mail.Transport.send0(Transport.java:194)
        at javax.mail.Transport.send(Transport.java:124)
        at net.datenwerke.rs.core.service.mail.MailServiceImpl.sendMailSync(MailServiceImpl.java:237)
        ... 11 more
    Caused by: java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)
        at java.base/javax.net.ssl.DefaultSSLSocketFactory.throwException(SSLSocketFactory.java:263)
        at java.base/javax.net.ssl.DefaultSSLSocketFactory.createSocket(SSLSocketFactory.java:285)
        at com.sun.mail.util.SocketFetcher.startTLS(SocketFetcher.java:484)
        at com.sun.mail.smtp.SMTPTransport.startTLS(SMTPTransport.java:1913)
        ... 18 more
    Caused by: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)
        at java.base/java.security.Provider$Service.newInstance(Provider.java:1831)
        at java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:236)
        at java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:164)
        at java.base/javax.net.ssl.SSLContext.getInstance(SSLContext.java:168)
        at java.base/javax.net.ssl.SSLContext.getDefault(SSLContext.java:99)
        at java.base/javax.net.ssl.SSLSocketFactory.getDefault(SSLSocketFactory.java:123)
        at com.sun.mail.util.SocketFetcher.startTLS(SocketFetcher.java:479)
        ... 19 more
    Caused by: java.lang.NullPointerException: No password supplied for PKCS#12 KeyStore.
        at org.bouncycastle.jce.provider.JDKPKCS12KeyStore.engineLoad(Unknown Source)
        at java.base/java.security.KeyStore.load(KeyStore.java:1479)
        at java.base/sun.security.ssl.TrustStoreManager$TrustAnchorManager.loadKeyStore(TrustStoreManager.java:365)
        at java.base/sun.security.ssl.TrustStoreManager$TrustAnchorManager.getTrustedCerts(TrustStoreManager.java:313)
        at java.base/sun.security.ssl.TrustStoreManager.getTrustedCerts(TrustStoreManager.java:55)
        at java.base/sun.security.ssl.TrustManagerFactoryImpl.engineInit(TrustManagerFactoryImpl.java:49)
        at java.base/javax.net.ssl.TrustManagerFactory.init(TrustManagerFactory.java:278)
        at java.base/sun.security.ssl.SSLContextImpl$DefaultManagersHolder.getTrustManagers(SSLContextImpl.java:1053)
        at java.base/sun.security.ssl.SSLContextImpl$DefaultManagersHolder.<clinit>(SSLContextImpl.java:1023)
        at java.base/sun.security.ssl.SSLContextImpl$DefaultSSLContext.<init>(SSLContextImpl.java:1198)
        at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
        at java.base/java.security.Provider.newInstanceUtil(Provider.java:153)
        at java.base/java.security.Provider$Service.newInstance(Provider.java:1824)
        ... 25 more
02-Nov-2020 12:53:17.493 WARNING [pool-7-thread-1] net.datenwerke.rs.core.service.mail.MailServiceImpl$1.run Mail could not be send
    net.datenwerke.rs.core.service.mail.exceptions.MailerRuntimeException: Mail could not be send
        at net.datenwerke.rs.core.service.mail.MailServiceImpl$MailSupervisorImpl.handleException(MailServiceImpl.java:58)
        at net.datenwerke.rs.core.service.mail.MailServiceImpl.sendMailSync(MailServiceImpl.java:247)
        at net.datenwerke.rs.core.service.mail.MailServiceImpl$1.run(MailServiceImpl.java:270)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:834)
    Caused by: javax.mail.MessagingException: Could not convert socket to TLS;
  nested exception is:
    java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)
        at com.sun.mail.smtp.SMTPTransport.startTLS(SMTPTransport.java:1918)
        at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:652)
        at javax.mail.Service.connect(Service.java:317)
        at javax.mail.Service.connect(Service.java:176)
        at javax.mail.Service.connect(Service.java:125)
        at javax.mail.Transport.send0(Transport.java:194)
        at javax.mail.Transport.send(Transport.java:124)
        at net.datenwerke.rs.core.service.mail.MailServiceImpl.sendMailSync(MailServiceImpl.java:237)
        ... 4 more
    Caused by: java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)
        at java.base/javax.net.ssl.DefaultSSLSocketFactory.throwException(SSLSocketFactory.java:263)
        at java.base/javax.net.ssl.DefaultSSLSocketFactory.createSocket(SSLSocketFactory.java:285)
        at com.sun.mail.util.SocketFetcher.startTLS(SocketFetcher.java:484)
        at com.sun.mail.smtp.SMTPTransport.startTLS(SMTPTransport.java:1913)
        ... 11 more
    Caused by: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)
        at java.base/java.security.Provider$Service.newInstance(Provider.java:1831)
        at java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:236)
        at java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:164)
        at java.base/javax.net.ssl.SSLContext.getInstance(SSLContext.java:168)
        at java.base/javax.net.ssl.SSLContext.getDefault(SSLContext.java:99)
        at java.base/javax.net.ssl.SSLSocketFactory.getDefault(SSLSocketFactory.java:123)
        at com.sun.mail.util.SocketFetcher.startTLS(SocketFetcher.java:479)
        ... 12 more
    Caused by: java.lang.NullPointerException: No password supplied for PKCS#12 KeyStore.
        at org.bouncycastle.jce.provider.JDKPKCS12KeyStore.engineLoad(Unknown Source)
        at java.base/java.security.KeyStore.load(KeyStore.java:1479)
        at java.base/sun.security.ssl.TrustStoreManager$TrustAnchorManager.loadKeyStore(TrustStoreManager.java:365)
        at java.base/sun.security.ssl.TrustStoreManager$TrustAnchorManager.getTrustedCerts(TrustStoreManager.java:313)
        at java.base/sun.security.ssl.TrustStoreManager.getTrustedCerts(TrustStoreManager.java:55)
        at java.base/sun.security.ssl.TrustManagerFactoryImpl.engineInit(TrustManagerFactoryImpl.java:49)
        at java.base/javax.net.ssl.TrustManagerFactory.init(TrustManagerFactory.java:278)
        at java.base/sun.security.ssl.SSLContextImpl$DefaultManagersHolder.getTrustManagers(SSLContextImpl.java:1053)
        at java.base/sun.security.ssl.SSLContextImpl$DefaultManagersHolder.<clinit>(SSLContextImpl.java:1023)
        at java.base/sun.security.ssl.SSLContextImpl$DefaultSSLContext.<init>(SSLContextImpl.java:1198)
        at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
        at java.base/java.security.Provider.newInstanceUtil(Provider.java:153)
        at java.base/java.security.Provider$Service.newInstance(Provider.java:1824)
        at java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:236)
        at java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:164)
        at java.base/javax.net.ssl.SSLContext.getInstance(SSLContext.java:168)
        at java.base/javax.net.ssl.SSLContext.getDefault(SSLContext.java:99)
        at java.base/javax.net.ssl.SSLSocketFactory.getDefault(SSLSocketFactory.java:123)
        at com.sun.mail.util.SocketFetcher.startTLS(SocketFetcher.java:479)
        at com.sun.mail.smtp.SMTPTransport.startTLS(SMTPTransport.java:1913)
        at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:652)
        at javax.mail.Service.connect(Service.java:317)
        at javax.mail.Service.connect(Service.java:176)
        at javax.mail.Service.connect(Service.java:125)
        at javax.mail.Transport.send0(Transport.java:194)
        at javax.mail.Transport.send(Transport.java:124)
        at net.datenwerke.rs.core.service.mail.MailServiceImpl.sendMailSync(MailServiceImpl.java:237)
        at net.datenwerke.rs.scheduler.service.scheduler.mail.MailReportAction.doExecute(MailReportAction.java:140)
        at net.datenwerke.scheduler.service.scheduler.entities.AbstractAction.execute(AbstractAction.java:59)
        at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.executeAction(SchedulerTask.java:614)
        at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.executeActions(SchedulerTask.java:502)
        at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.safeCall(SchedulerTask.java:211)
        at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.call(SchedulerTask.java:103)
        at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.call(SchedulerTask.java:1)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        ... 3 more

Could you please help as to what I could be doing wrong and why the email functionality is not working as it should?

eduardo

Administrator

Registered: 2016-11-01

Website

Re: Scheduler error: Could not convert socket to TLS

Hi reportserveruser,

this seems to be an issue with Java 9 or 11.
You can correct it by adding this option:

-Djavax.net.ssl.trustStoreType=JKS

e.g. in your Tomcat setenv.sh file:

CATALINA_OPTS="-Djavax.net.ssl.trustStoreType=JKS"

After a tomcat restart this should work.

Regards,
Eduardo

reportserveruser

Member

Registered: 2020-11-02

Re: Scheduler error: Could not convert socket to TLS

Hello Eduardo,

Thank you for the response. I'm using a Windows machine so I guess I will have to change the setenv.bat file, right? The setenv.bat file already exists in the apache-tomcat/bin directory. Please find the contents below. As you can see I've added the last line as suggested by you but the exception continues to show.

set JAVA_HOME=E:\Report_Server\Bitnami\reportserver-3.1.2.6022-0\java
set JRE_HOME=%JAVA_HOME%
set JAVA_OPTS=++JvmOptions="-Drs.configdir=E:\Report_Server\Bitnami\reportserver-3.1.2.6022-0/apps/reportserver/reportserver-conf" ++JvmOptions="-Dfile.encoding=UTF8" --JvmMs 512 --JvmMx 1536
set JDK_JAVA_OPTIONS=--add-opens=java.base/java.net=ALL-UNNAMED %JDK_JAVA_OPTIONS%
set CATALINA_OPTS="-Djavax.net.ssl.trustStoreType=JKS"

I also removed the double quotes but the exception continues to persist

set JAVA_HOME=E:\Report_Server\Bitnami\reportserver-3.1.2.6022-0\java
set JRE_HOME=%JAVA_HOME%
set JAVA_OPTS=++JvmOptions="-Drs.configdir=E:\Report_Server\Bitnami\reportserver-3.1.2.6022-0/apps/reportserver/reportserver-conf" ++JvmOptions="-Dfile.encoding=UTF8" --JvmMs 512 --JvmMx 1536
set JDK_JAVA_OPTIONS=--add-opens=java.base/java.net=ALL-UNNAMED %JDK_JAVA_OPTIONS%
set CATALINA_OPTS=-Djavax.net.ssl.trustStoreType=JKS

Please advice.

Last edited by reportserveruser (2020-11-02 12:31:47)

eduardo

Administrator

Registered: 2016-11-01

Website

Re: Scheduler error: Could not convert socket to TLS

Hi reportserveruser,

in later Bitnami packages this will already be preconfigured. For example, the setenv.bat file for 3.3.0 contains the following:

set JAVA_OPTS=++JvmOptions="-Drs.configdir=C:\Bitnami\reportserverenterprise-3.3.0.6030-0/apps/reportserver/reportserver-conf" ++JvmOptions="-Dfile.encoding=UTF8" ++JvmOptions="--add-opens=java.base/java.net=ALL-UNNAMED" ++JvmOptions="--add-opens=java.base/jdk.internal.ref=ALL-UNNAMED" ++JvmOptions="-Djavax.net.ssl.trustStoreType=JKS" --JvmMs 512 --JvmMx 1536

There, you see this: ++JvmOptions="-Djavax.net.ssl.trustStoreType=JKS"

It should work as shown here after a tomcat restart, please let us know.

Regards,
Eduardo

reportserveruser

Member

Registered: 2020-11-02

Re: Scheduler error: Could not convert socket to TLS

Hello Eduardo,

Still no luck. I've pasted the modified contents of the setenv.bat below -

set JAVA_HOME=E:\Report_Server\Bitnami\reportserver-3.1.2.6022-0\java
set JRE_HOME=%JAVA_HOME%
set JAVA_OPTS=++JvmOptions="-Drs.configdir=E:\Report_Server\Bitnami\reportserver-3.1.2.6022-0/apps/reportserver/reportserver-conf" ++JvmOptions="-Dfile.encoding=UTF8" ++JvmOptions="-Djavax.net.ssl.trustStoreType=JKS" --JvmMs 512 --JvmMx 1536
set JDK_JAVA_OPTIONS=--add-opens=java.base/java.net=ALL-UNNAMED %JDK_JAVA_OPTIONS%

eduardo

Administrator

Registered: 2016-11-01

Website

Re: Scheduler error: Could not convert socket to TLS

Hi reportserveruser,

what do you see in your reportserver tomcat log? You should see something similar as:

  _____                       _    _____                            ______       _                       _          
 |  __ \                     | |  / ____|                          |  ____|     | |                     (_)         
 | |__) |___ _ __   ___  _ __| |_| (___   ___ _ ____   _____ _ __  | |__   _ __ | |_ ___ _ __ _ __  _ __ _ ___  ___ 
 |  _  // _ \ '_ \ / _ \| '__| __|\___ \ / _ \ '__\ \ / / _ \ '__| |  __| | '_ \| __/ _ \ '__| '_ \| '__| / __|/ _ \
 | | \ \  __/ |_) | (_) | |  | |_ ____) |  __/ |   \ V /  __/ |    | |____| | | | ||  __/ |  | |_) | |  | \__ \  __/
 |_|  \_\___| .__/ \___/|_|   \__|_____/ \___|_|    \_/ \___|_|    |______|_| |_|\__\___|_|  | .__/|_|  |_|___/\___|
            | |                                                                              | |                    
            |_|                                                                              |_|                    

Version: RS3.3.0-6030 2020-09-25-11-16-41
Code Version: 2020-09-25-10-02-31
Java Version: BellSoft OpenJDK 64-Bit Server VM 11.0.8+10-LTS (11)
VM Args: -Dcatalina.home=C:\Bitnami\REPORT~1.603\APACHE~1 -Dcatalina.base=C:\Bitnami\REPORT~1.603\APACHE~1 -Dignore.endorsed.dirs=C:\Bitnami\REPORT~1.603\APACHE~1\endorsed -Djava.io.tmpdir=C:\Bitnami\REPORT~1.603\APACHE~1\temp -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=C:\Bitnami\REPORT~1.603\APACHE~1\conf\logging.properties -Drs.configdir=C:\Bitnami\reportserverenterprise-3.3.0.6030-0/apps/reportserver/reportserver-conf -Dfile.encoding=UTF8 --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/jdk.internal.ref=ALL-UNNAMED -Djavax.net.ssl.trustStoreType=JKS --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED exit abort -Xms512m -Xmx1536m
rs.configdir: C:\Bitnami\reportserverenterprise-3.3.0.6030-0\apps\reportserver\reportserver-conf (OK)

There, in the VM Args section, you should see: -Djavax.net.ssl.trustStoreType=JKS  if the configuration works.

Our Bitnami installation in 3.3.0 contains exactly the following:

set JAVA_HOME=C:\Bitnami\REPORT~1.603\java
set JRE_HOME=%JAVA_HOME%
set JAVA_OPTS=++JvmOptions="-Drs.configdir=C:\Bitnami\reportserverenterprise-3.3.0.6030-0/apps/reportserver/reportserver-conf" ++JvmOptions="-Dfile.encoding=UTF8" ++JvmOptions="--add-opens=java.base/java.net=ALL-UNNAMED" ++JvmOptions="--add-opens=java.base/jdk.internal.ref=ALL-UNNAMED" ++JvmOptions="-Djavax.net.ssl.trustStoreType=JKS" --JvmMs 512 --JvmMx 1536
set JDK_JAVA_OPTIONS= %JDK_JAVA_OPTIONS%

which outputs the log above. Can you pls check ?

Regards,
Eduardo

reportserveruser

Member

Registered: 2020-11-02

Re: Scheduler error: Could not convert socket to TLS

Hello Eduardo,

I'm not able to see -Djavax.net.ssl.trustStoreType=JKS in the logs.

  _____                       _    _____                         
|  __ \                     | |  / ____|                         
| |__) |___ _ __   ___  _ __| |_| (___   ___ _ ____   _____ _ __
|  _  // _ \ '_ \ / _ \| '__| __|\___ \ / _ \ '__\ \ / / _ \ '__|
| | \ \  __/ |_) | (_) | |  | |_ ____) |  __/ |   \ V /  __/ |   
|_|  \_\___| .__/ \___/|_|   \__|_____/ \___|_|    \_/ \___|_|   
            | |                                                   
            |_|                                                   

Version: RS3.1.2-6022 2020-04-01-15-17-05
Code Version: 2020-04-01-14-55-32
Java Version: AdoptOpenJDK OpenJDK 64-Bit Server VM 11.0.6+10 (11)
VM Args: -Dcatalina.home=E:\Report_Server\Bitnami\reportserver-3.1.2.6022-0\apache-tomcat -Dcatalina.base=E:\Report_Server\Bitnami\reportserver-3.1.2.6022-0\apache-tomcat -Dignore.endorsed.dirs=E:\Report_Server\Bitnami\reportserver-3.1.2.6022-0\apache-tomcat\endorsed -Djava.io.tmpdir=E:\Report_Server\Bitnami\reportserver-3.1.2.6022-0\apache-tomcat\temp -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=E:\Report_Server\Bitnami\reportserver-3.1.2.6022-0\apache-tomcat\conf\logging.properties -Drs.configdir=E:\Report_Server\Bitnami\reportserver-3.1.2.6022-0/apps/reportserver/reportserver-conf -Dfile.encoding=UTF8 --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED exit abort -Xms512m -Xmx1536m
rs.configdir: E:\Report_Server\Bitnami\reportserver-3.1.2.6022-0\apps\reportserver\reportserver-conf (OK)

Is there some issue with my setenv.bat file?

set JAVA_HOME=E:\Report_Server\Bitnami\reportserver-3.1.2.6022-0\java
set JRE_HOME=%JAVA_HOME%
set JAVA_OPTS=++JvmOptions="-Drs.configdir=E:\Report_Server\Bitnami\reportserver-3.1.2.6022-0/apps/reportserver/reportserver-conf" ++JvmOptions="-Dfile.encoding=UTF8" ++JvmOptions="-Djavax.net.ssl.trustStoreType=JKS" --JvmMs 512 --JvmMx 1536
set JDK_JAVA_OPTIONS=--add-opens=java.base/java.net=ALL-UNNAMED %JDK_JAVA_OPTIONS%

reportserveruser

Member

Registered: 2020-11-02

Re: Scheduler error: Could not convert socket to TLS

Hello Eduardo,

Could you please verify if the changes I've made to the setenv.bat file are correct? Is there a specific way to change the bat file? Please guide.

eduardo

Administrator

Registered: 2016-11-01

Website

Re: Scheduler error: Could not convert socket to TLS

Hi reportserveruser,

since you are using the Bitnami package, you have to reinstall the service for changes in setenv.bat to load.

Pls check here how you can reinstall the service: https://docs.bitnami.com/installer/infr … at-memory/
The example explains how to modify memory settings, but this should be used analogously for -Djavax.net.ssl.trustStoreType=JKS

You can again check in the tomcat logs for the VM Args:, where you will see if this is loaded correctly.

Regards,
Eduardo

reportserveruser

Member

Registered: 2020-11-02

Re: Scheduler error: Could not convert socket to TLS

Hello Eduardo,

I followed your instructions and the setenv.bat loaded successfully. After this I got another exception - java.lang.RuntimeException: javax.mail.AuthenticationFailedException

I got rid of the exception by modifying the below Gmail security settings -

1. Clearing Captcha
2. Using Less Secure Apps

Thank you so much Eduardo and team for patiently helping me through this. Much appreciated!

eduardo

Administrator

Registered: 2016-11-01

Website

Re: Scheduler error: Could not convert socket to TLS

Hi reportserveruser,

I am glad this worked

Regards,
Eduardo