Run a soap service on remote runtime

[Anonymous]

Hello All,

I'm trying to run a ESB SOAP service from my development computer to a remote runtime like this :

and here the result i get on the console : 

Exécution en erreur :java.lang.Exception: Job was not built successfully, please check the logs for more details available on C:/talend/workspace/mw/.repositories/1258769164/branches/develop/TIGO_MW/poms/jobs/process/ESB/test_0.1/lastGenerated.log

[Job was not built successfully, please check the logs for more details available on C:/talend/workspace/mw/.repositories/1258769164/branches/develop/TIGO_MW/poms/jobs/process/ESB/test_0.1/lastGenerated.log
]

Note that for a very simple job (tFixedFlow + tLogRow), it works fine. 

[Anonymous]

Are you still trying to run it through the Remote Job Server functionality? You need to try the "ESB Runtime" functionality. Or follow one of the other steps I gave. 

Since you have TAC you must be a subscription customer. As such, it might be easier for you to contact support. They can talk you through this or take control of a remote access session and show you.

[Anonymous]

I will try to build my service and deploy it on the talend runtime manually. 

A new issue i'm getting is below:

the content of lastGenerated.log : 

[WARNING] Disabling enhanced local repository: using legacy is strongly discouraged to ensure build reproducibility.
[INFO] Scanning for projects...
[INFO] 
[INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building MW_TRAINGIN Test-0.1.0 (0.1,Jobs) Bundle 0.1.0
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- builder-maven-plugin:7.1.1:generate (default) @ Test-bundle ---
[INFO] Skipping ci-builder
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @ Test-bundle ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 5 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.6.1:compile (default-compile) @ Test-bundle ---
[INFO] Not compiling main sources
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:testResources (default-testResources) @ Test-bundle ---
[INFO] Not copying test resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.6.1:testCompile (default-testCompile) @ Test-bundle ---
[INFO] Not compiling test sources
[INFO] 
[INFO] --- maven-surefire-plugin:2.20:test (default-test) @ Test-bundle ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-bundle-plugin:2.5.3:bundle (default-bundle) @ Test-bundle ---
[INFO] 
[INFO] --- maven-assembly-plugin:3.0.0:single (default) @ Test-bundle ---
[INFO] Reading assembly descriptor: C:\talend\workspace\esb\.repositories\1258769164\branches\develop\MW_TRAINGIN\poms\jobs\process\ESB\test_0.1/src/main/assemblies/assembly.xml
[WARNING] The following patterns were never triggered in this artifact inclusion filter:
o  'org.example.mw_traingin.job:Test'

[INFO] Building jar: C:\talend\workspace\esb\.repositories\1258769164\branches\develop\MW_TRAINGIN\poms\jobs\process\ESB\test_0.1\target\Test-bundle-0.1.0.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6.786 s
[INFO] Finished at: 2019-08-08T08:37:44+00:00
[INFO] Final Memory: 24M/328M
[INFO] ------------------------------------------------------------------------

[Anonymous]

When are you getting this error? What are you doing before you get it? Have you contacted support about this? I would need to see what you are doing and be able to take a look at your environment to help out with this. Support can do this for you.

[Anonymous]

Hi @rhall ,

I contacted the support but there are not reactive at all. 

i'm getting this when trying to export my soap services :

[Anonymous]

I'm afraid I cannot recreate what you are seeing. I would need access to your system to be able to investigate any further. 

How long ago did you contact support? They are usually reasonably prompt at responding. Have you at least had an email confirmation to say that they have logged your call? If not, there may have been a problem with your request.

[Anonymous · Accepted solution]

Hi,

It's was a dumb problem. Just have to rename the name of my job so it's now different to the name of the service.

Sharing for other getting the same 

[Anonymous]

Did support solve this for you? If so, do you know whether they raised a Jira for this? By luck (certainly not judgement) I have never named my service by the same name as any of the jobs that are used to provide the service functionality. However, if this is the cause of the error, the error message should identify this as the problem. At the moment the error does not give enough information. If this was identified by support, can you ask them to raise a Jira to get this error better identified?

Thanks for returning to update the post