Visual LANSA Forum

Hi All

I'm having an issue where we are running lansa for the web, v14, on a beefy new system i when at its' busiest is idling at between 30% and 50%. So we should not be having timeout issues but that is exactly what we are experiencing. Also the network is experiencing no issues.

Most users after clicking on a submit button get a message popping up on their browser 'webpage is not responding' with a 'Recover webpage' button. If they click on the button they are kicked off the page they are working on and the message 'We are unable to return you to <url>' appears.

Are there any checks that I could run or to determine what is causing the page to time-out?

Thanks,
v

You could check the LWEB_JOB jobs to look for jobs in MSGW or the job log to see if there is something taking a long time.

Another thing you should also check is the following. Run the command STRDIGQRY HOSTNAME(localhost). If this doesn't return a response almost immediately this could be your issue. What we found is that the network team was blocking an outbound port so that this command would timeout. This will cause an issue where about every 15 minutes your pages will take minutes to respond.

You could also look in the /LANSA_XXXpgmlib/x_lansa/log/x_err.log file to see if there are any strange messages.

Is it always the same page that has the issue, just some pages or can the issue appear on any page?

Thanks for this.

Some feedback:

-Tested STRDIGQRY HOSTNAME and received immediate response back.

-There are no logs to be found in the directory, so no clues there.

-It's usually the same page because users are normally in the same application due to 80% of sessions at the time are using this application.

Also got users to run tracert when they experience sluggishness, and again, nothing untoward to report on the network there.

Have you watched the subsystem with the LWEB_JOB jobs running? Are any jobs going into a LCKW status which could cause these delays. What kinds of things does this common page do? Could there be some type of long running query or call to an API that could be causing a delay? If you can reproduce can you find the LWEB_JOB handling your request so that you can look for messages in this job to see if there are any clues while the page is waiting for a response.

Hi.

Could it be this: https://www.lansa.com/support/notes/p0461.html

/klaus