error in adduserecord with kinesalite and kpl

[vikrantch-hk]

Hi Team,

I am using kinesalite with KPL and getting below error message

com.amazonaws.services.kinesis.producer.LogInputStreamReader - [2018-04-04 18:11:54.990304] [0x00000694] [error]   [shard_map.cc:152] Shard map update for stream "sample" failed. Code:  Message: Unable to connect to endpoint;

I am using below configuration

amazon-kinesis-client 1.8.8
amazon-kinesis-producer 0.12.8

System.setProperty(SDKGlobalConfiguration.AWS_CBOR_DISABLE_SYSTEM_PROPERTY, "true");
		System.setProperty(SDKGlobalConfiguration.DISABLE_CERT_CHECKING_SYSTEM_PROPERTY, "true");
	    System.setProperty("USE_SSL", "true");
		
		KinesisProducerConfiguration config = new KinesisProducerConfiguration();
        config.setRegion(Region.getRegion(Regions.US_EAST_1).getName());
        config.setCredentialsProvider(new EnvironmentVariableCredentialsProvider());
        config.setKinesisEndpoint("192.168.70.107");
        config.setKinesisPort(4567);
        config.setLogLevel("warning");
        config.setVerifyCertificate(false);
        producer = new com.amazonaws.services.kinesis.producer.KinesisProducer(config);

I am able to put record using kinesis rest api. Please let me know what configuration I am missing.

[richard-hunt]

I'm having the same issue, using a similar configuration to try and connect to a local kinesalite instance:

    System.setProperty(SDKGlobalConfiguration.AWS_CBOR_DISABLE_SYSTEM_PROPERTY, "true");
    System.setProperty(SDKGlobalConfiguration.DISABLE_CERT_CHECKING_SYSTEM_PROPERTY, "true");

    KinesisProducerConfiguration configuration = new KinesisProducerConfiguration();
    configuration.setCredentialsProvider(new DefaultAWSCredentialsProviderChain());
    configuration.setRegion("ap-southeast-2");
    configuration.setKinesisEndpoint("localhost");
    configuration.setKinesisPort(4567);
    configuration.setVerifyCertificate(false);

    KinesisProducer producer = new KinesisProducer(configuration);

I'm getting the same 'Unable to connect to endpoint' error reported back by the native component (on Windows). Interestingly, if I revert back to KPL 0.10.2 (replacing setKinesisEndpoint() and setKinesisPort() with setCustomEndpoint() and setPort() respectively) everything works fine, so it seems something has changed from a connectivity perspective between 0.10 and 0.12.

Between this and #186 (unable to configure a proxy) it seems impossible to make use of KPL if you're forced to develop behind a corporate proxy.

[amdhing]

Not sure if I missed anything, but using KPL 0.12.5 and below should not be continued as per https://docs.aws.amazon.com/streams/latest/dev/kinesis-kpl-upgrades.html . Isn't that right?