Nope I made it available from anywhere, you can test that url it should work........At this point I have no choice but to try to use Mysql but that driver is also not available or make api calls with AWS service with the following structure APi Gateway -> Lmabda -> DynamoDB or RDS and back.
This is a known issue where Xcode/lldb/XNU kernel work together and cause this issue. This is being worked on. However, if you hit this case, it should be EINVAL (which is 22 on macOS) and not EDEADLK 11 Resource deadlock avoided. (I'm assuming you're on macOS because you mention Xcode)
This is the same thread trying to acquire a lock again that it already holds. If you post the whole stack trace (bt in lldb, more info here), then we should be able to tell where the problem is.
You can ignore those, they're not from NIO/MongoKitten/... but from the networking system itself, that's also a known bug in the OS.