Develop Reference

Elasticsearch Client is defaulting to localhost

I am using spring.data.elasticsearch with Elasticsearch 7.14.1 in my Spring Boot (2.5.4) application.
My application.properties is something like this
spring.elasticsearch.rest.uris=elasticsearch:9200
spring.data.elasticsearch.cluster=elasticsearch:9200
spring.data.elasticsearch.repositories.enabled=true
This works fine as long as the invocation is from localhost, no issues. However, when I try to bring up my Spring Boot container, I see a failure with NoReachableHostException
reactor.core.Exceptions$ErrorCallbackNotImplemented: org.springframework.data.elasticsearch.client.NoReachableHostException: Host 'localhost:9200' not reachable. Cluster state is offline.
blah-blah-service
Caused by: org.springframework.data.elasticsearch.client.NoReachableHostException: Host **'localhost:9200'** not reachable. Cluster state is offline.
blah-blah-service
at org.springframework.data.elasticsearch.client.reactive.SingleNodeHostProvider.lambda$lookupActiveHost$3(SingleNodeHostProvider.java:101)
Clearly, my suggestion to use "elasticsearch" host (defined network, that is tested and accessible from within and outside docker containers), hasn't gone well with Spring Data for whatever reason. I have even used
#PropertySource("classpath:mysearch.properties")
in my application to try and coax these properties into the app, but doesn't look like anything works. Is there something I am missing in my Elasticsearch configuration or otherwise?
PS: I have exercised curl http://elasticsearch:9200 from within the container and find no issues

These configurations are Spring Boot specific, Spring Data Elasticsearch does not use them. But as far as I can see, you are configuring the transport client (cluster entry, should not be used anyway) and the imperative REST client, but according to the error message you are using the reactive REST client.
According to the Spring Boot documentation you would need to set spring.data.elasticsearch.client.reactive.endpoints

In the .properties file, I used the below and solved the issue for me;
spring.elasticsearch.rest.uris=http://localhost:<port_number>
spring.data.elasticsearch.client.reactive.endpoints=localhost:<port_number>

How to request https endpoints through quarkus

I am creating endpoint that is dependent on another endpoint,i have created interface and did all of that stuff but when i requested https://example.com to give me info it did not responded and request timeout exception came up.the quarkus is not supporting https request i also have added certificates kindly let me know what i am doing wrong or what i need to do.
quarkus.http.ssl.certificate.file=META-INF/dev.crt
quarkus.http.ssl.certificate.key-file=META-INF/dev.com.key
com.package.xyz/mp-rest/url=https://example.com

You need to specify some properties in your application.properties file:
quarkus.http.ssl-port=8443
quarkus.http.insecure-requests=enabled
quarkus.http.ssl.certificate.key-store-file=keystore.jks
quarkus.http.ssl.certificate.key-store-password=password
Documentation source I used for this was the Quarkus cookbook available from RedHat: https://developers.redhat.com/books/quarkus-cookbook see section 3.8

Is it possible to prevent a Spring Boot app from attempting to connect to IBM MQ?

I have a spring boot application that is connecting to an IBM MessageQueue service using the IBM Spring Boot starter:
com.ibm.mq:mq-jms-spring-boot-starter:2.1.2
I have a component class listening to the queues and it has the following annotation to enable/disable connecting to the queue:
#ConditionalOnProperty(name = "queue.enabled", havingValue = "true")
I also have the following property in my application.properties:
queue.enabled=false
This annotation worked for disabling the queue connections when I was connecting to ActiveMQ, but upon changing the codebase to connect to IBM MQ it seems that the connection is unaffected by the ConditionalOnProperty and always tries to connect.
Is there a way to enable/disable connecting to the IBM MQ service upon server startup?

The MQAutoConfiguration class that exists in the mq-jms-spring-boot-starter dependency is what is causing the attempted queue connection.
You have two options to fix this issue, one requires you to set a specific property, and the other allows you to define the property you want used to enable or disable the queue connection.
Option 1
Set the value spring.jta.enabled = false in your application.properties file.
(This may not be a preferred option if you're using transactions in your application.)
Looking at the MQAutoConfiguration class, you can see it is conditional on the property spring.jta.enabled. Setting that property to false in your application.properties file will prevent the MQAutoConfiguration class from being registered, which means no MQ beans get registered, and therefore no attempts will be made to connect to a queue.
Option 2 (if you don't want to disable JTA)
Create the package com.ibm.mq.spring.boot and create a copy of the MQAutoConfiguration class there. Modify the #ConditionalOnProperty annotation to the property of your choosing.

Just exclude configuration in your application.properties.
spring.autoconfigure.exclude=com.ibm.mq.spring.boot.MQAutoConfiguration

How To Setup Qpid with Queues using qpid-config.json

Is it possible to define what queues and topics should exist in qpid using qpid-config.json. I am using qpid 7.1.0.
How would I do this in a config file?

Qpid Broker-J has two levels of configuration, broker-wide configurations and virtual-host specific configuration. Each virtual host has its own set of queues and topics (or - more properly - exchanges), so the queue and topic definitions are in the virtual host config.
If you are just using the default configuration you get with Broker-J then it will create a virtualhost named "default" with the configuration stored as JSON in the file system (e.g. in work/default/config.json ).
Probably the best way to see how the queue and exchange configuration is stored in that file is to first create queues/exchanges through the Management UI, and then look to see what the config looks like. (Note that you shouldn't manually edit the config while Qpid is running... as it will likely overwrite it, however you can update the config while Qpid is stopped and it will pick up the changes).

Kafka spring integration authorization with sasl

I am trying to connect to kafka server via spring integration module with SASL config and get error
java.lang.IllegalArgumentException: Could not find a 'KafkaClient' entry in the JAAS configuration. System property 'java.security.auth.login.config' is not set
but when I construct simple consumer and poll messages everything works fine. Can someone tell me how to turn off JAAS authorization or connect via it properly.
Here is my KafkaConfig.java
and SaslConfiguration.java. Thanks for answer!

There is a KafkaConsumerFactory which simply can accept the same set of properties you are mentioning in you gist: https://docs.spring.io/spring-kafka/docs/2.1.10.RELEASE/reference/html/_reference.html#_receiving_messages