DBX Error Issue

[Lavanya1612]

Hi,

We encountered a "DBX Server Error: Cannot communicate with the task server." To resolve this, I changed the Task Server port, and the error was fixed. We successfully tested this in the lower environment, as it uses OpenJDK.

In production, Oracle JDK (paid version) was installed during setup. To reduce costs for the client, we attempted to switch to OpenJDK, but we encountered the same "DBX Server Error: Cannot communicate with the task server." As a result, we reverted the changes.

Given that the documentation states OpenJDK is not compatible and that only JDK/JRE 17 or higher is supported (tested with JDK 17.0.12), would changing the Task Server port to 1025 and switching to OpenJDK potentially cause any issues in production?

[kiran_panchavat]

@Lavanya1612 

Changing the Task Server port to 1025 should not be an issue in itself, as it is above the privileged port range (<1024) and is less likely to face permission issues. Ensure that port 1025 is not being used by another service and that firewall rules allow communication on this port. Since this worked in the lower environment, there is a good chance it could work in production. However, production environments often have different security policies, firewall rules, and resource loads, which could affect stability.

Incompatibility with OpenJDK might lead to failures in JDBC connections, scheduler issues, or unstable behavior of the DB Connect app. If DB Connect fails, any dashboards, alerts, or scheduled searches that rely on database inputs might be impacted.

If cost is the main concern, consider using OpenJDK but be prepared with a rollback plan