Symptom
HANA indexserver trace shows below similar error message:
e SQLSession sm_handler.cc(03022) : (sockfd:5217, channel:0x000072740eadfb00, event:0x000078ee7fcdfe00, part:371) communication error: SSL exception 1: no.2110005 (Basis/IO/Stream/impl/NetworkChannel.cpp:1783) TID: 663807
Error during stream send: NetworkChannel::sendvRawImp - ::writev failed, rc=32: Broken pipe; $Context$=[26a5b910e5e825ea,[...]:30015,[...]:40060,SES,0]; $channel$={<NetworkChannelSSLFilter>={<NetworkChannelBase>={this=135315716674584, fd=INVALID, refCnt=1, local=[...]/30015_tcp, remote=[...]/40060_tcp, state=Closed, pending=[----]}}}
HANA doesn't have resource issue. Every time the error happens to same remote IP or same app.
On remote client side, following similar JDBC error can be seen:
java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30000ms (total=10, active=10, idle=0, waiting=182)
Read more...
Environment
- SAP HANA, platform edition 1.0
- SAP HANA, platform edition 2.0
Keywords
KBA , HAN-DB-CLI , SAP HANA Clients (JDBC, ODBC) , 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.
SAP Knowledge Base Article - Preview