-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to connect to vault #3
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I did a mvm install of the vault properties provider. When I test my connection with the appropriate token I get the following error
org.mule.tooling.client.api.connectivity.ConnectivityTestingObjectNotFoundException: Component resource not found
org.mule.tooling.client.api.connectivity.ConnectivityTestingObjectNotFoundException: Component resource not found
org.mule.tooling.agent.rest.client.exceptions.ToolingServiceAPIException: HTTP 404 Not Found. org.mule.tooling.agent.rest.client.exceptions.model.ErrorEntity@4039609e[errorType=class org.mule.runtime.api.exception.ObjectNotFoundException,errorMessage=It was not possible to find an object for identifier No object found with path: Vault_Properties_Provider_Config,errorDetail=org.mule.runtime.api.exception.ObjectNotFoundException: It was not possible to find an object for identifier No object found with path: Vault_Properties_Provider_Config
,additionalProperties={}]
at org.mule.tooling.agent.rest.client.exceptions.ToolingServiceAPIException.newToolingServiceAPIException(ToolingServiceAPIException.java:82)
at org.mule.tooling.agent.rest.client.exceptions.ToolingServiceAPIException.newToolingServiceAPIException(ToolingServiceAPIException.java:67)
at org.mule.tooling.agent.rest.client.tooling.applications.applicationId.components.componentId.connection.Connection.readConnectivityTestingResponse(Connection.java:76)
at org.mule.tooling.agent.rest.client.tooling.applications.applicationId.components.componentId.connection.Connection.get(Connection.java:62)
at org.mule.tooling.agent.rest.client.RestAgentToolingService.lambda$testConnectionApplication$17(RestAgentToolingService.java:431)
at org.mule.tooling.agent.rest.client.service.ServiceFunction.serviceCallWrapper(ServiceFunction.java:28)
at org.mule.tooling.agent.rest.client.RestAgentToolingService.testConnectionApplication(RestAgentToolingService.java:429)
at org.mule.tooling.client.internal.metadata.AbstractRuntimeToolingServiceDecorator.testConnectionApplication(AbstractRuntimeToolingServiceDecorator.java:116)
at org.mule.tooling.client.internal.ApplicationConnectivityTestingService.lambda$doTestConnection$0(ApplicationConnectivityTestingService.java:46)
at org.mule.tooling.client.internal.application.DefaultApplication.evaluateWithRemoteApplication(DefaultApplication.java:116)
at org.mule.tooling.client.internal.ApplicationConnectivityTestingService.doTestConnection(ApplicationConnectivityTestingService.java:45)
at org.mule.tooling.client.internal.AbstractConnectivityTestingService.testConnection(AbstractConnectivityTestingService.java:44)
at org.mule.tooling.client.internal.AbstractConnectivityTestingService.invokeMethod(AbstractConnectivityTestingService.java:57)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.mule.tooling.client.bootstrap.internal.reflection.Dispatcher$ToolingCallable.call(Dispatcher.java:241)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
The text was updated successfully, but these errors were encountered: