Naresh Kumar Reddy Gaddam comments

Results 4 comments of


                                            Naresh Kumar Reddy Gaddam

Dependent jar changing the default behaviour from STS

We also faced similar issue with Kinesis when running in EKS. Default credentials is not picking the `Web Identity Token from AWS STS`

Out of memory issue

Will take the heapdump, but there is no data pushed to Kinesis stream, and OOM happens after 6 to 8 hours after deploying. The Queue which is used is also...

Our heap dump points to this thread: ``` idle-connection-reaper at java.util.concurrent.ConcurrentHashMap$EntrySetView.iterator()Ljava/util/Iterator; (ConcurrentHashMap.java:4811) at software.amazon.awssdk.http.apache.internal.conn.IdleConnectionReaper$ReaperTask.run()V (IdleConnectionReaper.java:152) at java.util.concurrent.ThreadPoolExecutor.runWorker(Ljava/util/concurrent/ThreadPoolExecutor$Worker;)V (ThreadPoolExecutor.java:1128) at java.util.concurrent.ThreadPoolExecutor$Worker.run()V (ThreadPoolExecutor.java:628) at java.lang.Thread.run()V (Thread.java:829) ``` With leak suspect details: So...

Out of memory issue

Yes, we are using that