rcenvironment / rce

Distributed, workflow-driven integration environment
https://rcenvironment.de/
51 stars 16 forks source link

Failed to connect to network connection #59

Open StRuoff opened 9 months ago

StRuoff commented 9 months ago

I want to do the following: I have an RCE instance running on Machine A (Linux), where some components are published. I want to run a workflow that executes one of the components, but need to call it via console (inside a script that I have), so what I call is (for testing if everythin is set up corectly):

rce.exe -p default --headless --exec "components list -r ; stop" or rce.exe -p default --batch "components list -r

and get the following Message:

Failed to connect to "129.247.149.169:21000": Ignoring a request to connect to 129.247.149.169:21000 (activemq-tcp) as the network layer is shutting down (Connection details: activemq-tcp:129.247.149.169:21000(connectOnStartup=true, autoRetryDelayMultiplier=1.5, autoRetryInitialDelay=5, autoRetryMaximumDelay=300, autoRetry=true))

If I open the console with rce.exe --headless -console and type the commands rce components list -r, everything runs as expected.

Starting a local RCE instance in advance and then connecting to it via "ssh wfadmin@localhost" could be an option, but would make it one more "manual" step, which we do not want to have in our approach.

I attached the corresponding log file: debug.log

StRuoff commented 9 months ago

Some additional Info: If I run a workflow (Input, 2 custom components (both remote), Output),via rce -p default --batch "wf run -p placeholder_file workflow_file" it works just fine.

ArneBachmannDLR commented 9 months ago

We do it similarly in our automatic RCE test and deployment service via "{rce}" --profile "{profile}" --batch "wf run --delete never -p {phvf} {workflow}" -data "{workspace}"