Persistent nlserver_web_xxx cursor locking tables in adobe campaign classic v7

Question

We are encountering a recurring issue in our Adobe Campaign environment involving a persistent database cursor process that appears to be related to nlserver_web_xxx. Specifically, we are observing entries such as:

Fetch 30 FROM cur2383

This cursor remains in an active state in the database and does not get released, even though there are no active campaigns or workflows running at the time. As a result, it is locking certain tables that are critical for our nightly data refresh processes.

What is the purpose of this nlserver_web_xxx process and the associated cursor (e.g., cur2383)?
Why does the cursor remain active and not get released automatically?

_Manoj_Kumar_ · Answer

Hello @kien_kienma Web process is used in multiple ways

to preview delivery
to show mirror page
For redirections and tracking

I believe you are seeing an issue on your Marketing instance. First of all this is an DB issue, the Postgres should be responsible for releasing the cursor.

The main reason is the volume to data being processed on your instance and DB is not able to process all of that.

Here are few thing you can do to identify the root cause and fix it.

Ask Adobe to restart the web instance and clear any long running queries in DB.
Start Monitoring your instance for long running activities in the workflow and check control panel to long running queries.
The first query that you will see in Control panel will help you identify the problematic workflow
Optimize workflow to improve runtime or performance.

Long term fix: Upgrade to latest version campaign or Upsize the Hardware.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded