[
https://issues.apache.org/jira/browse/TRAFODION-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572031#comment-16572031
]
Selvaganesan Govindarajan commented on TRAFODION-3180:
------------------------------------------------------
Analysis revealed that the mxosrvr process in connecting state was attempting
to open the ssmp process on the node for a non-unique query as part of
establishing connection. The ssmp process has many ports in CLOSE_WAIT state.
It looks like the client happens to hit on a port that is in CLOSE_WAIT state.
The port transitions to ESTABLISHED state after some time. Hence the connection
was taking a longer time.
> At times establishing a JDBC/ODBC connection takes observably long time
> -----------------------------------------------------------------------
>
> Key: TRAFODION-3180
> URL: https://issues.apache.org/jira/browse/TRAFODION-3180
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-exe
> Affects Versions: any
> Reporter: Selvaganesan Govindarajan
> Assignee: Selvaganesan Govindarajan
> Priority: Major
> Fix For: 2.4
>
>
> When it takes time, DCS master status page shows the link between driver and
> the mxosrvr process is in CONNECTING state. After 30 seconds or a minute, the
> connection is established. This issue was observed at a customer installation
> when Trafodion cluster has been up and running for months.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
