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
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 -rand get the following Message:
If I open the console with
rce.exe --headless -consoleand type the commandsrce 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