【问题标题】:java.lang.IllegalArgumentException: URI is not absolute Error in spingboot applicationjava.lang.IllegalArgumentException: URI is not absolute 春季启动应用程序中的错误
【发布时间】:2018-01-05 07:28:51
【问题描述】:

我正在尝试从 App2 调用 App1。两者都在 springboot 中并托管在 Cloudfoundry 中。我在执行此过程时收到以下错误。

java.lang.IllegalArgumentException: URI 不是绝对的

但是当我从邮递员那里调用 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 文件中恢复(都试过了)

【问题讨论】:

  • 你能在 RestTemplate 中记录你请求的 URL

标签: java rest spring-boot get cloud-foundry


【解决方案1】:

将 API 从一个应用程序公开到另一个应用程序,我想您可能需要启用服务发现并注册,(如在 Eureka Server 中),因为它们将托管在同一云铸造空间。

希望下面的链接对你有帮助

Pivotal link for service registry

【讨论】:

    猜你喜欢
    • 2023-01-30
    • 1970-01-01
    • 2018-06-15
    • 2018-05-20
    • 2015-11-11
    • 2018-09-04
    • 2015-12-23
    • 2017-10-10
    相关资源
    最近更新 更多