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 have checked that an error occurs when running with agent of latest released 2.5.1-p1 version.
(If you build and use the 2.5.1-p1 tag, then you can get following error .)
java.lang.IllegalStateException: pinpoint-bootstrap-x.x.x(-SNAPSHOT)(-RCx).jar not found.
at com.navercorp.pinpoint.bootstrap.agentdir.AgentDirBaseClassPathResolver.resolve(AgentDirBaseClassPathResolver.java:73)
at com.navercorp.pinpoint.bootstrap.PinpointBootStrap.resolveAgentDir(PinpointBootStrap.java:132)
at com.navercorp.pinpoint.bootstrap.PinpointBootStrap.start(PinpointBootStrap.java:100)
It seems that the version like patch from (-p1) is not supported,
I have checked that an error occurs when running with agent of latest released 2.5.1-p1 version.
```
java.lang.IllegalStateException: pinpoint-bootstrap-x.x.x(-SNAPSHOT)(-RCx).jar not found.
at com.navercorp.pinpoint.bootstrap.agentdir.AgentDirBaseClassPathResolver.resolve(AgentDirBaseClassPathResolver.java:73)
at com.navercorp.pinpoint.bootstrap.PinpointBootStrap.resolveAgentDir(PinpointBootStrap.java:132)
at com.navercorp.pinpoint.bootstrap.PinpointBootStrap.start(PinpointBootStrap.java:100)
```
It seems that the version like patch from (-p1) is not supported, I have fixed it.
Prerequisites
Please check the FAQ, and search existing issues for similar questions before creating a new issue.YOU MAY DELETE THIS PREREQUISITES SECTION.
What version of pinpoint are you using?
tags/v2.5.1-p1
Describe the bug
I have checked that an error occurs when running with agent of latest released 2.5.1-p1 version.
(If you build and use the 2.5.1-p1 tag, then you can get following error .)
It seems that the version like patch from (-p1) is not supported,
What did you do to trigger the bug?
Expected behavior
Screenshots
Logs
Additional context
related PR : #9917
The text was updated successfully, but these errors were encountered: