SAP Knowledge Base Article - Preview

3331951 - "Error during stream receive: NetworkChannel::receiveRawImp. recv failed, rc=110: Connection timed out" where client_program=HDBStudio

Symptom

No client connectivity problems have been reported by your users, but you see the following logs in your indexserver service tracing:

[7942]{-1}[-1/-1] 2023-04-13 18:03:38.004457 e SQLSession       sm_handler.cc(01325) : (sockfd:61, part:22, channel:0x00007f2e66717e80, event:0x00007f30c90d3dc0) receive duration time=2 ms, channel error: exception  1: no.2110006  (Basis/IO/Stream/impl/NetworkChannel.cpp:2102) TID: 7942
    Error during stream receive: NetworkChannel::receiveRawImp. recv failed, rc=110: Connection timed out; $Context$=[af6680219aeefe2c,10.180.2.239:30715,10.7.236.36:62941,SES,0]; $channel$={<NetworkChannelSSLFilter>={<NetworkChannelBase>={this=139837217843224, fd=61, refCnt=1, local=<HANA IP address>/<HANA SQL port>_tcp, remote=<client IP address>/<client port>_tcp, state=Connected, pending=[----]}}}
exception throw location:
   0: 0x00007f3171d4347a in Stream::NetworkChannel::receiveRawImp(void*, unsigned long, unsigned long&)+0x286 at Basis/IO/Stream/impl/NetworkChannel.cpp:2102 (libhdbbasis.so)
   1: 0x00007f3171d386a2 in Stream::NetworkChannel::doReceive(void*, unsigned long)+0x3f0 at Basis/IO/Stream/impl/NetworkChannel.cpp:1585 (libhdbbasis.so)
   2: 0x00007f315ebcce30 in SessionLayer::TcpChannel::receive()+0x60 at api/Communication/Raw/NetworkChannelStream.hpp:109 (libhdbsessionlayer.so)
   3: 0x00007f318e6232b5 in ptime::SessionHandler::doReceiveMessage_(ptime::CommEventObjects&)+0x1b1 at ptime/session/sm_handler.cc:1274 (libhdbsqlsession.so)
   4: 0x00007f318e6259fa in ptime::SessionHandler::receiveMessage_(Execution::Context&, ptime::ThreadStatusCallbackBase&, SessionLayer::CommEvent*, bool)+0x1d6 at ptime/session/sm_handler.cc:1940 (libhdbsqlsession.so)
   5: 0x00007f318e62670f in ptime::SessionHandler::receiveMessage(Execution::Context&, SessionLayer::CommEvent*, bool)+0x2b at ptime/session/sm_handler.cc:1884 (libhdbsqlsession.so)
   6: 0x00007f318e659137 in ptime::TcpReceiver::doWork(Execution::Context&, SessionLayer::CommMgr*)+0xdd3 at ptime/session/tcp_receiver.cc:392 (libhdbsqlsession.so)
   7: 0x00007f318e656f70 in ptime::TcpReceiver::runInner(void*)+0xd0 at ptime/session/tcp_receiver.cc:502 (libhdbsqlsession.so)
   8: 0x00007f318e6571d1 in non-virtual thunk to ptime::TcpReceiver::run(void*)+0x30 at ptime/session/tcp_receiver.cc:480 (libhdbsqlsession.so)
   9: 0x00007f3175e31427 in TrexThreads::PoolThread::run()+0xe53 at TrexThreads/PoolThread.cpp:423 (libhdbbasement.so)
  10: 0x00007f3175e32f00 in TrexThreads::PoolThread::run(Execution::ThreadRC&)+0x10 at TrexThreads/PoolThread.cpp:120 (libhdbbasement.so)
  11: 0x00007f3171c6a3ee in Execution::Thread::staticMainImp(Execution::Thread*)+0x54a at Basis/Execution/impl/Thread.cpp:593 (libhdbbasis.so)
  12: 0x00007f3171c72b05 in Execution::pthreadFunctionWrapper(Execution::Thread*)+0x1c1 at Basis/Execution/impl/ThreadInterposition.cpp:703 (libhdbbasis.so)
  13: 0x00007f317123b94a in start_thread+0xd6 (libpthread.so.0)
  14: 0x00007f316fd86d0f in __GI___clone+0x3b (libc.so.6)
exception type information:
 - 0: public ltt::exception@0x00007f317110a878
[7942]{-1}[-1/-1] 2023-04-13 18:03:38.011070 e SQLSession       sm_handler.cc(03315) : ===== START OF SESSION DUMP ======================
[7942]{-1}[-1/-1] 2023-04-13 18:03:38.011075 e SQLSession       sm_handler.cc(03316) : CHANNEL      : (sockfd:61, part:22) open_time=4532864 ms, exp_size(header)=416, act_size(buffer)=0
[7942]{-1}[-1/-1] 2023-04-13 18:03:38.011078 e SQLSession       sm_handler.cc(03317) : ACTION       : name=ExecutePrepared, message_type=EXECUTE, stocked_error_code=0, scrollable=0, oabap_stream=0
[7942]{-1}[-1/-1] 2023-04-13 18:03:38.012363 e SQLSession       sm_handler.cc(03318) : CLIENT       : <client hostname>[<client IP address>]:<port>(pid=<process ID>), client_library=JDBC 2.12.8-ce01a5c7bf23ae8a3b3b3ef4a501eb48cdbac672, client_program=HDBStudio
[7942]{-1}[-1/-1] 2023-04-13 18:03:38.012368 e SQLSession       sm_handler.cc(03319) : PROTOCOL     : 4.1, internal_session_id=1621988990704113, packet_count(message_id)=8, version_exchanged=1, authenticated=1
[7942]{-1}[-1/-1] 2023-04-13 18:03:38.012373 e SQLSession       sm_handler.cc(03320) : DISTRIBUTION : mode=2, version=6
[7942]{-1}[-1/-1] 2023-04-13 18:03:38.012375 e SQLSession       sm_handler.cc(03321) : ROUTING      : anchor=345090, primary=345090, own=345090, update_tid=0, A/A_origin_site_type=0, A/A_origin_conn=0, A/A_protocol_version=2
[7942]{-1}[-1/-1] 2023-04-13 18:03:38.012377 e SQLSession       sm_handler.cc(03323) : ===== END OF SESSION DUMP ========================

---

You would like to understand why these messages are logged in the indeserver tracing.


Read more...

Environment

  • SAP HANA Studio
  • SAP HANA, platform edition

Product

SAP HANA, platform edition all versions

Keywords

KBA , HAN-STD-ADM-DBA , SAP HANA Studio (Eclipse) Admin Tooling , HAN-DB , SAP HANA Database , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.