Clarity runs on Oracle 19c, however there are processes that connect to external SQL Server database 2016/2019 which started failing after the upgrade to 16.0.3.
STEPS TO REPRODUCE:
1.On Clarity server running Oracle
2.Create a process with GEL Script
<gel:script
xmlns:gel="jelly:com.niku.union.gel.GELTagLibrary"
xmlns:ftp="jelly:com.niku.union.gel.FTPTagLibrary"
xmlns:file="jelly:com.niku.union.gel.FileTagLibrary"
xmlns:core="jelly:core"
xmlns:sql="jelly:sql">
<sql:setDataSource var="omega" url="jdbc:sqlserver://host:1433;DatabaseName=clarity;" driver="com.microsoft.sqlserver.jdbc.SQLServerDriver" user="pwd" password="pwd"/>
<sql:query dataSource="${omega}" escapeText="0" var="results2">
SELECT id from FROM SRM_RESOURCES where is_active = 1
</sql:query>
</gel:script>
3.Activate and run the process:
Expected: The process should finish.
Actual: The process errors:
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(SqlTagSupport.java:156) at com.niku.union.gel.tags.sql.QueryTag.getConnection(QueryTag.java:57) at org.apache.commons.jelly.tags.sql.QueryTag.doTag(QueryTag.java:134) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:248) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187) at com.niku.union.gel.tags.ScriptTag.doTag(ScriptTag.java:20) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:248) at com.niku.union.gel.GELScript.run(GELScript.java:58) at com.niku.union.gel.GELController.invoke(GELController.java:79) at com.niku.bpm.services.ExecuteCustomAction.run(ExecuteCustomAction.java:217) 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:829)
Release : 16.0.3
This is reported as DE67822 and will be under Engineering review.