You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I started to using pinpoint apm with docker compose. In this tutorial pinpoint-docker
After running the monitoring normally, there was a problem with the request operation.
The Quickstart Application provided in the guide is causing 404 errors when requesting a specific URL.
The specific URL is "/callSelf/httpclient4/getTwitterUrlCount.pinpoint".
I analyzed the files in the path through decompiles, but there seemed to be no problem with the code.
However, it seems that the Twitter API is no longer available.
HttpClient4Controller does not have mapping information defined for Twitter API.
It would be nice if you could simply provide exception response information through exception handling such as ExceptionHandler.
Or, if you write down the failure case in the API description, it seems that the user will not misunderstand.
For other url(getGeoCode), we are sending a response with details about the error through exception handling when a problem occurs.
While this is a guide project, I suggest that it's better to fix the code causing errors.
Thank you for taking the time to read the long text. I hope it was helpful.
Hello,
I started to using pinpoint apm with docker compose. In this tutorial
pinpoint-docker
After running the monitoring normally, there was a problem with the request operation.
The Quickstart Application provided in the guide is causing 404 errors when requesting a specific URL.
The specific URL is "/callSelf/httpclient4/getTwitterUrlCount.pinpoint".
Problem
pinpoint-quickstart-testapp.war
I analyzed the files in the path through decompiles, but there seemed to be no problem with the code.
However, it seems that the Twitter API is no longer available.
HttpClient4Controller does not have mapping information defined for Twitter API.
It would be nice if you could simply provide exception response information through exception handling such as ExceptionHandler.
Or, if you write down the failure case in the API description, it seems that the user will not misunderstand.
For other url(getGeoCode), we are sending a response with details about the error through exception handling when a problem occurs.
While this is a guide project, I suggest that it's better to fix the code causing errors.
Thank you for taking the time to read the long text. I hope it was helpful.
Error log
at [Source: org.apache.http.conn.EofSensorInputStream@33f9fb6; line: 1, column: 2]
com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1419)
com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:508)
com.fasterxml.jackson.core.base.ParserMinimalBase._reportUnexpectedChar(ParserMinimalBase.java:437)
com.fasterxml.jackson.core.json.UTF8StreamJsonParser._handleUnexpectedValue(UTF8StreamJsonParser.java:2363)
com.fasterxml.jackson.core.json.UTF8StreamJsonParser._nextTokenNotInObject(UTF8StreamJsonParser.java:794)
com.fasterxml.jackson.core.json.UTF8StreamJsonParser.nextToken(UTF8StreamJsonParser.java:690)
com.fasterxml.jackson.databind.ObjectMapper._initForReading(ObjectMapper.java:3105)
com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3051)
com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2207)
com.navercorp.pinpoint.testapp.service.remote.HttpRemoteService.execute(HttpRemoteService.java:95)
com.navercorp.pinpoint.testapp.service.remote.HttpRemoteService.get(HttpRemoteService.java:37)
com.navercorp.pinpoint.testapp.controller.CallSelfController.httpClient4GetTwitterUrlCount(CallSelfController.java:70)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:498)
org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:221)
org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:137)
org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:110)
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:776)
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:705)
org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959)
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893)
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:967)
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:858)
javax.servlet.http.HttpServlet.service(HttpServlet.java:489)
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:843)
javax.servlet.http.HttpServlet.service(HttpServlet.java:583)
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:85)
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
The text was updated successfully, but these errors were encountered: