topic Re: Error deploying ESB route in TAC, Connection Refused in Talend Studio

Error deploying ESB route in TAC, Connection Refused

Anonymous — Sat, 16 Nov 2024 09:15:58 GMT

I'm unable to deploy a route to the runtime server from TAC after publishing the route to Nexus.

The 2 errors I'm getting from tac.log are:

java.lang.RuntimeException: Error resolving artifact ESB_TEST:TestRoute-feature:xml:0.1.0-SNAPSHOT: Could not transfer artifact ESB_TEST:TestRoute-feature:xml:0.1.0-SNAPSHOT from/to tesb.snapshot (http://admin:****@localhost:8081/nexus/content/repositories/snapshots/😞 Connect to localhost:8081 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused (Connection refused) : mvn:http://admin:****@localhost:8081/nexus/content/repositories/snapshots!ESB_TEST/TestRoute-feature/0.1.0-SNAPSHOT/xml

and

Unexpected exception : Service method 'public abstract boolean org.talend.gwtadministrator.client.module.conductor.esbconductor.service.EsbConductorService.checkIfFeatureDeployed(int) throws org.talend.gwttoolkit.client.exception.ClientBusinessException' threw an unexpected exception: org.talend.gwttoolkit.client.exception.ClientSystemException: NullPointerException

Our setup consists of 2 machines, nexus and tac are on 1 machine and runtime and jobserver are on the other.

Regular talend integration jobs deploy and run fine onto jobserver but ESB routes are unable to be deployed.

The runtime/jobserver machine shows up fine in the Server Tab of Tac, port 8000 and 8001 are green, although it says the monitoring port 8888 is misconfigured.

For the first error I wanted to try giving it the actual ip address to nexus but I can't figure out where to set that. I have no idea whats causing the 2nd error.

Any help on how to resolve would be greatly appreciated!

Re: Error deploying ESB route in TAC, Connection Refused

Anonymous — Mon, 25 Sep 2017 07:19:00 GMT

Hi,

Can you deploy your job in runtime from studio directly? Does this issue repro on all your routes or a specific one?

Best regards

Sabrina

Re: Error deploying ESB route in TAC, Connection Refused

nmodi — Fri, 06 Oct 2017 19:49:55 GMT

even I am getting kind of same error while deploying rest service onto runtime server.

publish to nexus works fine however I keep getting below error while deploying job to runtime server:

Suppressed: java.io.IOException: Error downloading mvnOC/TESTRESTSERVICE_3/0.2.0
at org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:77)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)a

To see the whole post, download it here
OriginalPost.pdf

Re: Error deploying ESB route in TAC, Connection Refused

AddyAdharsh — Wed, 01 Aug 2018 18:18:51 GMT

Hi Kelsonpdx,

1. For monitoring port issue, please try to use the FQDN (fully-qualified-domain-name) of the Execution / JobServer, while adding the server. I had a similar problem and it is resolved now - Thanks to Talend Community. Obviously, check if TAC can reach Execution / JobServer host in the port 8888 - sometimes firewall might be the culprit.

2. For your Route deployment, your Runtime is looking for the Nexus Repository in localhost (which need not be and is not in most of the cases ). For this, please go to the runtime directory or ESB container directory (depending upon your type of install), and in "etc" directory, you shall find a file called "org.ops4j.pax.url.mvn". In that file, scroll down to the last to find the Nexus configuration. Please change the hostname appropriately. =====> Kindly pay attention to which version of Nexus you are using. Right now, 7.0.1 uses Nexus v3 and older ones might use Nexus v2.

Hope these answers help you. Good luck

Cheers,

Adharsh