| Author |
Message
|
| mar1020mar |
 Posted: Sun Jan 27, 2019 8:47 am Post subject: IIB V10 - Error Launching Debugger for more than one EG. |
 |
|
Newbie
Joined: 27 Jan 2019
Posts: 4
|
IIB V10 server is installed on Azure. In Toolkit (Remote access) when trying to Launch the debugger for the first EG, there is no issue.
For all the other issues the following error is displayed when trying to launch the debugger.
Cannot communicate with the Flow Engine
Reason:
The flow engine has been attached to another debug session, or
The flow engine is not listening on the specified port, or
The Broker is not running, or
Timeout occurred while connecting |
|
| Back to top |
|
 |
| mar1020mar |
| Posted: Mon Jan 28, 2019 5:46 am Post subject: |
|
|
Newbie
Joined: 27 Jan 2019
Posts: 4
|
| Any one faced this issue, can you please reply? |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 28, 2019 6:42 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mar1020mar wrote: |
| Any one faced this issue, can you please reply? |
You posted on a Sunday. Many of us have some kind of life outside this forum. None of us have any kind of SLA on response times. You want urgent help, call IBM.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 28, 2019 6:44 am Post subject: Re: IIB V10 - Error Launching Debugger for more than one EG. |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mar1020mar wrote: |
| IIB V10 server is installed on Azure. In Toolkit (Remote access) when trying to Launch the debugger for the first EG, there is no issue. |
Why are you trying to debug 2 EGs simultaneously?
| mar1020mar wrote: |
| The flow engine has been attached to another debug session |
This is most likely the problem.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mar1020mar |
| Posted: Mon Jan 28, 2019 6:44 am Post subject: |
|
|
Newbie
Joined: 27 Jan 2019
Posts: 4
|
| sorry, I have re-posted to just check if someone already had faced this issue.... |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 28, 2019 6:46 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mar1020mar wrote: |
| sorry, I have re-posted to just check if someone already had faced this issue.... |
....and patience is a virtue as well as an opera.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mar1020mar |
| Posted: Mon Jan 28, 2019 4:19 pm Post subject: |
|
|
Newbie
Joined: 27 Jan 2019
Posts: 4
|
Thank you all.
The issue is resolved.
The ports used by the rest of the EG's (debugger port) were blocked by the firewall in the Azure cloud. Once, the ports were allowed from the firewall, able to launch the debugger for rest of the EG's as well. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 29, 2019 5:36 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mar1020mar wrote: |
| The ports used by the rest of the EG's (debugger port) were blocked by the firewall in the Azure cloud. Once, the ports were allowed from the firewall, able to launch the debugger for rest of the EG's as well. |
I missed the part where you said you were using Azure. My bad.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
