Skip to Content
avatar image
Former Member

Problem when discovering the new added HANA service

Hi all,

I got a tough problem when I use HANA SDS. The version of HANA I used is 1.00.100.00.1434512907 and the version of SDS is 1.0.100.0.000000. I install HANA DB and SDS in the same server provided by SAP MyLab service..

After I added HANA service in Data Services, when I try to discovery the service, an error shows like:

And there is also an error message in the console like:

[FAILURE:Unable to determine capabilitities of adapter type db_in][CODE:702020][EXCEPTION:Failed to read server's response: Connection refused (port 55322 to address 127.0.0.1 (localhost))]
java.lang.Exception: xmlrpc call Connection.reset() failed msg: 2015-10-16 08:03:48 DBInput_Adapter::resetConnection - Error getting connection from service


- DBInput_Adapter::resetConnection Adapter initialization failed
DBInput_Adapter::reset() Connection initialization failed
  at com.sybase.esp.cluster.plugins.servicetypes.adapter.InternalAdapter.reset(InternalAdapter.java:161)
  at com.sybase.esp.cluster.plugins.servicetypes.adapter.InternalAdapter.getTableNames(InternalAdapter.java:243)
  at com.sybase.esp.cluster.plugins.servicetypes.adapter.DiscoveryServiceImpl.getTableNames(DiscoveryServiceImpl.java:341)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:483)
  at com.sybase.esp.cluster.plugins.servicetypes.Service.execute(Service.java:112)
  at com.sybase.esp.cluster.impl.CacheService.rpcNodeExecuteService(CacheService.java:8681)
  at com.sybase.esp.cluster.impl.CacheService.rpcClusterExecuteService(CacheService.java:8525)
  at com.sybase.esp.cluster.impl.Node.clusterExecuteService(Node.java:1280)
  at com.sybase.esp.cluster.impl.ClusterServiceHandler.executeService(ClusterServiceHandler.java:250)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:483)
  at org.apache.xmlrpc.server.ReflectiveXmlRpcHandler.invoke(ReflectiveXmlRpcHandler.java:115)
  at org.apache.xmlrpc.server.ReflectiveXmlRpcHandler.execute(ReflectiveXmlRpcHandler.java:106)
  at org.apache.xmlrpc.server.XmlRpcServerWorker.execute(XmlRpcServerWorker.java:46)
  at org.apache.xmlrpc.server.XmlRpcServer.execute(XmlRpcServer.java:86)
  at org.apache.xmlrpc.server.XmlRpcStreamServer.execute(XmlRpcStreamServer.java:200)
  at org.apache.xmlrpc.webserver.XmlRpcServletServer.execute(XmlRpcServletServer.java:112)
  at org.apache.xmlrpc.webserver.XmlRpcServlet.doPost(XmlRpcServlet.java:196)
  at com.sybase.esp.cluster.impl.RpcService$NodeRpcServlet.doPost(RpcService.java:364)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
  at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:751)
  at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:566)
  at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:219)
  at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1111)
  at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:498)
  at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:183)
  at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1045)
  at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
  at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:98)
  at org.eclipse.jetty.server.Server.handle(Server.java:461)
  at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:284)
  at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:244)
  at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:534)
  at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:607)
  at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:536)
  at java.lang.Thread.run(Thread.java:812)

This troubles me a lot because I’m trying to store SDS output data to the HANA DB. Appreciate a lot if anyone can give me a hand.

Best regards,

Alex Lu

test.jpg (174.5 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Oct 26, 2015 at 03:10 PM

    Hi Alex,

    Proxy settings are configured by default on the MyLab servers. You will need to turn off proxy use for the SDS server connections. Check this document for instructions on configuring the no_proxy setting:

    Configuring a HANA ODBC Connection for Smart Data Streaming in SPS09

    Note that the instructions in that document for configuring the no_proxy setting do apply to SPS 10 as well as SPS9.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Dear Robert,

      The problem is figured out by modifying the STREAMING.sh shell script as the document shows. The little difference is that I add the HANA master node address to the $no_proxy list rather than the sub domain name.

      Thanks a lot for your kindly help! 😳

      Best regards,

      Alex Lu