topic Re: Run a soap service on remote runtime in Talend Studio

Run a soap service on remote runtime

Anonymous — Tue, 06 Aug 2019 17:25:29 GMT

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.

Re: Run a soap service on remote runtime

Anonymous — Tue, 06 Aug 2019 17:35:46 GMT

It seems to suggest that there is a Java error. Can you click on the "code" tab in the bottom left of the screen and take a look for any Java errors (red blocks on the right side of the page).

Re: Run a soap service on remote runtime

Anonymous — Tue, 06 Aug 2019 17:39:27 GMT

There isn't java errors, the job works fine on local run, but don't in remote execution.

Re: Run a soap service on remote runtime

Anonymous — Tue, 06 Aug 2019 22:23:08 GMT

OK, I had to check it wasn't a Java error given the message.

The next thing to check is how your remote engine has been configured in your Studio. I can't help but notice that it says your runtime is a JobServer. JobServers do not run services, but will run normal jobs...which is consistent with your experiences. Can you open your Preferences, go to Talend--> Run/Debug and show us each of the links within there.

Re: Run a soap service on remote runtime

Anonymous — Wed, 07 Aug 2019 10:19:33 GMT

Hi,

here the exec debug parameters

Re: Run a soap service on remote runtime

Anonymous — Wed, 07 Aug 2019 10:39:19 GMT

OK, there are two ways you can solve this. Either use the ESB Runtime option (tick the box in the top left to use a local runtime) or compile your service and place it manually in the "deploy" folder of a remote runtime. What you were trying to do is run a service using a mechanism intended for jobs.

This can be confusing, but you need to look out for "Job Server" and "Runtime". Even though a "Runtime" can run jobs, services and routes, a Job Server can only run jobs.

Re: Run a soap service on remote runtime

Anonymous — Wed, 07 Aug 2019 10:50:12 GMT

Ok @rhall, i will follow your advic and try to find a solution.

Re: Run a soap service on remote runtime

Anonymous — Wed, 07 Aug 2019 15:52:29 GMT

@rhall ,

i delete my workspace and the whole talend infrastructure (TAC, Runtime Server and Job Server). Note tjhat in this case i use only tac and runtime server.

When i run the job on local, it works fine. But when i run it on my Remote RunTime sever, below is what i get :

Exécution en erreur :java.lang.Exception: Job was not built successfully, please check the logs for more details available on C:/talend/workspace/esb/.repositories/1258769164/branches/develop/MW_TRAINGIN/poms/jobs/process/ESB/test_0.1/lastGenerated.log
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:3.0.0:single (default) on project Test-bundle: Failed to create assembly: Error creating assembly archive jar-with-dependencies: Manifest not found: C:\talend\workspace\esb\.repositories\1258769164\branches\develop\MW_TRAINGIN\poms\jobs\process\ESB\test_0.1\src\main\bundle-resources\META-INF\MANIFEST.MF (Le chemin d’accès spécifié est introuvable) -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

[Job was not built successfully, please check the logs for more details available on C:/talend/workspace/esb/.repositories/1258769164/branches/develop/MW_TRAINGIN/poms/jobs/process/ESB/test_0.1/lastGenerated.log
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:3.0.0:single (default) on project Test-bundle: Failed to create assembly: Error creating assembly archive jar-with-dependencies: Manifest not found: C:\talend\workspace\esb\.repositories\1258769164\branches\develop\MW_TRAINGIN\poms\jobs\process\ESB\test_0.1\src\main\bundle-resources\META-INF\MANIFEST.MF (Le chemin d’accès spécifié est introuvable) -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
]

Re: Run a soap service on remote runtime

Anonymous — Wed, 07 Aug 2019 16:20:45 GMT

I'm a bit confused now. Why did you delete your TAC and Runtime? This does not indicate a problem with either of those. What this is showing is that you do not have a Runtime on your development box (where your Studio is) and in order to test this in the Runtime, using the Studio, you will need that.

Alternatively you can compile the service as an "OSGI Bundle for ESB", unzip the package and copy the .kar file into the deploy folder of a runtime anywhere. The correct way of promoting services to the Runtime is to promote them to an archive repository, then use TAC to deploy and run them in the Runtime.

Re: Run a soap service on remote runtime

Anonymous — Wed, 07 Aug 2019 16:26:23 GMT

@rhall i reinstall my TAC and servers for another reason hoping it will fix this problem at the same time.

Now when i try to build the service i got this error:

java.lang.Exception: Service was not built successfully, please check the logs for more details available on C:/talend/workspace/esb/.repositories/1258769164/branches/develop/MW_TRAINGIN/poms/jobs/process/ESB/test_0.1/lastGenerated.log
	at org.talend.repository.services.ui.ServiceExportWizard.performFinish(ServiceExportWizard.java:140)

and last genereated log didn't retrieve any erros :

[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.189 s
[INFO] Finished at: 2019-08-07T15:26:09+00:00
[INFO] Final Memory: 24M/321M
[INFO] ------------------------------------------------------------------------

Re: Run a soap service on remote runtime

Anonymous — Wed, 07 Aug 2019 17:54:18 GMT

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.

Re: Run a soap service on remote runtime

Anonymous — Thu, 08 Aug 2019 10:14:35 GMT

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] ------------------------------------------------------------------------

Re: Run a soap service on remote runtime

Anonymous — Thu, 08 Aug 2019 10:47:32 GMT

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.

Re: Run a soap service on remote runtime

Anonymous — Thu, 08 Aug 2019 14:09:44 GMT

Hi @rhall ,

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

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

Re: Run a soap service on remote runtime

Anonymous — Thu, 08 Aug 2019 15:09:24 GMT

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.

Re: Run a soap service on remote runtime

Anonymous — Fri, 09 Aug 2019 12:27:43 GMT

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

Re: Run a soap service on remote runtime

Anonymous — Fri, 09 Aug 2019 12:40:51 GMT

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