I am trying to connect to GCP memory store from the spring boot application
Getting the following error
keeps throwing
redis.clients.jedis.exceptions.jedisConnectionException: Unexpected end of stream at redis.clients.jedis.RedisInputStream.ensureFill
Related
I have this error
Caused by: org.apache.kafka.common.KafkaException: SSL trust store is specified, but trust store password is not specified.
at org.apache.kafka.common.security.ssl.SslFactory.createTruststore(SslFactory.java:184)
at org.apache.kafka.common.security.ssl.SslFactory.configure(SslFactory.java:104)
at org.apache.kafka.common.network.SslChannelBuilder.configure(SslChannelBuilder.java:41)
Although same code is deployed in other environments work just fine.
The code is trying to work as a kafka consumer
If I query using Kafka console consumer, it fetches data properly
Getting this error Closing NIO session because of unhandled exception while starting ignite(apache-ignite-fabric-2.6.0-bin).
Trying restarting the instance and increasing the onheap and offheap memory.
we tried another version apache-ignite-fabric-2.5.0-bin got the same error.
Any suggestion or configuration i need to do to fix this issue.
[06:06:33,024][SEVERE][grid-nio-worker-client-listener-0-#40][ClientListenerProcessor] Closing NIO session because of unhandled exception.
class org.apache.ignite.IgniteCheckedException: Invalid handshake message
at org.apache.ignite.internal.processors.odbc.ClientListenerNioServerBuffer.read(ClientListenerNioServerBuffer.java:115)
at org.apache.ignite.internal.processors.odbc.ClientListenerBufferedParser.decode(ClientListenerBufferedParser.java:60)
at org.apache.ignite.internal.processors.odbc.ClientListenerBufferedParser.decode(ClientListenerBufferedParser.java:40)
at org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:114)
at org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
at org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3490)
at org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:175)
at org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:1113)
at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2339)
at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2110)
at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1764)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
I don't see why there will be activity on ODBC port when you start Apache Ignite instance. Are you sure that no applications are trying to connect to Ignite ports, send garbage to sockets when you bring Ignite up?
Maybe there's something which confuses Ignite for their buddy.
I am following this tutorial on how to send a picture taken from the pi camera to the CLoudant NoSQL database on Bluemix.
"There are 3 node-red flows in total. The Process Doorbell flow (on the raspberry pi) should send an IBM IoT visitorAlert event message to Node-RED on Bluemix which should, in turn, send an IBM IoT sendPicture command message back to Node-RED on Raspberry Pi. This will eventually create a Base64 encoded image string, package it up with the filename, length and status into a payload that gets sent to Cloudant in Bluemix by the insertPicture node. See if it worked by going to the Bluemix Cloudant dashboard."
I created the flows on node-Red, but am getting this error on the node-red in the pi:
"Error stopping node: Error: [BaseClient:disconnect] Client is not
connected"
I am getting this error on the node-red in Bluemix:
"Error: Connection refused: Not authorized"
What could be the issue?
I am trying to integrate AWS elasticache redis with spring boot application using spring-data-redis. Getting below exception when using a service.
Caused by: redis.clients.jedis.exceptions.JedisConnectionException: Could not get a resource from the pool
org.springframework.data.redis.connection.jedis.JedisConnectionFactory.fetchJedisConnector(JedisConnectionFactory.java:191)
... 84 more
Caused by: redis.clients.jedis.exceptions.JedisConnectionException: java.net.ConnectException: Connection refused
at redis.clients.jedis.Connection.connect(Connection.java:164)
Using below code
#Bean
public RedisConnectionFactory jedisConnectionFactory(JedisPoolConfig jedisPoolConfig) {
JedisConnectionFactory redisConnectionFactory = new JedisConnectionFactory(jedisPoolConfig);
redisConnectionFactory.setHostName("AWS primary replication group endpoint");
redisConnectionFactory.setPort(6379);
redisConnectionFactory.setUsePool(true);
redisConnectionFactory.setTimeout(3600);
return redisConnectionFactory;
}
I am able to connect to AWS Redis from my EC2 instance where the service is deployed. Any sample code or steps would be really helpful.
Might be late to this party but it was my experience that declaring spring.redis.host in application.yml, application.properties or at the command-line as a -D argument were not respected by RedisProperties within RedisAutoConfiguration.
What ultimately worked for me was exporting an environment variable, like so
export SPRING_REDIS_HOST=...
before starting up a service that attempts to connect to ElastiCache.
I'm GlassFish 3.1.2, ActiveMQ 5.1.1 and ActiveMQ 5.8 resource adapter (activemq-rar-5.1.1) I have created a GlassFish cluster with 2 instances. I reference http://geertschuring.wordpress.com/2012/04/20/how-to-connect-glassfish-3-to-activemq-5/ to assist with the initial deployment/configuration of activemq resource adapter After configuring the Connector Connection Pool via GlassFish Admin Console and enable Ping. When Ping is executed an error occurs: Ping Connection Pool for jms/ActiveMQConnectionFactory is Failed. Ping failed Exception - This pool is not registered with the runtime environment : jms/ActiveMQConnectionFactory Please check the server.log for more details. Ping failed Exception - This pool is not registered with the runtime environment : jms/ActiveMQConnectionFactory Please check the server.log for more details.
appreciate for your replay
by any chance is your glassfish instance in a cluster?. In our case it was failing with the same error message, and we figured out that if the instance is in a cluster, it doesn´t work. Though it works if it is not in a cluster.
We verified this also by checking in the activemq admin console the the consumers were active and receiving message, even if the ping command was failing.