Post Upgrade to 16.0.3 Via Process GEL Scripts Connecting to External MS SQL Server Database Fails
search cancel

Post Upgrade to 16.0.3 Via Process GEL Scripts Connecting to External MS SQL Server Database Fails


Article ID: 256519


Updated On:


Clarity PPM On Premise


Post upgrade to 16.0.3, using external connection as MS SQL Server in the process fails

Steps to Reproduce

  1. On Clarity server running Oracle
  2. Create a process with GEL Script
  3. Activate and run the process

Expected Results: The process should be able to connect to external connection and finish 

Actual Results: The process errors with below error stack 

BPM-0704: An error occurred while executing custom script: org.apache.commons.jelly.JellyTagException: null:6:83: <sql:query> Unable to get connection, DataSource invalid: "No suitable driver found for jdbc:sqlserver://<host>:1433;DatabaseName=clarity;" at org.apache.commons.jelly.tags.sql.SqlTagSupport.getConnection( at com.niku.union.gel.tags.sql.QueryTag.getConnection( at org.apache.commons.jelly.tags.sql.QueryTag.doTag( at at at org.apache.commons.jelly.TagSupport.invokeBody( at com.niku.union.gel.tags.ScriptTag.doTag( at at at com.niku.union.gel.GELController.invoke( at at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker( at java.base/java.util.concurrent.ThreadPoolExecutor$ at java.base/


Release : 16.0.3 and onwards 


This is due to how connection classes are handled in clarity 


  • Create a tag in properties.xml in order for clarity to connect to an external connection 

 <database id="Test" jndiDatabaseId="jdbc/TestDS" vendor="mssql" serviceName="niku" serviceId="Test" driver="" url="jdbc:sqlserver://localhost:1433;DatabaseName=Test;encrypt=false" username="Test" password="Clarity#1234" schemaName="Test" upgradeStatus="upgradeNotNeeded"/>