Aerospike instance behaving irregularly

Aerospike server is up and running and AQL (CLI) is working fine whereas my JAVA client is throwing SocketConnectionException randomly i.e. some queries are working fine and some are not. The Wrapper Exception is AerospikeException$Connection. Please note that I am not running Aerospike locally but it is on some other server, but i think it should not randomly throw this exception.

Can anyone tell exactly why this might be happening?

Another point, does Aerospike client throws Exception if it is unable to find the requested bin?

aql> insert into test.demo (pk, b1) values (1, 1)
    [
    [
      {
        "Status": "OK, 1 record affected."
      }
    ]
    ]

    aql> select b1 from test.demo where pk=1
    [
    [
      {
        "edigest": "N/A",
        "ttl": 431996,
        "gen": 2,
        "bins": {
          "b1": 1
        }
      }
    ]
    ]

    aql> select b2 from test.demo where pk=1
    [
    [
      {
        "edigest": "N/A",
        "ttl": 431992,
        "gen": 2
      }
    ]
    ]

I don’t see an exception when querying for a non-existent bin. BIN_NOT_FOUND error code is reserved for a future functionality. See

https://www.aerospike.com/docs/dev_reference/error_codes.html

Aerospike throws socket connection timeout exception if reading from a bin which does not exist.

The below exception is thrown when I try to use recordSet.next() after a search query. com.aerospike.client.AerospikeException$Timeout: Client timeout: timeout=100 iterations=1 failedNodes=0 failedConns=0 lastNode=BB9AB42B6565000

Details: Aerospike Query Client Version 3.12.1 C Client Version 4.1.5