Creating ESB conductor fail due to unknown mvn protocol

cmarchand — Sat, 16 Nov 2024 11:53:33 GMT

Hi !
I try to deploy a route via TAC. The route has a context group associated with.
I can get the route from Artifact Repository, but when I try to select the context, I get this exception (extracted from catalina.out) :
java.net.MalformedURLException: unknown protocol: mvn
at java.net.URL.(URL.java:590)
at java.net.URL.(URL.java:480)
at java.net.URL.(URL.java:429)
at java.net.URI.toURL(URI.java:1098)
at org.apache.karaf.features.internal.FeatureValidationUtil.validate(FeatureValidationUtil.java:44)
at org.apache.karaf.features.internal.FeaturesServiceImpl.validateRepository(FeaturesServiceImpl.java:199)
at org.apache.karaf.features.internal.FeaturesServiceImpl.internalAddRepository(FeaturesServiceImpl.java:210)
at org.apache.karaf.features.internal.FeaturesServiceImpl.addRepository(FeaturesServiceImpl.java:204)
at org.talend.administrator.esbconductor.business.feature.FeaturesFileParser.load(FeaturesFileParser.java:115)
at org.talend.administrator.esbconductor.business.feature.FeaturesFileParser.(FeaturesFileParser.java:106)
at org.talend.gwtadministrator.server.esbconductor.view.EsbTaskViewAdapter.getFeatureBean(EsbTaskViewAdapter.java:390)
at org.talend.gwtadministrator.server.esbconductor.services.EsbConductorServiceImpl.getFeature(EsbConductorServiceImpl.java:80)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:561)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:208)
at org.talend.gwttoolkit.server.TalendRemoteServiceServlet.processCall(TalendRemoteServiceServlet.java:81)
at org.talend.gwtadministrator.server.LoggedAndLicenseCheckRemoteServiceServlet.processCall(LoggedAndLicenseCheckRemoteServiceServlet.java:36)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:248)
at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1001)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
Any hints or workaround ?
Best regards,
Christophe

Re: Creating ESB conductor fail due to unknown mvn protocol

Anonymous — Tue, 01 Oct 2013 22:38:33 GMT

Hello,
Can you make sure that you have the mvn library in endorsed folder under <TOMCAT_HOME>/?
Thanks,

Re: Creating ESB conductor fail due to unknown mvn protocol

cmarchand — Wed, 02 Oct 2013 09:17:19 GMT

I'm sure I do not have it !
Thanks a lot,
Christophe

Re: Creating ESB conductor fail due to unknown mvn protocol

Anonymous — Sat, 20 Apr 2019 10:28:22 GMT

I am facing same issue while creating a esb task in tac through nexus

tomcat was not having endorsed dir. I added it also contains jar(talend-url-mvn-1.0.0).

I also tried by defining environment variable but it is not working

org.talend.gwttoolkit.client.exception.ClientSystemException: unknown protocol: mvn

Thanks

Ashish

Re: Creating ESB conductor fail due to unknown mvn protocol

Anonymous — Fri, 26 Apr 2019 03:54:48 GMT

Hello @ashish_s

Here exists a related jira issue on talend bug tracker:https://jira.talendforge.org/browse/TESB-20988

It is fixed in V 7.0.1

Could you please clarify in which Tomcat you are?

Best regards

Sabrina

topic Re: Creating ESB conductor fail due to unknown mvn protocol in Talend Studio

Creating ESB conductor fail due to unknown mvn protocol

Re: Creating ESB conductor fail due to unknown mvn protocol

Re: Creating ESB conductor fail due to unknown mvn protocol

Re: Creating ESB conductor fail due to unknown mvn protocol

Re: Creating ESB conductor fail due to unknown mvn protocol