Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Posting on Qlik Community is temporarily paused. Thank you for patience and we'll update you soon!
cancel
Showing results for 
Search instead for 
Did you mean: 
ipm_talend
Contributor
Contributor

Problem saving feature in ESB Conductor in Talend ESB

Hello,

 

When trying to add a task in ESB Conductor, I am able to select a feature, but when saving, I get following error message : ERROR TalendRemoteServiceServlet - java.lang.RuntimeException : Unable to load mvn: ...

 

More info in printscreen attached.

 

 

Labels (4)
10 Replies
Anonymous
Not applicable

I am having the same issue:

Save failed: java.lang.RuntimeException: Unable to load mvn:http://admin:****@localhost:8081/repository/releases@id=talend.release!org.example.xxx_test.service/Informatica_3_Complex_ESB-feature/0.1.0/xml/features : mvn:http://admin:****@localhost:8081/repository/releases@id=talend.release!org.example.xxx_test.service/Informatica_3_Complex_ESB-feature/0.1.0/xml/features -- For more information see your log file

 

This is with a full server install on Ubuntu 16.04 LTS. Everything is set to the defaults. I have verified the locations in org.ops4j.pax.url.mvn.cfg in the esb/container/etc directory. The URL: http://localhost:8081/repository/releases opens without errors.

ipm_talend
Contributor
Contributor
Author

You still have this issue?

 

Have you tried replacing localhost with actual hostname or ipaddress?

 

 

Eduardo5
Contributor
Contributor

Hello, 

 

I'm having exactly the same issue in a TAC 7.1.1 installation. 


I have tried with the hostname and the ip instead of localhost. 

 

In my scenario, I'm able to deploy etl jobs from Nexus (via TAC- Job conductor). However, for ESB routes from nexus (TAC - ESB Conductor) I'm getting the same error. 

 

TAC message

Save failed: java.lang.RuntimeException: URL [mvn:http://admin:****@10.128.24.32:8081/repository/dev@snapshots@id=talend.snapshot!BI_Datalake.Test/Test2-feature/0.1.0-SNAPSHOT/xml/features] could not be resolved. : mvn:http://admin:****@10.128.24.32:8081/repository/dev@snapshots@id=talend.snapshot!BI_Datalake.Test/Test2-feature/0.1.0-SNAPSHOT/xml/features -- For more information see your log file

 

LOG message

2019-02-19 07:47:47 ERROR TalendRemoteServiceServlet - java.lang.RuntimeException: URL [mvn:http://admin:****@10.128.24.32:8081/repository/dev@snapshots@id=talend.snapshot!BI_Datalake.Test/Test2-feature/0.1.0-SNAPSHOT/xml/features] could not be resolved. : mvn:http://admin:****@10.128.24.32:8081/repository/dev@snapshots@id=talend.snapshot!BI_Datalake.Test/Test2-feature/0.1.0-SNAPSHOT/xml/features
org.talend.administrator.common.exception.SystemException: java.lang.RuntimeException: URL [mvn:http://admin:****@10.128.24.32:8081/repository/dev@snapshots@id=talend.snapshot!BI_Datalake.Test/Test2-feature/0.1.0-SNAPSHOT/xml/features] could not be resolved. : mvn:http://admin:****@10.128.24.32:8081/repository/dev@snapshots@id=talend.snapshot!BI_Datalake.Test/Test2-feature/0.1.0-SNAPSHOT/xml/features

Caused by: java.lang.RuntimeException: URL [mvn:http://admin:****@10.128.24.32:8081/repository/dev@snapshots@id=talend.snapshot!BI_Datalake.Test/Test2-feature/0.1.0-SNAPSHOT/xml/features] could not be resolved. : mvn:http://admin:****@10.128.24.32:8081/repository/dev@snapshots@id=talend.snapshot!BI_Datalake.Test/Test2-feature/0.1.0-SNAPSHOT/xml/features

 

@groupproductmanagement  did you solve the issue? If yes, what did you do?

ipm_talend
Contributor
Contributor
Author

No, it is not solved yet.  we're still investigating this issue

Anonymous
Not applicable

Looking very closely at the message, I noticed that TAC wants there to be a repository object in:

org.example.job_name.service/JOB_NAME-feature/version/xml/feature

when the actual object is located at:

org.example.job_name.service/JOB_NAME-feature/version/JOB_NAME-features.xml

Could this be the problem? Is it a bug in the 7.1.1 ESB conductor?

I created an extremely simple ESB job as an additional test and it has the same issue.

Eduardo5
Contributor
Contributor

I don't think it's a TAC 7.1.1 bug because I have the following scenario:

 

I have 2 TACs (TAC1 and TAC2) deployed in different VM's but using the same nexus and the same Talend runtime (karaf)

From studio, i can publish artifacts (etl jobs and esb routes) to nexus

 

From TAC1:
- I'm able to create a task from job conductor (via nexus)and deploy an etl job in a runtime
- I'm able to create a task from esb conductor (via nexus)and deploy an esb route in a runtime

 

From TAC2
- I'm able to create a task from job conductor (via nexus)and deploy an etl job in a runtime
- I'm NOT!!! able to create a task from esb conductor (via nexus). If iI manually copy the feature in .m2/repository it works and I can deploy the artifact in Karaf

 

I put the TAC log in DEBUG. 

 



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

Hi @groupproductmanagement ,

 

Did you get any solutions to this issue?

 

I have the same issue.

 

Thank you.

Duncan2
Contributor
Contributor

I have the same issue.

 

Has anyone found a fix for this?

Eduardo5
Contributor
Contributor

Hello, 

 

Finally, I contacted Talend Support (I have an enterprise license) and they provided me with a patch that I had to install in my TAC 7.1

 

Thanks