我正在尝试从 App2 调用 App1。两者都采用 springboot 并托管在 Cloudfoundry 中。我在执行此过程时收到以下错误。
java.lang.IllegalArgumentException: URI is not absolute
但是当我从 postman 那里调用 App1 时,它工作得很好。另外,当我从 App2(来自本地机器)调用 App1(在 cloudfoundry)时,它工作正常。
public class ClassA {
private String app1URL;
public ClassA(ConfigClass config) {
this.app1URL= config.getApp1Url();
SimpleClientHttpRequestFactory requestFactory = new SimpleClientHttpRequestFactory();
this.rest = new RestTemplate(requestFactory);
this.headers = new HttpHeaders();
headers.add("Accept", "*/*");
}
public String get(long employeeId, String token) {
HttpEntity<String> requestEntity = new HttpEntity<>(headers);
String app1URL = this.app1URL + "employee?employeeid="
+ employeeId+"&access_token=" + token;
ResponseEntity<String> responseEntity = rest.exchange((app1URL),
HttpMethod.GET, requestEntity,String.class);
return responseEntity.getBody();
}
当我用实际值对 app1URL 进行硬编码时,它可以在 cloudfoundry 中工作。因此,我怀疑在 cloudfoundry 中解析 this.app1URL 时存在一些问题。 堆栈跟踪如下:
java.lang.IllegalArgumentException: URI is not absolute
at org.springframework.http.client.support.HttpAccessor.createRequest(HttpAccessor.java:85) ~[spring-web-4.3.8.RELEASE.jar!/:4.3.8.RELEASE]
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:282) ~[spring-tx-4.3.8.REL
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_152]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_152]
at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:97) ~[spring-w
at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:738) ~[spring-web
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:963) ~[spring-webmvc-4.3.8.RELEASE.jar!/:4.3.8.RELEASE]
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:970) [spring-webmvc-4.3.8.RELEASE.jar!/:4.3.8.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.3.8.RELEASE.jar!/:4.3.8.RELE
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:317) [spring-security-web-4.2.2.RELEASE.jar!/:4.2
at org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:137) [spring-security-web-4.2.2.RELEASE.jar!/:
at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99) ~[spring-tx-4.3.8.RELEASE.
at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:63) [spring-security-web-4.2.2.RELEASE.ja
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_152]
at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:116) [spring-security-web-4.2.2.RELEASE.jar!/:4.2.2.RE
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331) [spring-security-web-4.2.2.RELEASE.jar!/:4.2
at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:105) [spring-security-web-4.
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.3.8.RELEASE.jar!/:4.3.8.RELEASE]
at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:177) [spring-security-web-4.2.2.RELEASE.jar!/:4.2.2.RELEASE]
at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) [spring-web-4.3.8.RELEASE.jar!/:4.3.8.RELEASE]
at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:262) [spring-web-4.3.8.RELEASE.jar!/:4.3.8.RELEASE]
at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99) [spring-web-4.3.8.RELEASE.jar!/:4.3.8.RELEASE]
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:897) ~[spring-webmvc-4.3.8.RELEASE.jar!/:4.3.8.RELEASE]
at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846) [spring-webmvc-4.3.8.RELEASE.jar!/:4.3.8.RELEASE]
at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:114) [spring-security-web-4.2.2.RELEASE.j
临时解决方案:我必须在java代码中硬编码url才能使其工作。似乎 url 没有从 application.properties 以及 manifest.yml 文件中解析(都尝试过)
最佳答案
将 API 从一个应用程序暴露到另一个应用程序,我想您可能需要启用服务发现并注册(例如在 Eureka Server 中),因为它们将托管在 Cloud Foundry 的同一空间上。
希望以下链接对您有帮助
关于java.lang.IllegalArgumentException : URI is not absolute Error in spingboot application,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/48109049/