お世話になっております。
海隆一創の王です。
チケットの内容は下記となります。
Why is my Process no longer able to spy or interact with Chrome Browser?
Chrome integration works in such a way that (after a fresh reboot), once a Process is run that interacts with Chrome, a connection is made with Chrome over port 31924. Even after that Process has completed, the connection to port 31924 will still be open and is not disposed of.
When performing testing of a Process via Studio, the Process is run via the local (private) Resource. As described above, the local Resource would initially open the connection, and that local Resource would then hold on to that connection.
If you subsequently attempt to run the Process from Control Room to a Runtime Resource running locally on the same machine, as the connection had already been opened by the local Resource, a new connection cannot then be initiated, which causes a failure.
For this reason, only performing a reboot of the Resource machine will free the connection and allow the Process to run again via either Control Room or Studio.
Our expectations are that you should only encounter this issue during the testing phase of the Process. The reason for this is because you will be switching between running the Process within Studio and Control Room. We don't expect the issue to present itself within a Production environment as the Process would only ever be run from a Runtime Resource.
上記原因なら再起動後はアタッチ出来ると思います。
PC-errの場合は再起動後でもエラーになるのは、 port 31924は他のプログラムが使ったりしているかもしれません。
以下のコマンドで調べてみてください。
上段は誰も使ってない状態、下段はChromeが開いている状態です。
以上、ご参考になれば幸いです。
------------------------------
RONG WANG
IT
株式会社 海隆一創
Asia/Tokyo
------------------------------
海隆一創の王です。
チケットの内容は下記となります。
Why is my Process no longer able to spy or interact with Chrome Browser?
Chrome integration works in such a way that (after a fresh reboot), once a Process is run that interacts with Chrome, a connection is made with Chrome over port 31924. Even after that Process has completed, the connection to port 31924 will still be open and is not disposed of.
When performing testing of a Process via Studio, the Process is run via the local (private) Resource. As described above, the local Resource would initially open the connection, and that local Resource would then hold on to that connection.
If you subsequently attempt to run the Process from Control Room to a Runtime Resource running locally on the same machine, as the connection had already been opened by the local Resource, a new connection cannot then be initiated, which causes a failure.
For this reason, only performing a reboot of the Resource machine will free the connection and allow the Process to run again via either Control Room or Studio.
Our expectations are that you should only encounter this issue during the testing phase of the Process. The reason for this is because you will be switching between running the Process within Studio and Control Room. We don't expect the issue to present itself within a Production environment as the Process would only ever be run from a Runtime Resource.
上記原因なら再起動後はアタッチ出来ると思います。
PC-errの場合は再起動後でもエラーになるのは、 port 31924は他のプログラムが使ったりしているかもしれません。
以下のコマンドで調べてみてください。
上段は誰も使ってない状態、下段はChromeが開いている状態です。
以上、ご参考になれば幸いです。
------------------------------
RONG WANG
IT
株式会社 海隆一創
Asia/Tokyo
------------------------------
