Back to bug 1401118
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Rory Thrasher | 2016-12-12 21:43:15 UTC | Status | NEW | MODIFIED |
| errata-xmlrpc | 2016-12-12 21:43:43 UTC | Status | MODIFIED | ON_QA |
| Johnny Liu | 2016-12-13 05:46:34 UTC | Flags | needinfo?(rthrashe) | |
| Rory Thrasher | 2016-12-13 19:06:56 UTC | Flags | needinfo?(rthrashe) | |
| Timothy Williams | 2016-12-15 16:25:45 UTC | Status | ON_QA | CLOSED |
| Resolution | --- | CANTFIX | ||
| Last Closed | 2016-12-15 11:25:45 UTC | |||
| Rory Thrasher | 2016-12-16 17:24:06 UTC | Status | CLOSED | ASSIGNED |
| Resolution | CANTFIX | --- | ||
| Keywords | Reopened | |||
| Rory Thrasher | 2016-12-19 21:55:42 UTC | Doc Text | Cause: In rare cases, a broker would successfully make an activemq connection, but immediately run out of memory or otherwise be unable to do anything with that connection. Consequence: The broker will have an open connection with an activemq server that is not functioning. The broker will not properly failover to an alternate activemq server, even if available. Workaround (if any): The best way to workaround this issue is to determine and fix the cause of activemq's failure (probably an out-of-memory error). Setting wrapper.java.additional.8=-Dorg.apache.activemq.UseDedicatedTaskRunner to false in the file `/etc/activemq/wrapper.conf` was able to fix the memory issue. Result: Fixing the problem behind the activemq failure should allow activemq to function normally. | |
| Doc Type | If docs needed, set a value | Known Issue | ||
| Eric Rich | 2017-05-09 12:33:45 UTC | Status | ASSIGNED | CLOSED |
| Resolution | --- | EOL | ||
| Last Closed | 2016-12-15 11:25:45 UTC | 2017-05-09 08:33:45 UTC |
Back to bug 1401118