-
Notifications
You must be signed in to change notification settings - Fork 66
vert.x dnsresolver does not work in che #3428
Comments
seems relevant to add this flag to command if it does not have side effects. |
@cescoffier what do you guys prefer ? seems fixing it in the pom.xml would be the best/most complete option ? but if not then lets fix it in the stacks. And yes @ibuziuk it does not have any sideeffects as far as we know except actually making it work reliably ;) |
@cescoffier we are going to make rollout (hopefully last before summit) on prod tomorrow, so please let me know if we should update the command |
I would recommend disabling the async DNS resolver in Che. So yes updating the command would work and is probably the best approach. |
@cescoffier ok, lemme provide PR with command update. |
…debug commands osio issue openshiftio/openshift.io#3428
PR is sent redhat-developer/rh-che#662 |
…debug commands osio issue openshiftio/openshift.io#3428
PR for rh-che is merged - should be soon on prod-preview |
@maxandersen @cescoffier @slemeur fix is available on prod: are you ok to close ? |
Ok for me |
if you run vert.x without use of fmp on openshift - need to set Dvertx.disableDnsResolver=true to make it work on che or in any other IDE using pods.
possible fixes:
change https://github.com/redhat-developer/rh-che/blob/master/assembly/fabric8-stacks/src/main/resources/stacks.json#L476 to have this flag set
OR
change booster pom's to have it set for vertx:run
OR
change the booster to have a main to set the flag early
The text was updated successfully, but these errors were encountered: