Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id DC29F200D66 for ; Fri, 15 Dec 2017 07:08:07 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id D935A160C25; Fri, 15 Dec 2017 06:08:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A948F160C16 for ; Fri, 15 Dec 2017 07:08:06 +0100 (CET) Received: (qmail 7708 invoked by uid 500); 15 Dec 2017 06:08:05 -0000 Mailing-List: contact dev-help@olingo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@olingo.apache.org Delivered-To: mailing list dev@olingo.apache.org Received: (qmail 7691 invoked by uid 99); 15 Dec 2017 06:08:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Dec 2017 06:08:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 39E1C180A23 for ; Fri, 15 Dec 2017 06:08:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id fcXJZgsZTyvQ for ; Fri, 15 Dec 2017 06:08:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 00BAB5F3E1 for ; Fri, 15 Dec 2017 06:08:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7B8D1E0635 for ; Fri, 15 Dec 2017 06:08:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 305C3212FB for ; Fri, 15 Dec 2017 06:08:00 +0000 (UTC) Date: Fri, 15 Dec 2017 06:08:00 +0000 (UTC) From: "Feby Baby (JIRA)" To: dev@olingo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (OLINGO-1216) How to consume Odata service having self-signed certificate using Olingo in java? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 15 Dec 2017 06:08:08 -0000 [ https://issues.apache.org/jira/browse/OLINGO-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feby Baby updated OLINGO-1216: ------------------------------ Description: I am trying to consume Redfish API which uses OData service in Java using Spring boot application. I understand that Olingo and Odata4j are the java libraries for consuming OData service. I tried using Olingo but getting error as the https server is having a self-signed certificate. Initially, I tried to access the redfish API using RestTemplate which worked out well. But for getting @odata.id tag information, we need to use the OData specific library. Sample json output of Redfish API: { @odata.context: "/redfish/v1/$metadata#ServiceRoot.ServiceRoot", @odata.id: "/redfish/v1", @odata.type: "#ServiceRoot.v1_0_2.ServiceRoot", AccountService: { @odata.id: "/redfish/v1/Managers/iDRAC.Embedded.1/AccountService" }, Chassis: { @odata.id: "/redfish/v1/Chassis" }, Description: "Root Service", EventService: { @odata.id: "/redfish/v1/EventService" }, Id: "RootService", JsonSchemas: { @odata.id: "/redfish/v1/JSONSchemas" }, Links: { Sessions: { @odata.id: "/redfish/v1/Sessions" } }, Managers: { @odata.id: "/redfish/v1/Managers" }, Name: "Root Service", RedfishVersion: "1.0.2", Registries: { @odata.id: "/redfish/v1/Registries" }, SessionService: { @odata.id: "/redfish/v1/SessionService" }, Systems: { @odata.id: "/redfish/v1/Systems" }, Tasks: { @odata.id: "/redfish/v1/TaskService" } } Code: ODataClient client = ODataClientFactory.getClient(); String serviceUrl = "https://IP_address/redfish/v1/Systems/"; client.getConfiguration().setHttpClientFactory(new BasicAuthHttpClientFactory("[uname]", "[pswd]")); URI absoluteUri = client.newURIBuilder(serviceUrl).build(); ODataEntitySetIteratorRequest request = client.getRetrieveRequestFactory().getEntitySetIteratorRequest(absoluteUri); // odata4 sample/server limitation not handling metadata=full request.setAccept("application/json;odata.metadata=minimal"); ODataRetrieveResponse> response = request.execute(); ClientEntitySetIterator iterator = response.getBody(); I am getting the following certificate related error while trying to consume the OData service API: bq. [Request processing failed; nested exception is org.apache.olingo.client.api.http.HttpClientException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target] with root cause bq. bq. sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target bq. at sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:141) ~[na:1.8.0_92] bq. at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:126) ~[na:1.8.0_92] bq. at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280) ~[na:1.8.0_92] bq. at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:382) ~[na:1.8.0_92] bq. at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:292) ~[na:1.8.0_92] bq. at sun.security.validator.Validator.validate(Validator.java:260) ~[na:1.8.0_92] bq. at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324) ~[na:1.8.0_92] bq. at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229) ~[na:1.8.0_92] bq. at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124) ~[na:1.8.0_92] bq. at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1491) ~[na:1.8.0_92] bq. at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216) ~[na:1.8.0_92] bq. at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979) ~[na:1.8.0_92] bq. at sun.security.ssl.Handshaker.process_record(Handshaker.java:914) ~[na:1.8.0_92] bq. at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062) ~[na:1.8.0_92] bq. at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375) ~[na:1.8.0_92] bq. at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403) ~[na:1.8.0_92] bq. at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387) ~[na:1.8.0_92] bq. at org.apache.http.conn.ssl.SSLSocketFactory.createLayeredSocket(SSLSocketFactory.java:573) ~[httpclient-4.5.3.jar:4.5.3] bq. at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:557) ~[httpclient-4.5.3.jar:4.5.3] bq. at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:414) ~[httpclient-4.5.3.jar:4.5.3] bq. at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180) ~[httpclient-4.5.3.jar:4.5.3] bq. at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:326) ~[httpclient-4.5.3.jar:4.5.3] bq. at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:610) ~[httpclient-4.5.3.jar:4.5.3] bq. at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:445) ~[httpclient-4.5.3.jar:4.5.3] bq. at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:835) ~[httpclient-4.5.3.jar:4.5.3] bq. at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) ~[httpclient-4.5.3.jar:4.5.3] bq. at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108) ~[httpclient-4.5.3.jar:4.5.3] bq. at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56) ~[httpclient-4.5.3.jar:4.5.3] bq. at org.apache.olingo.client.core.communication.request.AbstractODataRequest.doExecute(AbstractODataRequest.java:301) ~[odata-client-core-4.4.0.jar:na] bq. at org.apache.olingo.client.core.communication.request.retrieve.ODataEntitySetIteratorRequestImpl.execute(ODataEntitySetIteratorRequestImpl.java:59) ~[odata-client-core-4.4.0.jar:na] bq. at org.apache.olingo.client.core.communication.request.retrieve.ODataEntitySetIteratorRequestImpl.execute(ODataEntitySetIteratorRequestImpl.java:36) ~[odata-client-core-4.4.0.jar:na] bq. Kindly help me to resolve the issue. Please find below the links which I referred. [https://templth.wordpress.com/2015/04/27/implementing-an-odata-service-with-olingo/][1] [1]: https://templth.wordpress.com/2015/04/27/implementing-an-odata-service-with-olingo/ was: I am trying to consume Redfish API which uses OData service in Java using Spring boot application. I understand that Olingo and Odata4j are the java libraries for consuming OData service. I tried using Olingo but getting error as the https server is having a self-signed certificate. Initially, I tried to access the redfish API using RestTemplate which worked out well. But for getting @odata.id tag information, we need to use the OData specific library. Sample json output of Redfish API: { @odata.context: "/redfish/v1/$metadata#ServiceRoot.ServiceRoot", @odata.id: "/redfish/v1", @odata.type: "#ServiceRoot.v1_0_2.ServiceRoot", AccountService: { @odata.id: "/redfish/v1/Managers/iDRAC.Embedded.1/AccountService" }, Chassis: { @odata.id: "/redfish/v1/Chassis" }, Description: "Root Service", EventService: { @odata.id: "/redfish/v1/EventService" }, Id: "RootService", JsonSchemas: { @odata.id: "/redfish/v1/JSONSchemas" }, Links: { Sessions: { @odata.id: "/redfish/v1/Sessions" } }, Managers: { @odata.id: "/redfish/v1/Managers" }, Name: "Root Service", RedfishVersion: "1.0.2", Registries: { @odata.id: "/redfish/v1/Registries" }, SessionService: { @odata.id: "/redfish/v1/SessionService" }, Systems: { @odata.id: "/redfish/v1/Systems" }, Tasks: { @odata.id: "/redfish/v1/TaskService" } } Code: ODataClient client = ODataClientFactory.getClient(); String serviceUrl = "https://IP_address/redfish/v1/Systems/"; client.getConfiguration().setHttpClientFactory(new BasicAuthHttpClientFactory("[uname]", "[pswd]")); URI absoluteUri = client.newURIBuilder(serviceUrl).build(); ODataEntitySetIteratorRequest request = client.getRetrieveRequestFactory().getEntitySetIteratorRequest(absoluteUri); // odata4 sample/server limitation not handling metadata=full request.setAccept("application/json;odata.metadata=minimal"); ODataRetrieveResponse> response = request.execute(); ClientEntitySetIterator iterator = response.getBody(); I am getting the following certificate related error while trying to consume the OData service API: [Request processing failed; nested exception is org.apache.olingo.client.api.http.HttpClientException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target] with root cause sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:141) ~[na:1.8.0_92] at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:126) ~[na:1.8.0_92] at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280) ~[na:1.8.0_92] at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:382) ~[na:1.8.0_92] at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:292) ~[na:1.8.0_92] at sun.security.validator.Validator.validate(Validator.java:260) ~[na:1.8.0_92] at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324) ~[na:1.8.0_92] at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229) ~[na:1.8.0_92] at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124) ~[na:1.8.0_92] at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1491) ~[na:1.8.0_92] at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216) ~[na:1.8.0_92] at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979) ~[na:1.8.0_92] at sun.security.ssl.Handshaker.process_record(Handshaker.java:914) ~[na:1.8.0_92] at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062) ~[na:1.8.0_92] at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375) ~[na:1.8.0_92] at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403) ~[na:1.8.0_92] at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387) ~[na:1.8.0_92] at org.apache.http.conn.ssl.SSLSocketFactory.createLayeredSocket(SSLSocketFactory.java:573) ~[httpclient-4.5.3.jar:4.5.3] at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:557) ~[httpclient-4.5.3.jar:4.5.3] at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:414) ~[httpclient-4.5.3.jar:4.5.3] at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180) ~[httpclient-4.5.3.jar:4.5.3] at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:326) ~[httpclient-4.5.3.jar:4.5.3] at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:610) ~[httpclient-4.5.3.jar:4.5.3] at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:445) ~[httpclient-4.5.3.jar:4.5.3] at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:835) ~[httpclient-4.5.3.jar:4.5.3] at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) ~[httpclient-4.5.3.jar:4.5.3] at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108) ~[httpclient-4.5.3.jar:4.5.3] at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56) ~[httpclient-4.5.3.jar:4.5.3] at org.apache.olingo.client.core.communication.request.AbstractODataRequest.doExecute(AbstractODataRequest.java:301) ~[odata-client-core-4.4.0.jar:na] at org.apache.olingo.client.core.communication.request.retrieve.ODataEntitySetIteratorRequestImpl.execute(ODataEntitySetIteratorRequestImpl.java:59) ~[odata-client-core-4.4.0.jar:na] at org.apache.olingo.client.core.communication.request.retrieve.ODataEntitySetIteratorRequestImpl.execute(ODataEntitySetIteratorRequestImpl.java:36) ~[odata-client-core-4.4.0.jar:na] Kindly help me to resolve the issue. Please find below the links which I referred. [https://templth.wordpress.com/2015/04/27/implementing-an-odata-service-with-olingo/][1] [1]: https://templth.wordpress.com/2015/04/27/implementing-an-odata-service-with-olingo/ > How to consume Odata service having self-signed certificate using Olingo in java? > --------------------------------------------------------------------------------- > > Key: OLINGO-1216 > URL: https://issues.apache.org/jira/browse/OLINGO-1216 > Project: Olingo > Issue Type: Question > Components: odata4-client > Affects Versions: (Java) V4 4.4.0 > Environment: java, Spring boot > Reporter: Feby Baby > Priority: Blocker > > I am trying to consume Redfish API which uses OData service in Java using Spring boot application. > I understand that Olingo and Odata4j are the java libraries for consuming OData service. I tried using Olingo but getting error as the https server is having a self-signed certificate. Initially, I tried to access the redfish API using RestTemplate which worked out well. But for getting @odata.id tag information, we need to use the OData specific library. > Sample json output of Redfish API: > { > @odata.context: "/redfish/v1/$metadata#ServiceRoot.ServiceRoot", > @odata.id: "/redfish/v1", > @odata.type: "#ServiceRoot.v1_0_2.ServiceRoot", > AccountService: { > @odata.id: "/redfish/v1/Managers/iDRAC.Embedded.1/AccountService" > }, > Chassis: { > @odata.id: "/redfish/v1/Chassis" > }, > Description: "Root Service", > EventService: { > @odata.id: "/redfish/v1/EventService" > }, > Id: "RootService", > JsonSchemas: { > @odata.id: "/redfish/v1/JSONSchemas" > }, > Links: { > Sessions: { > @odata.id: "/redfish/v1/Sessions" > } > }, > Managers: { > @odata.id: "/redfish/v1/Managers" > }, > Name: "Root Service", > RedfishVersion: "1.0.2", > Registries: { > @odata.id: "/redfish/v1/Registries" > }, > SessionService: { > @odata.id: "/redfish/v1/SessionService" > }, > Systems: { > @odata.id: "/redfish/v1/Systems" > }, > Tasks: { > @odata.id: "/redfish/v1/TaskService" > } > } > Code: > ODataClient client = ODataClientFactory.getClient(); > String serviceUrl = "https://IP_address/redfish/v1/Systems/"; > client.getConfiguration().setHttpClientFactory(new BasicAuthHttpClientFactory("[uname]", "[pswd]")); > URI absoluteUri = client.newURIBuilder(serviceUrl).build(); > ODataEntitySetIteratorRequest request = client.getRetrieveRequestFactory().getEntitySetIteratorRequest(absoluteUri); > > // odata4 sample/server limitation not handling metadata=full > request.setAccept("application/json;odata.metadata=minimal"); > > ODataRetrieveResponse> response = request.execute(); > ClientEntitySetIterator iterator = response.getBody(); > I am getting the following certificate related error while trying to consume the OData service API: > bq. [Request processing failed; nested exception is org.apache.olingo.client.api.http.HttpClientException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target] with root cause > bq. > bq. sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target > bq. at sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:141) ~[na:1.8.0_92] > bq. at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:126) ~[na:1.8.0_92] > bq. at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280) ~[na:1.8.0_92] > bq. at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:382) ~[na:1.8.0_92] > bq. at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:292) ~[na:1.8.0_92] > bq. at sun.security.validator.Validator.validate(Validator.java:260) ~[na:1.8.0_92] > bq. at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324) ~[na:1.8.0_92] > bq. at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229) ~[na:1.8.0_92] > bq. at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124) ~[na:1.8.0_92] > bq. at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1491) ~[na:1.8.0_92] > bq. at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216) ~[na:1.8.0_92] > bq. at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979) ~[na:1.8.0_92] > bq. at sun.security.ssl.Handshaker.process_record(Handshaker.java:914) ~[na:1.8.0_92] > bq. at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062) ~[na:1.8.0_92] > bq. at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375) ~[na:1.8.0_92] > bq. at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403) ~[na:1.8.0_92] > bq. at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387) ~[na:1.8.0_92] > bq. at org.apache.http.conn.ssl.SSLSocketFactory.createLayeredSocket(SSLSocketFactory.java:573) ~[httpclient-4.5.3.jar:4.5.3] > bq. at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:557) ~[httpclient-4.5.3.jar:4.5.3] > bq. at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:414) ~[httpclient-4.5.3.jar:4.5.3] > bq. at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180) ~[httpclient-4.5.3.jar:4.5.3] > bq. at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:326) ~[httpclient-4.5.3.jar:4.5.3] > bq. at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:610) ~[httpclient-4.5.3.jar:4.5.3] > bq. at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:445) ~[httpclient-4.5.3.jar:4.5.3] > bq. at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:835) ~[httpclient-4.5.3.jar:4.5.3] > bq. at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) ~[httpclient-4.5.3.jar:4.5.3] > bq. at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108) ~[httpclient-4.5.3.jar:4.5.3] > bq. at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56) ~[httpclient-4.5.3.jar:4.5.3] > bq. at org.apache.olingo.client.core.communication.request.AbstractODataRequest.doExecute(AbstractODataRequest.java:301) ~[odata-client-core-4.4.0.jar:na] > bq. at org.apache.olingo.client.core.communication.request.retrieve.ODataEntitySetIteratorRequestImpl.execute(ODataEntitySetIteratorRequestImpl.java:59) ~[odata-client-core-4.4.0.jar:na] > bq. at org.apache.olingo.client.core.communication.request.retrieve.ODataEntitySetIteratorRequestImpl.execute(ODataEntitySetIteratorRequestImpl.java:36) ~[odata-client-core-4.4.0.jar:na] > bq. > Kindly help me to resolve the issue. > Please find below the links which I referred. > [https://templth.wordpress.com/2015/04/27/implementing-an-odata-service-with-olingo/][1] > [1]: https://templth.wordpress.com/2015/04/27/implementing-an-odata-service-with-olingo/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)