ProTop .net 4gl stack trace query

[jdpjamesp]

When I look at the User Inspection screen in ProTop .Net I always seem to get a message that the 4gl stack trace cannot be displayed for this user. Is this because there's some setting we don't have switched on? Any ideas?

OE 10.2A by the way.

 

[TomBascom]

You have to turn it on in PROMON.

R&D, 1, 18

Turn on for all current users
Turn on for all future users

 

[jdpjamesp]

Thanks Tom - does it have a performance hit for the users?

 

[TomBascom]

Nothing noticeable.

There are rumors of a memory leak in unpatched 10.2 -- so I don't generally just turn it on for everyone and leave it on.

 

[jdpjamesp]

Ah that's worth knowing. I shall just use it when we need it!!

 

[TomBascom]

I think that it takes a few days to become a problem -- so it isn't urgent that you avoid it. You just don't want to leave it on always and forever.

 

[jdpjamesp]

Thanks Tom - the db actually crashed 30 minutes after I enabled it although I don't think it was my doing, but it did have me scared!!

 

[Rob Fitzpatrick]

Is there something in particular you're trying to troubleshoot with the stack traces, like a program that is consistently crashing or hanging?

 

[jdpjamesp]

Not really. We just have some shockingly bad code around. Users often find themselves inside mammoth transactions, usually because batch processes are written with messages to screen or errors that aren't trapped properly. We also have code that uses really bad indexing. I regularly keep track of how the db is doing and from time to time see a user with a huge number of reads on a table. My plan is to be able to pin-point exactly where these reads are coming from as we have quite a lot of dynamic queries that obviously don't show indexes in xrefs. All a mess really.