These are chat archives for spring-cloud/spring-cloud
/traceresults even show that destination was set to "**:**"
2018-06-19 14:19:40.142 INFO [euler-httpclient-processor-kafka,04772d505166a729,04772d505166a729,false] 18805 --- [o-auto-1-exec-8] s.c.a.AnnotationConfigApplicationContext : Refreshing ...
destination was set to "**:**"
correction "destination": "*:**", only one asterisk
[admin@adpt3 streaming]$ curl -v --noproxy localhost -X POST http://adpt3.euler:40090/management/bus/refresh?destination=foo:** * About to connect() to adpt3.euler port 40090 (#0) * Trying 10.203.0.10... * Connected to adpt3.euler (10.203.0.10) port 40090 (#0) > POST /management/bus/refresh?destination=foo:** HTTP/1.1 > User-Agent: curl/7.29.0 > Host: adpt3.euler:40090 > Accept: */* > < HTTP/1.1 200 < X-Application-Context: euler-httpclient-processor-kafka:aggregator,euler-s3:0 < Content-Length: 0 < Date: Tue, 19 Jun 2018 06:13:22 GMT < * Connection #0 to host adpt3.euler left intact
OK I think I know what I have misunderstood.
refreshrequest is directly targeted the instance and it is refresh capable, then it refreshes regardless of destination parameter. If
refresh is received by an instance and is propagated to other instances subscribing to the Spring Cloud Bus, then the destination is checked against. (
destination is used) Am I correct?
destinationis checked by the instances received request via bus.
If you have two instance of same app each launched with different profiles('a', and 'b') and both are clients to Eureka and both are registered under a name "service", then if your FeinClient happen to pick 'a' and your destination parameter is set to a path that includes 'b' in it, then this will trigger refresh of instance 'a' regardlessly, which is no what is expected.
I think I got confused, but this is actually what is expected and correct.
sonatypeblocking the release, once it's solved it will be released at any moment @SoftwareKing
I think my RestTemplate is failing to POST the trailing request parameter,"/bus/refresh?destination=<appname>:**" thusly all of the instances subscribed to Spring Cloud Bus reacts to this requests and refresh themselves. Do I need to include it as part of url?
I think it there is some other problem I cannot identify. All I know is
destinaiton param is disregarded totally... it worked with curl command
RestTemplateto send a request to trigger the
Feign, can't you rely on
spring-cloud-config-monitorand the push notifications?
RestTemplate? Is it a manual step?
Hi all, i upgraded from spring cloud connectors 2.0.1.RELEASE to 2.0.2.RELEASE and got login failures with a oracle database.
The problem is that in 2.0.2 the password and username is URL Encoded, thus the login fails when the password/username contains special characters like for my case a bracket ']'.
The encoding is done only for Oracle.
Is there any reason why username and password are going to be url encoded for building the JDBC URL? And is there a workaround for this "issue"? Thx!