Last Modified: Dec 13, 2019
See more info
Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 11.6.4, 11.6.5, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4
Opened: Nov 18, 2015
When troubleshooting the tmm state when mcpd exits, it is not possible to generate a tmm core
Unable to force a tmm core when mcpd exits. There is no functional impact to this but it can make diagnosing issues more difficult.
Troubleshooting mcpd and tmm state at the same time
A new sys db variable has been added called tmm.mcp.disconnect.core to cause tmm to core when mcpd disconnects.
A new sys db variable has been added called tmm.mcp.disconnect.core. The default value is disabled. When enabled, tmm will core if mcpd exists. This can be useful for troubleshooting purposes.