-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
"No resolvable bootstrap urls given in bootstrap.servers" - Kafka #11758
Comments
I already provide all steps for problem reproduction. Is something missing? |
@vw98075 Nothing is missing. We just need time to work on that and reproduce it on our own such that we can reproduce it too (if you mean the added label). |
I tried to reproduce this issue but I could only reproduce it once (the first time).. |
I already encountered this because the Kafka broken didn't start correctly, or I started the application to quickly. |
I just encountered this. Generated via 6.10.1. It would be good for the generated application to not fail if kafka fails. Caveat: I'm new to kafka and currently understand it as a tool for inter-service communication. If that's right, it would seem strange for 1 service to fail if the separately-run communication service would be unavailable. In case it's helpful to whoever eventually figures out what's going, I'll share the {
"generator-jhipster": {
"authenticationType": "oauth2",
"cacheProvider": "ehcache",
"clientFramework": "angularX",
"serverPort": "8002",
"serviceDiscoveryType": false,
"skipUserManagement": true,
"baseName": "inventory",
"buildTool": "gradle",
"databaseType": "sql",
"devDatabaseType": "mssql",
"enableHibernateCache": true,
"enableSwaggerCodegen": true,
"enableTranslation": false,
"jhiPrefix": "jhi",
"languages": ["en", "fr"],
"messageBroker": "kafka",
"nativeLanguage": "en",
"prodDatabaseType": "mssql",
"searchEngine": "elasticsearch",
"skipClient": false,
"testFrameworks": ["protractor", "cucumber", "gatling"],
"websocket": "spring-websocket",
"applicationType": "monolith",
"packageName": "package.name",
"packageFolder": "package/folder",
"useSass": true,
"jhipsterVersion": "6.10.1",
"creationTimestamp": 1597859100648,
"skipServer": false,
"clientPackageManager": "npm",
"clientTheme": "none",
"clientThemeVariant": "",
"embeddableLaunchScript": false,
"entitySuffix": "",
"dtoSuffix": "DTO",
"otherModules": [],
"blueprints": []
},
"entities": []
}
|
@mrsegen : can you provide all steps to reproduce the issue ? And add the stacktrace too plz ? |
@pascalgrimaud , sure! Steps taken:
For the docker_[application]-app_1 container, stack trace (with pertinent preceding logs) are:
For docker_kafka_1, it's full output before exiting was:
|
I'm reopening it and will try to reproduce |
Also the docker_zookeeper_1 had this at the bottom of its output:
Though on another docker-compose attempt, after running
On an additional docker-compose attempt:
|
@mrsegen : I try to reproduce the issue, but it works well for me
|
Here the project I used: All the commands: Here all the logs: So as already said previously, I think it can happened when Zookeeper / Kafka doesn't start correctly. Just try to relaunch it and it should be OK. |
Thank you, kindly! |
✔️ I'm no longer seeking the issue. |
Ok then, so let's close this. |
One tangential point I didn't notice about the successful example / failure to reproduce... I see from your screenshot that you were able to login as the admin user. (Not the case for me one two separate attempts.) This would be a separate issue, but the next problem I was having was that clicking "Sign in" from localhost:8002 would direct the browser to (I'm sneaking a moment to check this between time with my kids...) I hope to try out your sample repo. Just mentioning now in case you may be aware of something obvious I'm missing. I'll confirm whether I need to update to latest stable of generator-jhipster. |
@mrsegen : about Keycloak, you should have a look at https://www.jhipster.tech/docker-compose/#-keycloak and don't forget to add |
That did it! Thank you! For anyone else stumbling on this with spurious errors while generating a fresh service with JHipster, the Keycloak container was failing to start via docker-compose, with an error about port 9443 being in use. After restarting Docker Desktop, it was good to go! |
@pascalgrimaud I have a (further tangential) follow up question: Where in the JHipster repositories is the 30 second default that's generated at |
The logic is here: So you're right about mssql app. It should be increase to 60 |
Overview of the issue
An error on Kafka straight from the box
Motivation for or Use Case
Generating a microservice application with Kafka
Reproduce the error
based on the Jhipster document.
The first notable error message:
and
Related issues
Suggest a Fix
JHipster Version(s)
6.8.0
JHipster configuration
Entity configuration(s)
entityName.json
files generated in the.jhipster
directoryBrowsers and Operating System
Linux Mint
The text was updated successfully, but these errors were encountered: