nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Disable LSCS on runtime

Samir_Friend

Hi,

To check for a performance issue on our runtime server (not TeamSite) I need to disable LSCS and more specifically rules execution for targeting.

I disabled it by changing the property lscs.enabled to false in the content.properties and restarted the LSDS server but it seems that LSCS queries are still getting fired. Is there any place else I need to change something?

This is urgent. Appreciate a quick response.

Thanks.

Find more posts tagged with

Comments

mart2001

If you use Tomcat and don't host any other apps on that Tomcat instance, you can just stop that Tomcat instance. If you use Websphere or Weblogic, go to the admin console and you can stop the LSCS instance.

Samir_Friend

If you use Tomcat and don't host any other apps on that Tomcat instance, you can just stop that Tomcat instance. If you use Websphere or Weblogic, go to the admin console and you can stop the LSCS instance.

So does it mean that changing these property values on runtime doesn't have any effect?

Also, if I stop that tomcat instance, the rules will still be executed and pages will throw an error. It needs to be disabled at the root.

Rick Poulin

So does it mean that changing these property values on runtime doesn't have any effect?

Also, if I stop that tomcat instance, the rules will still be executed and pages will throw an error. It needs to be disabled at the root.

AFAIK, you can't just "turn off" LSCS functionality from your pages. The controllers and externals don't care about the lscs.enabled property. Once those are executed by a page, they'll be looking for your LSCS instance. The only way to turn if off is to write wrapper classes around the default ones that look at that property.

(also AFAIK, that property is only used by the deployment process. The runtime side only looks at the connection properties, and it will connect as soon as any external/controller attempts to do so)

Samir_Friend

AFAIK, you can't just "turn off" LSCS functionality from your pages. The controllers and externals don't care about the lscs.enabled property. Once those are executed by a page, they'll be looking for your LSCS instance. The only way to turn if off is to write wrapper classes around the default ones that look at that property.

(also AFAIK, that property is only used by the deployment process. The runtime side only looks at the connection properties, and it will connect as soon as any external/controller attempts to do so)

I was afraid it would come to this. Thanks anyway Rick.