Pool error message in app-ca.log when running GEL script

[Paul Schofield]

Hi everyone, has anyone seen this error when executing a GEL script as a process:

ERROR 2025-10-08 06:05:46,681 [Custom script execution pool-20-thread-3] union.gel
(clarity:admin:5270087__67BC862E-2413-4E60-AF41-9DB5E4D816A2:none) () GEL Script not using the correct connection pool! - ApplicationName: null

The script works but it doesn't log anything in the process log if I use <gel:log> even though the log level is set to INFO.

It does log to app-ca.log using <gel:out> though.

Any ideas?

Paul

-------------------------------------------

[Luis Palacios]

Hi Paul, how are you opening connection to the DB or initializing connections. In parallel, for the gel:log portion, what is the process messages persistence set up as under logger config

-------------------------------------------

[Nika Hadzhikidi]

Paul, we introduced GEL Connection pool in 16.2.0, which version are you on exactly? Was this ever working before? 

It would be helpful to see how the datasource connection is called as Luis mentioned.

------------------------------
Nika Hadzhikidi
Sr Principal Support Engineer
Broadcom
------------------------------

[Paul Schofield]

Thank you both for the replies. It's a 16.3.1 installation, set up with logging level as INFO.

This is a simple script to illustrate things:

<gel:script 

 

xmlns:core="jelly:core" 

xmlns:gel="jelly:com.niku.union.gel.GELTagLibrary"

xmlns:sql="jelly:sql">

 

<gel:setDataSource dbId="niku" var="clarityDS"/>

 

<sql:query dataSource="${clarityDS}" var="projects" escapeText="false">

SELECT id, name, description FROM inv_investments

</sql:query>

 

<core:forEach items="${projects.rows}" var="project">

<gel:log level="INFO" message="${project.id} ${project.name} ${project.description}"/>

</core:forEach>

 

</gel:script>

It works fine in another system (16.3.3) but doesn't in the training system. I originally didn't have the clarityDS variable in there, but added it to see if that fixed things, but it didn't.

Paul

-------------------------------------------

[Luis Palacios]

Hi Paul,

if another env same version, does work. Have you checked properties.xml across the server running the BG and the other env. The snippet looks OK

-------------------------------------------

[Paul Schofield]

Hi again,

This is a small environment and there is only 1 server running everything. The properties files look the same (except for URLs and email being disabled). Where are the settings for this new pooling functionality? I don't see anything in the file or the NSA.

-------------------------------------------

[Nika Hadzhikidi]

Paul,

On 16.3.1 the GEL connection pool will be enabled by default, and it looks like this message would not be thrown otherwise.

I tested on SQL server – 16.3.1 and also 16.3.3 with your GEL script.

I was not able to reproduce the issue. I am thinking it has to do with your JDBC URL connection details. Do you mind sharing your properties.xml in a private message, with removed passwords.

One thing you can try is disable feature GEL_CONNECTION_POOL_S253100 on 16.3.1, and try the process again. Here is the KB with the command, use GEL_CONNECTION_POOL_S253100 for feature code  https://broadcomcms-software.wolkenservicedesk.com/external/article?articleNumber=370735

Here is the information on the GEL connection pool:

https://broadcomcms-software.wolkenservicedesk.com/external/article?articleNumber=393435

------------------------------
Nika Hadzhikidi
Sr Principal Support Engineer
Broadcom
------------------------------

[Paul Schofield]

Hi again, I couldn't find the problem but I upgraded the training server to 16.3.3 and everything is working as expected now.

-------------------------------------------

[Nika Hadzhikidi]

Thank you Paul for the update & glad upgrading helped. I was not able to identify why this value was coming up as null for you. We have internal code that sets a default that should be there. If you run across this again let me know. 

------------------------------
Nika Hadzhikidi
Sr Principal Support Engineer
Broadcom
------------------------------