-
Notifications
You must be signed in to change notification settings - Fork 65
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
Problems in IDE with duplicated actuator #1177
Comments
Here the full stacktrace:
|
de-jcup
added a commit
that referenced
this issue
Apr 1, 2022
- removed version number prometheus micrometer registry in `sechub-server-core` so we have not two different registration on eclipes launches
de-jcup
added a commit
that referenced
this issue
May 25, 2022
- documentation - minor changes - added missing spdx headers
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Situation
When I start SecHub server inside my IDE (eclipse) with
And executing
JobScenario2IntTest
I got an Illegal argument exception when second batch job is executed:But when integration tests were executed by github actions via gradle the tests did NOT fail.
So gradle and eclipse IDE run do differ here!
Environment
I tested with
develop
(Spring Boot 2.6.4)
feature-1098-...
./gradlew cleanEclipse clipse
and a refresh inside eclipse IDEAlways the first test works, after the job has been created, all other tests do fail, because on server side the mentioned exception happens.
After this it's no longer possible to execute any job test from IDE without restarting the integration test server launch again.
Wanted
Shall work again in eclipse - this is big problem and slows down development.
Analyze
When?
After the first job has been processed, the problem appears on server side. Means even on first (succesful) test!
How is the server started in eclipse?
I inspected the properties of the server launch in eclipse (for commit 26e197b) ... and I found something very odd (I added some new lines here and it's not the full java command, but it shows the problem):
There are two different micrometer-prometheus jars inside the classpath:
Looking at the depdencies of
sechub-server
I found:So inside gradle the library version is updated from 1.7.2 to 1.8.3 (and so should only use 1.8.3)
But where comes the 1.7.2?
Reason found:
Solution
The problem is, that for eclipse .classpath generation the gradle eclipse plugin does use not the commonly used jar version, but the project defined one.
I am not sure if
Change
build.gradle
part to `implementation 'io.micrometer:micrometer-registry-prometheus'The text was updated successfully, but these errors were encountered: