Sudden issues with TEM console performance

Usage and Config Platform
1

(imported topic written by SystemAdmin)

All

I wanted to post on here to get feedback for a current issue my company is having (PMRs created as well).

Recently we are experciencing very poor Console performance.

  • The decrease in performance is when the console is launched (takes up to a minute or two just to get to teh ‘loading’ window.
  • Also, when the console is finally open, and a user submits an action, we are witnessing two propogation error(s) (not at same time)

Error 1- Propogation error that shows an Unhandled Exception message

Error 2- propogation error that shows a series of Fixlet IDs and states:

The Signatures on the following custom fixlets/ tasks could not be verified. You must delete or re-sign the invalidly signed fixlets/ tasks

The only thing I am aware that changed is that I removed a user from teh admin console. However this user did not own the content indentified in the error message.

So, how do you re-sign these fixlets/ tasks? Any any ideas what is going on?

2

(imported comment written by MattBoyd)

I don’t think we’ve seen these issues. Is the propagation error happening for specific users or all users? Is the console hosted on a terminal server?

After the upgrade to 8.2, the console did seem sort of sluggish for me until I cleared my console cache. Have you tried that?

3

(imported comment written by SystemAdmin)

The console is mostly on a VM cluster, and this is where we get the errors.

The consoles on local endpoints mostly are not getting errors (one is), but are showing the extreme slowness of the app.

Yeah, we have tried clearing the cache to clear the issue, but it persists. It seems like an issue with the db, and I pray it is recoverable.

Thanks for the feedback, boyd

4

(imported comment written by MattBoyd)

Hmm… how about the console on the root server itself?

5

(imported comment written by SystemAdmin)

Yes, same performance, but doesnt crash on the server.

6

(imported comment written by SystemAdmin)

We are looking down the road of memory issues as well, as the debug logs show out of memory messages. And I know that seems like the obvious answer, however this seems to have come up unexpetedly.

7

(imported comment written by SystemAdmin)

Do you guys have an extremely large number of fixlets or actions or something? Maybe an analysis that is reporting up tons of data per computer?

8

(imported comment written by SystemAdmin)

I don think I do. I’ve been working with support to try to correct this,a nd there isn’t any content that is causing alarm to those I am working with.