Gateway long time to get started

Ignition
1

Hi all,
I'm experiencing a very long time for Ignition to get started, about 6 minutes. As far as I can understand, what is slowing down the system are the DisplayPath and Priority fields of some alarms, where I have to use the lookup instruction, e.g.

lookup({[.]../Config/AlmPriorities},{name},0,'almName','prio')
in the Priority field and

concat(lookup({[~]Setup/SourcesInPos},31,'','SourceID','Pos'),lookup({[~]Setup/SourcesInPos},32,'','SourceID','Pos'),translate('MPS3 - Blocked'))
in the DisplayPath field.

(AlmPriorities and SourcesInPos are Gateway Memory tags of type dataset)

I'm on Ignition 8.1.36, but I'm quite sure that that same logic did not cause any harm some versions ago .

Any suggestion?
Thanks in advance, regards

2

What lead you to that conclusion?
Are you already working with our support department?
What exactly takes six minutes - is that the time the gateway displays in it's "the gateway started successfully" log message?

3

Hi @PGriffith and thanks for your reply.

If I set static values for those properties, the gateway starts correctly

Yes, that's it. More over if you try to start a Designer session, you cannot until the end of that 6 minutes wait.

A collegue of mine remembers that gateway starting up was running smoothly until version 8.1.33

Thanks, regards

4

Can you use jstack to take some thread dumps during the gateway startup?

5

Thanks for your suggestion! How can I use jstack? - my development environment is based on docker.

Thanks, regards

6

Hmm, not sure then. I don't think we include jstack with the embedded Java runtime either.

You'll have to restore the backup into a Gateway running in a normal environment, with a separate JDK installed so you have access to jstack.

Otherwise you can run it through support and provide them with a backup or something.

7

Thanks @Kevin.Herron I'll ask my customer if he lets me hand a project backup over to Inductive's support.