I was looking at the change log for 9.0.71 and i saw this entry

Tomcat changeLog: https://tomcat.apache.org/tomcat-9.0-doc/changelog.html

Bug 66388: https://bz.apache.org/bugzilla/show_bug.cgi?id=66388
Fix: 66388: Correct a regression in the refactoring that replaced the use of the URL constructors. The regression broke lookups for resources that contained one or more characters in their name that required escaping when used in a URI path. (markt)

Bug 66409 (Marked as duplicate to 66388): https://bz.apache.org/bugzilla/show_bug.cgi?id=66409
There was something in 66409 that indicates change in how url is called:

Some investigation on our side showed that org.apache.cataline.webresources.AbstractArchiveResource#getURL() has changed from version 7.0.69 to 7.0.70. Instead of using the java.net.URL directly, java.net.URI(url).toURL() is used now. The problem is, that the URL is not encoded properly.

is this related? The weird thing is that the bug is supposed to be related to blank spaces in url but the url in context file does not have blank spaces.

It seems like we are getting the same error with tomcat 9.0.72. Could there be an issue with AAOD library files ability to connect to database with the new tomcat release?

Validation Error


Context File

Hi All,

I am encountering a strange issue. I am upgrading tomcat to resolve a vulnerability found from VA scan. The fix is to upgrade to Tomcat 9.0.69[/u] or higher.

I have decided to install Tomcat 9.0.71 but i encountered the error [u]Java.SQLSQLException The url cannot be null[/u] when i am trying to validate the database connection for my Orchestration Designer IVR application..

Does anyone have any idea on how to resolve this issue? The database connection succeeds when deployed with Tomcat 6.0.68.
The jdbc driver version used is mssql-jdbc-7.2.1.jre8.jar[u]

Edit: Just tried with Tomcat 9.0.70, AAOD IVR Application Database Validation works.

Hi All,

Seek your suggestions on how i can go about "catching errors" with VXML launched via dialogstart.

Background:
CCXMl is doing an outbound call. Once caller picks up, caller will be directed to this VXML to listen to some information before call is disconnected.

The issue here is that we are encountering error.badfetch.500 intermittently while launching this VXML and the outbound session just gets stuck there until the caller drops the call (caller will experience dead air in the meantime).

This is something i noticed when i was fiddling around with plugins and projects import.

Not sure if the old log4j comes from the plugin itself (oceana pdc plugin) but when the plugin was first installed, a folder was created with the old log4j inside. [Path: E:\Program Files\Eclipse 8.1.2\configuration\org.eclipse.osgi\1015\0\.cp\lib\log4j-1.2.14.jar]

Now, if i remove the 1015 folder and perform a project import that already uses the plugin, the folder 1015 is not created. And if i configure another project to use the plugin, the folder 1015 is new created but i do not locate the old log4j.

I have decided to remove the folder containing the old log4j and check each time the plugin is being newly utilized.

Hi,

Recently customer flagged a vulnerability for org.eclipse.osgi, is there a way to resolve this vulnerability?

I am using AAOD 8.1.2 and the full path scanned is as below:
E:\Program Files\Eclipse 8.1.2\configuration\org.eclipse.osgi\1015\0\.cp\lib\log4j-1.2.14.jar

Hi massimo,

I have tried turning on debug level 7 in tsapi.pro but i do not see any tsapi_tract.txt in the root folder when tomcat service is started.

Hi,

I encountered an issue with running aesconnector, the connector was unable to retrieve the configurations from ddconfig.

The same configurations used for aesconnector 07.20.09.04 works well with no issues. Would like to seek advice on how to resolve this issue. Both tsapi.pro are the same as well.

aesconnrector log

13/06/2022 19:58:50:454 DEBUG - CTIConnectorManager.setTServerWait: TServer wait time is 4
13/06/2022 19:58:50:470 DEBUG - CTIConnectorManager.init: initing AES connector. Verbosity set at 3
13/06/2022 19:58:50:470 DEBUG - CTIConnectorManager.init: AES Connector Version is 08.11.08.01
13/06/2022 19:58:50:470 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Observer timeout interval found: 100
13/06/2022 19:58:50:470 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Provider startup delay found: 4000
13/06/2022 19:58:50:470 DEBUG - CTIConnectorManager.getConnectionString: No entry for TServer in configuration file
13/06/2022 19:58:50:470 DEBUG - CTIConnectorManager.initProvider: Look for TServer config in DD application configuration (new method to 4.0)

Hi Wilson, any ETA for this?

Hmm... it doesnt seem like there is a new release for Orchestration Designer (8.1.1) yet

Hi Wilson, now i understand. i suppose all applications using older Orchestration versions will need to be redeployed and updated using AAOD 8.1.1 in order to fix the log4j issue. Thanks for the information.

Hi Wilson, does that mean we can just update log4j to the latest (log4j 2.15.0) without issues?
The version you have mentioned is also affected by the CVE.

Hi Wilson,

If i am not wrong, log4j 1.2.16 is still vulnerable to 3 CVE's (the same applies to log4j 1.2.17)

Log4j 1.2.x is also End-Of-Life.

Referencing: https://snyk.io/vuln/maven:log4j%3Alog4j

Hi All,

Any tips on how we can go about using the latest version for log4j? It seems that the log4j version from the runtime support files is outdated and recently, there is this high security risk for log4j 2.

I would like to deploy log4j 2.15.0.jar but i am getting error after removing log4j 1.2.15.jar in tomcat lib folder.

Hi,

I would like to understand how to define the URL Parameter Type for input parameters.

Currently there is WSOP Defined, Query and Path. What are the differences between these 3?

If the input required is as below, which parameter needs to be selected?
{
"systemId": "bf07",
"status": "A",
"codeList": [
"06528",
"06529"
]