[JAVA-5191] Using Java driver 4.6+ customer is getting `Failed looking up TXT record for host` Created: 05/Oct/23 Updated: 05/Oct/23 Resolved: 05/Oct/23 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Connection String |
| Affects Version/s: | 4.6.1, 4.10.2 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Minor - P4 |
| Reporter: | Janpreet Singh | Assignee: | Unassigned |
| Resolution: | Declined | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Documentation Changes Summary: | 1. What would you like to communicate to the user about this feature? |
| Description |
SummaryCustomer when attempts to establish connectivity using Java Driver 4.6 & above with their Atlas cluster using SRV connection string is getting the following error message ` Factory method 'mongo' threw exception; nested exception is com.mongodb.MongoConfigurationException: Failed looking up TXT record for host contact-policy-stage-us-pri.se6lv.mongodb.net` The issue is closely related to Details: Springboot version: 2.7.14 Java Driver: 4.6 & above MotivationWho is the affected end user?Currently the customer How does this affect the end user?They cannot use the SRV connection string to connect to their Atlas cluster. How likely is it that this problem or use case will occur?User can reproduce the error message at will. The connection works fine if we are using a non-SRV connection string If the problem does occur, what are the consequences and how severe are they?This is limited to the user environment only as of now. Is this issue urgent?A case has already been opened by the customer and they are seeking help from us. Is this ticket required by a downstream team?NA Is this ticket only for tests?Does this ticket have any functional impact, or is it just test improvements? Acceptance CriteriaWhat specific requirements must be met to consider the design phase complete? |
| Comments |
| Comment by Jeffrey Yemin [ 05/Oct/23 ] |
|
Hi there, thank you for reaching out. As this sounds like a support issue, I wanted to give you some resources to get this question answered more quickly:
Just in case you have already opened a support case and are not receiving sufficient help, please let me know and I can facilitate escalating your issue. Thank you! |