>>> On 5/21/2010 at 12:17 PM, in message <[email protected]>, >>> Josh Patten <[email protected]> wrote: > 16 GB RAM...It's only happened once. I wasn't seeing a memory spike > > Also, a ruby script doing some CDR stuff went rouge once and chewed up a > core until I killed it, then it came right back and started behaving >
The client where i see this issue doesn't show any obvious openfire errors in the logs....but it's not used there and I don't think they even know IM exist. While the memory consumption shows well within normal range, I only suspected the 2GB's as it was the only thing I see different. I wasn't sure how the default java stack size related to system memory. When I let the operation run long enough then sipxconfig responds with a java heap stack out of memory...even though memory usage on the system is fine and no swapping has occurred. I can replicate it bout 25% of the time by simply clicking the button to add a new user group. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
