OCI Functions: Timeout Issues When Invoking with Oracle Event Hub SDK
I'm performance testing and I'm maintaining legacy code that I tried several approaches but none seem to work. I'm experiencing timeout issues when invoking OCI Functions via the Oracle Event Hub SDK in my Java application. I'm using the version 1.0.0 of the Event Hub SDK, and my function is supposed to process messages from a Kafka topic. The function is set to have a timeout of 30 seconds, but I'm seeing timeouts occurring after 10 seconds on some invocations, despite the operations inside the function completing in under 5 seconds. Here's a simplified version of my function: ```java import com.oracle.bmc.functions.model.Function; import com.oracle.bmc.functions.Functions; public class MyFunction { public String handleRequest(String input) { // Simulate some processing try { Thread.sleep(4000); // Simulating a 4s processing time } catch (InterruptedException e) { e.printStackTrace(); } return "Processed: " + input; } } ``` In my Event Hub configuration, I have also set the event processor to have a max poll interval of 5 seconds. The relevant properties are set up in the `application.properties` like this: ```properties spring.cloud.stream.kafka.binder.brokers=<broker-list> spring.cloud.stream.kafka.bindings.input.consumer.autoCommitOffset=false spring.cloud.stream.kafka.bindings.input.consumer.maxPollIntervalMs=5000 ``` Despite these configurations, the messages are still timing out. I've tried increasing the `maxPollIntervalMs` to 10000 but saw no improvement. Additionally, I've verified that the OCI Function timeout settings are correctly set to 30 seconds in the console, but it seems the invocations are still being treated like they have a shorter timeout. Has anyone encountered similar issues with OCI Functions and Event Hubs? What could be causing these premature timeouts, and how can I debug or resolve this? Any insight would be greatly appreciated! This is my first time working with Java stable. Thanks for your help in advance! This issue appeared after updating to Java 3.10.