Will the console message for disconnected clients list ShMem clients as TCP/IP clients?

[VolkerBarth]

Using SA 12.0.1.3324, I'm trying to figure out an application problem ("post-mortem").

In the server's message log (dbsrv12 -o ...) there's a hint than the particular application has been disconnected abnormally. As this app runs locally and uses shared memory to connect, I'm puzzled that two messages tell me that

• a client socket was deactivated and
• a TCP/IP client has been disconnected, with the local IP address.

Is that simply a not correct wording in the error message, or should I conclude the app may have connected differently than expected?

---

I assume the former: Starting a local app makes sa_conn_info() lists the CommLink as "local" but killing the process still tells about a disconnected TCP/IP client.

[MCMartin · Accepted solution]

For me the message for a shared memory client reads:

Disconnecting shared memory client, process id not found
Disconnected SharedMemory client's AppInfo: ...

and for a tcp client:

Connection terminated abnormally
Disconnected TCPIP client's AppInfo: ...

Tested with 12.0.1.3537

[VolkerBarth · Accepted solution]

Yes, I verified this with 12.0.1.3554 - the messages are obviously correct.

I have figured out the problem is a different one:

When migrating to v12, I have specified the new v12 HOST parameter, and that makes even local connections using TPC/IP - which I was not aware of...

So the particular app is not using ShMem at all (in contrast to what I had expected), and the log messages are correct.

[MCMartin · Accepted solution]

That is really unexpected! I also thought, that shared memory is preferred always over tcpip if possible.

[VolkerBarth · Accepted solution]

Yep, see my new question🙂

[MarkCulp · Accepted solution]

This is expected behaviour. See my response to your question.

[VolkerBarth · Accepted solution]

Well, "expected behaviour" isn't a NPOV: Obviously developers and users of the product may have different ideas:)