Hey everyone,

Running into an issue where, when I run a process from an action button in PAW 2.0.96 (and other earlier versions), a notification pops up that the process was aborted after 10 seconds, but there are no error logs and the process runs fine.

Funny thing is, if i have another browser window open on the Admin pane, auto-refreshing the server thread monitor every few seconds, or if I have a cube view on the PAW tab where the action button is and set it to refresh every 5 seconds or so, then the process runs fine and notifies, after the ~30 seconds it takes, that it has run fine.

Is there some esoteric timeout setting I am just not configuring that needs to be configured that is responsible for this? Seems like there is an issue with PAW just NOT keeping the connection with TM1 open, or perhaps more likely the browser not keeping the connection with PAW open, for anything longer than 10 seconds in this instance.

Thanks,

Hey everyone,

Running into an issue where, when I run a process from an action button in PAW 2.0.96 (and other earlier versions), a notification pops up that the process was aborted after 10 seconds, but there are no error logs and the process runs fine.

Funny thing is, if i have another browser window open on the Admin pane, auto-refreshing the server thread monitor every few seconds, or if I have a cube view on the PAW tab where the action button is and set it to refresh every 5 seconds or so, then the process runs fine and notifies, after the ~30 seconds it takes, that it has run fine.

Is there some esoteric timeout setting I am just not configuring that needs to be configured that is responsible for this? Seems like there is an issue with PAW just NOT keeping the connection with TM1 open, or perhaps more likely the browser not keeping the connection with PAW open, for anything longer than 10 seconds in this instance.

Thanks,

Hi Tom,

The action button in PAW make async REST API calls to TM1, so unless there is a very low timeout set (e.g 10 seconds) this should not happen.  Note that the PAW cube viewer and most other interfaces in PAW also make async API calls to TM1 as well.

I might suspect there is some network infrastructure (software or hardware) between PAW and TM1 that is closing the connection.

Also, just to clarify, this is a PAW action button on a PAW book?  Not a Websheet button on a Websheet in a PAW book?

Hey everyone,

Running into an issue where, when I run a process from an action button in PAW 2.0.96 (and other earlier versions), a notification pops up that the process was aborted after 10 seconds, but there are no error logs and the process runs fine.

Funny thing is, if i have another browser window open on the Admin pane, auto-refreshing the server thread monitor every few seconds, or if I have a cube view on the PAW tab where the action button is and set it to refresh every 5 seconds or so, then the process runs fine and notifies, after the ~30 seconds it takes, that it has run fine.

Is there some esoteric timeout setting I am just not configuring that needs to be configured that is responsible for this? Seems like there is an issue with PAW just NOT keeping the connection with TM1 open, or perhaps more likely the browser not keeping the connection with PAW open, for anything longer than 10 seconds in this instance.

Thanks,

Hi Stuart,

The environment is an Azure VM which is hosting PAW, TM1 and Cognos Analytics.

ProxyTimeoutSeconds is set to 900.

This is a PAW workbook with a PAW action button, no websheets involved.

Thanks,

Tom

Hi Tom,

The action button in PAW make async REST API calls to TM1, so unless there is a very low timeout set (e.g 10 seconds) this should not happen.  Note that the PAW cube viewer and most other interfaces in PAW also make async API calls to TM1 as well.

I might suspect there is some network infrastructure (software or hardware) between PAW and TM1 that is closing the connection.

Also, just to clarify, this is a PAW action button on a PAW book?  Not a Websheet button on a Websheet in a PAW book?

Hey everyone,

Running into an issue where, when I run a process from an action button in PAW 2.0.96 (and other earlier versions), a notification pops up that the process was aborted after 10 seconds, but there are no error logs and the process runs fine.

Funny thing is, if i have another browser window open on the Admin pane, auto-refreshing the server thread monitor every few seconds, or if I have a cube view on the PAW tab where the action button is and set it to refresh every 5 seconds or so, then the process runs fine and notifies, after the ~30 seconds it takes, that it has run fine.

Is there some esoteric timeout setting I am just not configuring that needs to be configured that is responsible for this? Seems like there is an issue with PAW just NOT keeping the connection with TM1 open, or perhaps more likely the browser not keeping the connection with PAW open, for anything longer than 10 seconds in this instance.

Thanks,

Hi Tom,

Is the Azure VM Windows server 2016? Were you using Chrome/Edge? Does Firefox help?

It could be caused by http2 issue between Chromium based browsers and the library PAW uses on Windows server. Try Chrome with http2 disabled(https://my.f5.com/manage/s/article/K000092500).

Http2 can be disabled from PAW local if it's confirmed to be the cause. 

Hi Stuart,

The environment is an Azure VM which is hosting PAW, TM1 and Cognos Analytics.

ProxyTimeoutSeconds is set to 900.

This is a PAW workbook with a PAW action button, no websheets involved.

Thanks,

Tom

Hi Tom,

The action button in PAW make async REST API calls to TM1, so unless there is a very low timeout set (e.g 10 seconds) this should not happen.  Note that the PAW cube viewer and most other interfaces in PAW also make async API calls to TM1 as well.

I might suspect there is some network infrastructure (software or hardware) between PAW and TM1 that is closing the connection.

Also, just to clarify, this is a PAW action button on a PAW book?  Not a Websheet button on a Websheet in a PAW book?

Hey everyone,

Running into an issue where, when I run a process from an action button in PAW 2.0.96 (and other earlier versions), a notification pops up that the process was aborted after 10 seconds, but there are no error logs and the process runs fine.

Funny thing is, if i have another browser window open on the Admin pane, auto-refreshing the server thread monitor every few seconds, or if I have a cube view on the PAW tab where the action button is and set it to refresh every 5 seconds or so, then the process runs fine and notifies, after the ~30 seconds it takes, that it has run fine.

Is there some esoteric timeout setting I am just not configuring that needs to be configured that is responsible for this? Seems like there is an issue with PAW just NOT keeping the connection with TM1 open, or perhaps more likely the browser not keeping the connection with PAW open, for anything longer than 10 seconds in this instance.

Thanks,

Hi Larry,

It's Windows Server 2022 in this instance but I also have a separate environment where the same thing happens on Windows Server 2019 (same timeout settings in PAW).

It happens in Chrome and Edge. I had run into this issue in a previous build and Firefox did not have the same issue. Cannot test it in this particular instance because Firefox doesn't like the GoDaddy SSL certificate that the client's IT department provided.

I'll check out the link provided and let you know if it resolves the issue or not.

Thanks,

Tom

Hi Tom,

Is the Azure VM Windows server 2016? Were you using Chrome/Edge? Does Firefox help?

It could be caused by http2 issue between Chromium based browsers and the library PAW uses on Windows server. Try Chrome with http2 disabled(https://my.f5.com/manage/s/article/K000092500).

Http2 can be disabled from PAW local if it's confirmed to be the cause. 

Hi Stuart,

The environment is an Azure VM which is hosting PAW, TM1 and Cognos Analytics.

ProxyTimeoutSeconds is set to 900.

This is a PAW workbook with a PAW action button, no websheets involved.

Thanks,

Tom

Hi Tom,

The action button in PAW make async REST API calls to TM1, so unless there is a very low timeout set (e.g 10 seconds) this should not happen.  Note that the PAW cube viewer and most other interfaces in PAW also make async API calls to TM1 as well.

I might suspect there is some network infrastructure (software or hardware) between PAW and TM1 that is closing the connection.

Also, just to clarify, this is a PAW action button on a PAW book?  Not a Websheet button on a Websheet in a PAW book?

Hey everyone,

Running into an issue where, when I run a process from an action button in PAW 2.0.96 (and other earlier versions), a notification pops up that the process was aborted after 10 seconds, but there are no error logs and the process runs fine.

Funny thing is, if i have another browser window open on the Admin pane, auto-refreshing the server thread monitor every few seconds, or if I have a cube view on the PAW tab where the action button is and set it to refresh every 5 seconds or so, then the process runs fine and notifies, after the ~30 seconds it takes, that it has run fine.

Is there some esoteric timeout setting I am just not configuring that needs to be configured that is responsible for this? Seems like there is an issue with PAW just NOT keeping the connection with TM1 open, or perhaps more likely the browser not keeping the connection with PAW open, for anything longer than 10 seconds in this instance.

Thanks,

Hi Tom,

Is the Azure VM Windows server 2016? Were you using Chrome/Edge? Does Firefox help?

It could be caused by http2 issue between Chromium based browsers and the library PAW uses on Windows server. Try Chrome with http2 disabled(https://my.f5.com/manage/s/article/K000092500).

Http2 can be disabled from PAW local if it's confirmed to be the cause. 

Hi Stuart,

The environment is an Azure VM which is hosting PAW, TM1 and Cognos Analytics.

ProxyTimeoutSeconds is set to 900.

This is a PAW workbook with a PAW action button, no websheets involved.

Thanks,

Tom

Hi Tom,

The action button in PAW make async REST API calls to TM1, so unless there is a very low timeout set (e.g 10 seconds) this should not happen.  Note that the PAW cube viewer and most other interfaces in PAW also make async API calls to TM1 as well.

I might suspect there is some network infrastructure (software or hardware) between PAW and TM1 that is closing the connection.

Also, just to clarify, this is a PAW action button on a PAW book?  Not a Websheet button on a Websheet in a PAW book?

Hey everyone,

Running into an issue where, when I run a process from an action button in PAW 2.0.96 (and other earlier versions), a notification pops up that the process was aborted after 10 seconds, but there are no error logs and the process runs fine.

Funny thing is, if i have another browser window open on the Admin pane, auto-refreshing the server thread monitor every few seconds, or if I have a cube view on the PAW tab where the action button is and set it to refresh every 5 seconds or so, then the process runs fine and notifies, after the ~30 seconds it takes, that it has run fine.

Is there some esoteric timeout setting I am just not configuring that needs to be configured that is responsible for this? Seems like there is an issue with PAW just NOT keeping the connection with TM1 open, or perhaps more likely the browser not keeping the connection with PAW open, for anything longer than 10 seconds in this instance.

Thanks,

Hi Larry,

we seem to have the same issue, so I'm curious, how to disable http/2 for PAW local. I didn't find any clue in documentation, could you help please?

Thanks a lot

tv

Hi Tom,

Is the Azure VM Windows server 2016? Were you using Chrome/Edge? Does Firefox help?

It could be caused by http2 issue between Chromium based browsers and the library PAW uses on Windows server. Try Chrome with http2 disabled(https://my.f5.com/manage/s/article/K000092500).

Http2 can be disabled from PAW local if it's confirmed to be the cause. 

Hi Stuart,

The environment is an Azure VM which is hosting PAW, TM1 and Cognos Analytics.

ProxyTimeoutSeconds is set to 900.

This is a PAW workbook with a PAW action button, no websheets involved.

Thanks,

Tom

Hi Tom,

The action button in PAW make async REST API calls to TM1, so unless there is a very low timeout set (e.g 10 seconds) this should not happen.  Note that the PAW cube viewer and most other interfaces in PAW also make async API calls to TM1 as well.

I might suspect there is some network infrastructure (software or hardware) between PAW and TM1 that is closing the connection.

Also, just to clarify, this is a PAW action button on a PAW book?  Not a Websheet button on a Websheet in a PAW book?

Hey everyone,

Running into an issue where, when I run a process from an action button in PAW 2.0.96 (and other earlier versions), a notification pops up that the process was aborted after 10 seconds, but there are no error logs and the process runs fine.

Funny thing is, if i have another browser window open on the Admin pane, auto-refreshing the server thread monitor every few seconds, or if I have a cube view on the PAW tab where the action button is and set it to refresh every 5 seconds or so, then the process runs fine and notifies, after the ~30 seconds it takes, that it has run fine.

Is there some esoteric timeout setting I am just not configuring that needs to be configured that is responsible for this? Seems like there is an issue with PAW just NOT keeping the connection with TM1 open, or perhaps more likely the browser not keeping the connection with PAW open, for anything longer than 10 seconds in this instance.

Thanks,

Hi Tomáš,

For PAW local, it can be disabled via a PAW deployment override, with the following steps:

1 . Edit or create paw/config/paw-override.yml

2 . Contents:

version: "2.1"services:  pa-gateway:    environment:      - DisableHttp2=true

3.  Apply changes:  scripts\paw.ps1

Hi Larry,

we seem to have the same issue, so I'm curious, how to disable http/2 for PAW local. I didn't find any clue in documentation, could you help please?

Thanks a lot

tv

Hi Tom,

Is the Azure VM Windows server 2016? Were you using Chrome/Edge? Does Firefox help?

It could be caused by http2 issue between Chromium based browsers and the library PAW uses on Windows server. Try Chrome with http2 disabled(https://my.f5.com/manage/s/article/K000092500).

Http2 can be disabled from PAW local if it's confirmed to be the cause. 

Hi Stuart,

The environment is an Azure VM which is hosting PAW, TM1 and Cognos Analytics.

ProxyTimeoutSeconds is set to 900.

This is a PAW workbook with a PAW action button, no websheets involved.

Thanks,

Tom

Hi Tom,

The action button in PAW make async REST API calls to TM1, so unless there is a very low timeout set (e.g 10 seconds) this should not happen.  Note that the PAW cube viewer and most other interfaces in PAW also make async API calls to TM1 as well.

I might suspect there is some network infrastructure (software or hardware) between PAW and TM1 that is closing the connection.

Also, just to clarify, this is a PAW action button on a PAW book?  Not a Websheet button on a Websheet in a PAW book?

Hey everyone,

Running into an issue where, when I run a process from an action button in PAW 2.0.96 (and other earlier versions), a notification pops up that the process was aborted after 10 seconds, but there are no error logs and the process runs fine.

Funny thing is, if i have another browser window open on the Admin pane, auto-refreshing the server thread monitor every few seconds, or if I have a cube view on the PAW tab where the action button is and set it to refresh every 5 seconds or so, then the process runs fine and notifies, after the ~30 seconds it takes, that it has run fine.

Is there some esoteric timeout setting I am just not configuring that needs to be configured that is responsible for this? Seems like there is an issue with PAW just NOT keeping the connection with TM1 open, or perhaps more likely the browser not keeping the connection with PAW open, for anything longer than 10 seconds in this instance.

Thanks,

Hi.

We have seen this issue with a customer too - and disabling HTTP/2 "resolves" the issue.

We noticed that if we use a Chromium based browser from within Azure it will work - issue is only occurring from a client outside Azure.

(Firefox work from both outside and within Azure).

Disabling HTTP/2 is more like a workaround rather than a fix - and our customer is worried about performance.

IBM Support is not recognizing this as a defect, and suggest making a RFE.

Has anyone found a better solution to this problem?

BR,

Kasper

Hi Tomáš,

For PAW local, it can be disabled via a PAW deployment override, with the following steps:

1 . Edit or create paw/config/paw-override.yml

2 . Contents:

version: "2.1"services:  pa-gateway:    environment:      - DisableHttp2=true

3.  Apply changes:  scripts\paw.ps1

Hi Larry,

we seem to have the same issue, so I'm curious, how to disable http/2 for PAW local. I didn't find any clue in documentation, could you help please?

Thanks a lot

tv

Hi Tom,

Is the Azure VM Windows server 2016? Were you using Chrome/Edge? Does Firefox help?

It could be caused by http2 issue between Chromium based browsers and the library PAW uses on Windows server. Try Chrome with http2 disabled(https://my.f5.com/manage/s/article/K000092500).

Http2 can be disabled from PAW local if it's confirmed to be the cause. 

Hi Stuart,

The environment is an Azure VM which is hosting PAW, TM1 and Cognos Analytics.

ProxyTimeoutSeconds is set to 900.

This is a PAW workbook with a PAW action button, no websheets involved.

Thanks,

Tom

Hi Tom,

The action button in PAW make async REST API calls to TM1, so unless there is a very low timeout set (e.g 10 seconds) this should not happen.  Note that the PAW cube viewer and most other interfaces in PAW also make async API calls to TM1 as well.

I might suspect there is some network infrastructure (software or hardware) between PAW and TM1 that is closing the connection.

Also, just to clarify, this is a PAW action button on a PAW book?  Not a Websheet button on a Websheet in a PAW book?

Hey everyone,

Running into an issue where, when I run a process from an action button in PAW 2.0.96 (and other earlier versions), a notification pops up that the process was aborted after 10 seconds, but there are no error logs and the process runs fine.

Funny thing is, if i have another browser window open on the Admin pane, auto-refreshing the server thread monitor every few seconds, or if I have a cube view on the PAW tab where the action button is and set it to refresh every 5 seconds or so, then the process runs fine and notifies, after the ~30 seconds it takes, that it has run fine.

Is there some esoteric timeout setting I am just not configuring that needs to be configured that is responsible for this? Seems like there is an issue with PAW just NOT keeping the connection with TM1 open, or perhaps more likely the browser not keeping the connection with PAW open, for anything longer than 10 seconds in this instance.

Thanks,