Hi Jonathan, could you open a JIRA for the below topic, please? It makes it a lot easier to track the weird behaviour and it is so important to document your observations. Thereby, we’ll be able to reference this issue in upcoming discussions. Please put additional material into the JIRA, as long as you can provide it (legally speaking).
Optional: Can you a MWE that demonstrates the issue somehow? Best Martin — https://twitter.com/mawiesne <https://twitter.com/mawiesne> > Am 07.01.2019 um 03:47 schrieb exabrial12 <[email protected]>: > > Hey guys, > > We're noticing a pretty strange issue processing a large number of JMS > messages. After about 20k messages, messages consumed per second drops off > and there's heavy GC activity (smells like a memory leak). What interesting > though is the server continues to run and doesn't OutOfMemoryError. A simple > restart of TomEE (but not the broker) temporarily fixes the problem. We're > using an external broker, not the internal one > > What's interesting, is that Jonathan Gallimore and I were talking about a > similar issue with Websockets. We noticed that eventually the servers will > exhibit the same behavior once enough websockets are opened and closed. This > issue occurs infrequently enough because we might handle 20,000 websockets > over the course of a few days, but we can process 20,000 JMS messages in a > few mins. > > > I have a heap dump from the issue and several jstacks. I'll be honest, I'm > not sure where to start. In the past I've solved memory leaks by careful > code audits. Our codebase happens to be mostly stateless, with everything > else being managed by CDI scopes (ApplicationScoped and TransactionScoped). > > What's a good way to get started? > > > > -- > Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
smime.p7s
Description: S/MIME cryptographic signature
