topic Re: Stack Tracing still active after disabling in ThingWorx Developers

Stack Tracing still active after disabling

AlessandroN — Mon, 28 Apr 2025 10:25:27 GMT

Hi, i'm using ThingWorx 9.3.9-b1648, and I'm seeing a lost of logs related to the Stack Tracing feature.
Even after disabling it, the system still generates these logs.
Has anyone else experienced this issue?

Re: Stack Tracing still active after disabling

Surya_Tiwari — Mon, 28 Apr 2025 10:33:06 GMT

Hi @AlessandroN Have you disabled it from LoggingSubsystem > Configuration > Enable Stack Tracing?

Can you share your logs?

Re: Stack Tracing still active after disabling

AlessandroN — Mon, 28 Apr 2025 11:43:43 GMT

Hi @Surya_Tiwari , yes I tried to disable it several times, but unsuccessfully.

I paste here an extract of Application Logs, because are just full of these kind of lines:

are no subscribers to publisher Connectable 2025-04-28 13:40:12.813+0200 [L: TRACE] [O: c.t.s.s.i.SubscriptionStore] [I: ] [U: Administrator] [S: ] [P: ] [T: TWEventProcessor-8] There are no subscribers to publisher RemoteThing 2025-04-28 13:40:12.813+0200 [L: TRACE] [O: c.t.s.s.i.SubscriptionStore] [I: ] [U: Administrator] [S: ] [P: ] [T: TWEventProcessor-8] There are no subscribers to publisher GenericThing 2025-04-28 13:40:12.813+0200 [L: TRACE] [O: c.t.s.s.i.SubscriptionStore] [I: ] [U: Administrator] [S: ] [P: ] [T: TWEventProcessor-8] There are no subscribers to publisher RemoteThingWithTunnelsAndFileTransfer 2025-04-28 13:40:12.813+0200 [L: TRACE] [O: c.t.s.s.i.SubscriptionStore] [I: ] [U: Administrator] [S: ] [P: ] [T: TWEventProcessor-8] There are no subscribers to publisher Reportable 2025-04-28 13:40:12.813+0200 [L: TRACE] [O: c.t.w.c.ThreadLocalContext] [I: ] [U: Administrator] [S: ] [P: ] [T: TWEventProcessor-8] ----> CURRENT security context [user: Administrator, depth: 1] 2025-04-28 13:40:12.813+0200 [L: TRACE] [O: c.t.s.s.i.SubscriptionStore] [I: ] [U: Administrator] [S: ] [P: ] [T: TWEventProcessor-8] Firing AnyDataChange on Thing: Stazione_Programmazione_L16_4 2025-04-28 13:40:12.813+0200 [L: TRACE] [O: c.t.s.s.i.SubscriptionStore] [I: ] [U: Administrator] [S: ] [P: ] [T: TWEventProcessor-12] There are no subscribers to publisher Stazione_Programmazione_L12_3 2025-04-28 13:40:12.813+0200 [L: TRACE] [O: c.t.s.s.i.SubscriptionStore] [I: ] [U: Administrator] [S: ] [P: ] [T: TWEventProcessor-12] There are no subscribers to publisher RemoteThing 2025-04-28 13:40:12.813+0200 [L: TRACE] [O: c.t.s.s.i.SubscriptionStore] [I: ] [U: Administrator] [S: ] [P: ] [T: TWEventProcessor-12] There are no subscribers to publisher GenericThing 2025-04-28 13:40:12.813+0200 [L: TRACE] [O: c.t.s.s.i.SubscriptionStore] [I: ] [U: Administrator] [S: ] [P: ] [T: TWEventProcessor-12] There are no subscribers to publisher RemoteThingWithTunnelsAndFileTransfer 2025-04-28 13:40:12.813+0200 [L: TRACE] [O: c.t.s.s.i.SubscriptionStore] [I: ] [U: Administrator] [S: ] [P: ] [T: TWEventProcessor-12] There are no subscribers to publisher Reportable 2025-04-28 13:40:12.813+0200 [L: TRACE] [O: c.t.w.c.ThreadLocalContext] [I: ] [U: Administrator] [S: ] [P: ] [T: TWEventProcessor-1] ----> CURRENT security context [user: Administrator, depth: 1] 2025-04-28 13:40:12.813+0200 [L: TRACE] [O: c.t.s.s.i.SubscriptionStore] [I: ] [U: Administrator] [S: ] [P: ] [T: TWEventProcessor-16] There are no subscribers to publisher GenericThing 2025-04-28 13:40:12.813+0200 [L: TRACE] [O: c.t.w.c.ThreadLocalContext] [I: ] [U: Administrator] [S: ] [P: ] [T: TWEventProcessor-14] ----> CURRENT security context [user: Administrator, depth: 1] 2025-04-28 13:40:12.813+0200 [L: DEBUG] [O: c.t.t.c.RemoteThing] [I: ] [U: Administrator] [S: ] [P: ] [T: TWEventProcessor-14] Performing property read from CACHE: [name = isConnected, value = false] 2025-04-28 13:40:12.813+0200 [L: TRACE] [O: c.t.w.c.ThreadLocalContext] [I: ] [U: Administrator] [S: ] [P: ] [T: TWEventProcessor-14] ----> CURRENT security context [user: Administrator, depth: 1] 2025-04-28 13:40:12.813+0200 [L: TRACE] [O: c.t.s.s.i.SubscriptionStore] [I: ] [U: Administrator] [S: ] [P: ] [T: TWEventProcessor-16] Ther

Re: Stack Tracing still active after disabling

AlessandroN — Mon, 28 Apr 2025 11:52:13 GMT

Hi @Surya_Tiwari , yes I've already tried to disable it several times but unsuccessfully.

Which logs do you need? Because the Application logs are just full of these kind of lines:

Re: Stack Tracing still active after disabling

AlessandroN — Mon, 28 Apr 2025 12:04:09 GMT

Sorry @Surya_Tiwari but my answer seems to have been deleted.
Anyway, yes I've already tried to disable it from the LogginSubsystem but it still logging.

Which logs do you need? Because the Application Logs are just full of tracing (no sense tracing for me imho)

Re: Stack Tracing still active after disabling

VladimirRosu — Mon, 28 Apr 2025 12:36:21 GMT

Hi @AlessandroN

1. Is the ThingWorx instance having a normal CPU usage?

2. As @Surya_Tiwari asked, it would be good to share the specific log lines, as you mentioned that you see a lot of logs related to the Stack Tracing feature and we're unclear what exactly is the message (for example I never say in the Application Log a message that complained to the "Stack Tracing" feature itself, but I saw some message that contain the stack traces themselves, as below.)

3. Are those stack traces something that belong to ThingWorx features, or do they belong to a third party extension ? (I'm saying this because in a third party extension you could just decide to put the whole stack trace in the Application Log.)

Re: Stack Tracing still active after disabling

AlessandroN — Mon, 28 Apr 2025 12:53:07 GMT

Hi Vladimir,

1. yes the TWX Server has a normal CPU usage (<25%), but it is slown down when you try to see Twx Monitor Logs.
2. An example of log its attached to this message.
3. I can't answer to this question, because from the stack trace I can't understand the entity/entities related to the issue.

Re: Stack Tracing still active after disabling

VladimirRosu — Mon, 28 Apr 2025 13:05:22 GMT

Ah, that's not a Stack Trace feature issue. Instead your ApplicationLog is configured to a level way below WARN.

Check this - WARN is what you need:

Re: Stack Tracing still active after disabling

AlessandroN — Mon, 28 Apr 2025 13:25:27 GMT

Ok but this is just for the visualization table, the logging system still log files of 100MB every 4 minutes actually!

Re: Stack Tracing still active after disabling

VladimirRosu — Mon, 28 Apr 2025 13:33:14 GMT

Incorrect

That setting applies for the log writing activity, it does not affect only the UI.

With WARN active, the application log should not increase dramatically. However. please check that the same is valid for the other logs as well.

I'm curious to hear the outcome.

Re: Stack Tracing still active after disabling

AlessandroN — Mon, 28 Apr 2025 13:42:50 GMT

Seems that the stack tracing stopped when I set the config on "WARNING" (as you suggested).
I tried to set it on "ERROR" to have the minimum log, but it keeps logging all the Warnings and Infos anyway.

Re: Stack Tracing still active after disabling

VladimirRosu — Mon, 28 Apr 2025 19:13:16 GMT

OK, then there's more than just setting the correct log level (which someone set accidentally before this it looks).

There are three things I want to write/ask:

If ERROR is set, I do not know why it reports WARNs
Can you share an example of INFO ? I only see WARN
The important part is the error message itself - can you click on a single one of them to see the real message, and not just the header?