On PIM management servers we are seeing that Tibco process, tibemsd, stops running. When I check the log, ems.log, found in CA/AccessControlServer/MessageQueue/tibco/log we are seeing these types of messages.
SEVERE ERROR: No memory to create prop.
SEVERE ERROR: No memory trying to initialize connection.
SEVERE ERROR: No memory for creating connection.
SEVERE ERROR: No memory to process incoming data from connection id=####. Connection terminated.
This is caused by the 32bit tibemsd process reaching its 2GB maximum RAM usage and running out of memory. It can reach it's maximum memory due to the number of consumers, aka endpoint connections, and the number of messages sitting in the queues without being consumed.
There are two main ways to correct this error. First, is to add more Distribution Server to spread the load of the consumers. The other would be to update Tibco to 64bit so it is able to handle more RAM and thus able to handle more connection. The Tibco upgrade can be requested from a support ticket.