Navigation

    SmartAPI Forum
    • Register
    • Login
    • Search
    • Categories
    • Popular
    • Groups
    • FAQs
    • API Docs
    1. Home
    2. ckatangelapi
    3. Posts
    C
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Posts made by ckatangelapi

    • RE: Is Anybody is getting Live Datafeed using Websocket 2.0?

      @anil_patel ,
      Same issue for me.

      posted in General Discussion
      C
      ckatangelapi
    • WebSocket 2.0 Streaming is not sending live price and concerns on the Angel API support team

      @admin ,@administrators
      WebSocket 2.0 Streaming is not sending live price ticks, please resolve asap.

      I have few queries

      1. Is your IT team is doing proper release plan ? if yes, when will be the official release for "WebSocket 2.0 Streaming API"
      2. For any API/ ticker issues like this who will resolve this quickly? is there any support team ?, if yes give contact details , in case no how to trust on your API?
      3. I was using previous websocket connection ( not WebSocket 2.0 Streaming ) , I was running few algos and suddenly few months back it stopped working because of your url/api changes, now how algo traders would come to know about your changes here I was struggling to resolve thinking that there was some issue with my code.

      **Concerns and how to trust angel API in future ?

      1. Your IT team has no proper process.
      2. No proper release plans for enhancements.
      3. No quick support.
      4. No notifications for any code releases/enhancements.**

      Give your comments on above queries.

      posted in General Discussion
      C
      ckatangelapi
    • {"data":null,"message":"Something Went Wrong, Please Try After Sometime","errorcode":"AB1004","status":false}JSONObject["data"] is not a JSONObject.

      Hi Admin, Need help on below issue

      {"data":null,"message":"Something Went Wrong, Please Try After Sometime","errorcode":"AB1004","status":false}JSONObject["data"] is not a JSONObject.

      posted in NodeJS SDK
      C
      ckatangelapi
    • RE: Facing below hand shake issues daily 4 to 5 times in market timings

      Hi @c_harish , Yes I faced , daily I used to capture ticker data for backtesting and today it was many times (10+ times) I faced, finally stopped my server.

      posted in NodeJS SDK
      C
      ckatangelapi
    • RE: Facing below hand shake issues daily 4 to 5 times in market timings

      HI @admin , Today also I faced these issues around 7 to 8 times between 09:15 to 11:35, Fix these issues as early as possible.

      posted in NodeJS SDK
      C
      ckatangelapi
    • RE: Facing below hand shake issues daily 4 to 5 times in market timings

      Hi @admin , Any update on above issues.

      posted in NodeJS SDK
      C
      ckatangelapi
    • RE: Facing below hand shake issues daily 4 to 5 times in market timings

      @ckatangelapi

      Issue 3:

      com.neovisionaries.ws.client.OpeningHandshakeException: The status code of the opening handshake response is not '101 Switching Protocols'. The status line is: HTTP/1.1 503 Service Unavailable
      at com.neovisionaries.ws.client.HandshakeReader.validateStatusLine(HandshakeReader.java:232)
      at com.neovisionaries.ws.client.HandshakeReader.readHandshake(HandshakeReader.java:54)
      at com.neovisionaries.ws.client.WebSocket.readHandshake(WebSocket.java:3440)
      at com.neovisionaries.ws.client.WebSocket.shakeHands(WebSocket.java:3319)
      at com.neovisionaries.ws.client.WebSocket.connect(WebSocket.java:2354)
      at com.angelbroking.smartapi.ticker.SmartAPITicker.connect(SmartAPITicker.java:288)
      at com.angelbroking.smartapi.ticker.SmartAPITicker$1.onDisconnected(SmartAPITicker.java:188)
      at com.neovisionaries.ws.client.ListenerManager.callOnDisconnected(ListenerManager.java:224)
      at com.neovisionaries.ws.client.WebSocket.finish(WebSocket.java:3758)
      at com.neovisionaries.ws.client.WebSocket.onThreadsFinished(WebSocket.java:3724)
      at com.neovisionaries.ws.client.WebSocket.onReadingThreadFinished(WebSocket.java:3691)
      at com.neovisionaries.ws.client.ReadingThread.notifyFinished(ReadingThread.java:1138)
      at com.neovisionaries.ws.client.ReadingThread.runMain(ReadingThread.java:80)
      at com.neovisionaries.ws.client.WebSocketThread.run(WebSocketThread.java:45)

      Queries/Concerns:

      1. If these issues start occurring daily how we need to run our Alogs/backtest with live market.
      2. Whether this smart api code is tested properly in your dev/qa environments for handling multiple clients/connections.
      3. Because of these issues I am missing some important entries and exits.
      posted in NodeJS SDK
      C
      ckatangelapi
    • Facing below hand shake issues daily 4 to 5 times in market timings

      Hi Team, Bellow issues I am facing daily around 4 to 5 times in market timings , these issues have become blocker for me to continue , let me know whether I need to take any latest piece of code

      Issue 1:
      com.neovisionaries.ws.client.WebSocketException: Failed to send an opening handshake request to the server: Remote host closed connection during handshake
      at com.neovisionaries.ws.client.WebSocket.writeHandshake(WebSocket.java:3430)
      at com.neovisionaries.ws.client.WebSocket.shakeHands(WebSocket.java:3316)
      at com.neovisionaries.ws.client.WebSocket.connect(WebSocket.java:2354)
      at com.angelbroking.smartapi.ticker.SmartAPITicker.connect(SmartAPITicker.java:288)
      at com.angelbroking.smartapi.ticker.SmartAPITicker$1.onDisconnected(SmartAPITicker.java:188)
      at com.neovisionaries.ws.client.ListenerManager.callOnDisconnected(ListenerManager.java:224)
      at com.neovisionaries.ws.client.WebSocket.finish(WebSocket.java:3758)
      at com.neovisionaries.ws.client.WebSocket.onThreadsFinished(WebSocket.java:3724)
      at com.neovisionaries.ws.client.WebSocket.onWritingThreadFinished(WebSocket.java:3713)
      at com.neovisionaries.ws.client.WritingThread.notifyFinished(WritingThread.java:539)
      at com.neovisionaries.ws.client.WritingThread.runMain(WritingThread.java:78)
      at com.neovisionaries.ws.client.WebSocketThread.run(WebSocketThread.java:45)
      Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
      at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1009)
      at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1388)
      at sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:765)
      at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:123)
      at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
      at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
      at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:141)
      at com.neovisionaries.ws.client.WebSocket.writeHandshake(WebSocket.java:3423)
      ... 11 more
      Caused by: java.io.EOFException: SSL peer shut down incorrectly
      at sun.security.ssl.InputRecord.read(InputRecord.java:505)
      at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:990)
      ... 18 more

      Issue 2:
      com.neovisionaries.ws.client.WebSocketException: The status line of the opening handshake response is badly formatted. The status line is: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
      at com.neovisionaries.ws.client.HandshakeReader.readStatusLine(HandshakeReader.java:112)
      at com.neovisionaries.ws.client.HandshakeReader.readHandshake(HandshakeReader.java:48)
      at com.neovisionaries.ws.client.WebSocket.readHandshake(WebSocket.java:3440)
      at com.neovisionaries.ws.client.WebSocket.shakeHands(WebSocket.java:3319)
      at com.neovisionaries.ws.client.WebSocket.connect(WebSocket.java:2354)
      at com.angelbroking.smartapi.ticker.SmartAPITicker.connect(SmartAPITicker.java:288)
      at com.trading.angel.TestAngelWebSocketApi.tickerUsage(TestAngelWebSocketApi.java:201)
      at com.trading.angel.TestAngelWebSocketApi.main(TestAngelWebSocketApi.java:84)

      posted in NodeJS SDK
      C
      ckatangelapi