A customer was facing issue with WFO webpage login. Users are unable to login into the WFO web portal. They are able to get the login page but receiving the following error after entering credentials and pressing Enter.

"Please contact the administrator or technical support specialist to analyze the problem.
Full detail of the error can be found in the log.
Error is: java.rmi.RemoteException: EJB Exception:; nested exception is: java.rmi.RemoteException: Failed to notify login failure; nested exception is: com.bluepumpkin.common.jdmo.JdmoException: DEFAULT"

After going through **<logs path>/ProductionServer/error.log** I saw below lines.

####[ProductionServer]-[common] [2019-10-20 12:33:22.940+0300] [INFO] [QuartzScheduler_BluePumpkinQuartzScheduler-CC-QM-ELEARN1571563822349_ClusterManager] [common.logging.ErrorDumpAppender] <##   ##> - Message: ERROR_DUMP_HEADER

####[]-[] [2019-10-20 12:33:22.940+0300] [ERROR] [QuartzScheduler_BluePumpkinQuartzScheduler-CC-QM-ELEARN1571563822349_ClusterManager] [] <##   ##> - ClusterManager: Error managing cluster: Failed to obtain DB connection from data source 'BluePumpkinDSNonXA': java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc.bpmaindbnonxa' weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "SQL Server returned an incomplete response. The connection has been closed.".

org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'BluePumpkinDSNonXA': java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc.bpmaindbnonxa' weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "SQL Server returned an incomplete response. The connection has been closed.". [See nested exception: java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc.bpmaindbnonxa' weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "SQL Server returned an incomplete response. The connection has been closed.".]

    at org.quartz.impl.jdbcjobstore.JobStoreCMT.getNonManagedTXConnection(JobStoreCMT.java:167)

    at org.quartz.impl.jdbcjobstore.JobStoreSupport.doCheckin(JobStoreSupport.java:3167)

    at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.manage(JobStoreSupport.java:3811)

    at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.run(JobStoreSupport.java:3847)

Caused by: java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc.bpmaindbnonxa' weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "SQL Server returned an incomplete response. The connection has been closed.".

    at org.quartz.utils.JNDIConnectionProvider.getConnection(JNDIConnectionProvider.java:166)

    at org.quartz.utils.DBConnectionManager.getConnection(DBConnectionManager.java:112)

    at org.quartz.impl.jdbcjobstore.JobStoreCMT.getNonManagedTXConnection(JobStoreCMT.java:164)

    ... 3 more

####[ProductionServer]-[common] [2019-10-20 12:33:22.940+0300] [INFO] [QuartzScheduler_BluePumpkinQuartzScheduler-CC-QM-ELEARN1571563822349_ClusterManager] [common.logging.ErrorDumpAppender] <##   ##> - Message: ERROR_DUMP_FOOTER

They key line I observed many times:

**The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "SQL Server returned an incomplete response. The connection has been closed.**

After a lot of googling around, found out that customer had performed TLS/SSL security hardening on the SQL Sever’s Windows registry. After they reverted back, we stopped seeing these errors on the log file and were able to login to the server.

Note: I was lazy to type out the first to lines and so I copied it from Reference #2

References

  1. MSDN Blog: Intermittent JDBC Connectivity issue – The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: SQL Server returned an incomplete response. The connection has been closed
  2. Avaya KB: WFO: Unable To Login To WFO Portal (Application Error)
  3. Avaya KB: WFO: Users are unable to access the WFO web portal. Getting “Page Cannot be Displayed”.
  4. Avaya KB: WFO 12.0: we cant access WFO webpage