[
https://issues.apache.org/jira/browse/TRAFODION-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572036#comment-16572036
]
Selvaganesan Govindarajan commented on TRAFODION-3180:
------------------------------------------------------
The mxssmp process keeps the port in CLOSE_WAIT because the socket wasn't
closed on the server side when client exits gracefully as well as abruptly.
Upon debugging this issue, the seabed layer in Trafodion doesn't handle more
than one open to a process in a correct way. I have changed the IPC
infrastructure in SQL to ensure that there is ssmp process is opened only once
in mxosrvr process.
> 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)
