Why do these make you suspicious? I would not kill the process(es). I would rather consider restarting sipxconfig as a service. "If" sipxproxy or sipxbridge restarts then your calls using verizon will drop.
I would ask more questions about how to zero in on this because sipxbridge is also a process that uses java. Killing a java process might affect sipxbridge, so care is needed. Anyone have any better ideas? Also, java uses nearly 100% of available memory by design, so memory usage may not be a good indicator of anything wrong. Sipxconfig log should have more pointed information. You should look there. ============================ Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: tgrazi...@myitdepartment.net LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ ----- Original Message ----- From: sipx-users-boun...@list.sipfoundry.org <sipx-users-boun...@list.sipfoundry.org> To: sipx-users@list.sipfoundry.org <sipx-users@list.sipfoundry.org> Sent: Mon Jan 25 15:12:03 2010 Subject: Re: [sipx-users] Boss decided to run a report of some sort - killedjavaI think These seem to be the main offenders on memory top - 14:04:34 up 4 days, 20:43, 1 user, load average: 0.51, 0.47, 0.45 Tasks: 152 total, 1 running, 151 sleeping, 0 stopped, 0 zombie Cpu(s): 1.2%us, 0.5%sy, 0.0%ni, 98.0%id, 0.0%wa, 0.0%hi, 0.3%si, 0.0%st Mem: 8177104k total, 2500040k used, 5677064k free, 196264k buffers Swap: 10223608k total, 0k used, 10223608k free, 913316k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 32317 sipxchan 18 0 1496m 425m 11m S 0.0 5.3 28:36.40 java 4490 sipxchan 19 0 1367m 181m 9180 S 0.3 2.3 2:19.21 java 32404 sipxchan 19 0 1354m 138m 9080 S 1.0 1.7 6:59.58 java I would just kill the java process if I was sure that wouldn't cause any issues. On 1/25/2010 1:31 PM, mkitchin.pub...@gmail.com wrote: > Everything going great, and then my boss decided to run a report of > some sort (I don't know what) and he said it locked up. Now my web > interface is inaccessible. I get this message below > > HTTP ERROR: 500 > PermGen space > RequestURI=/sipxconfig/app > > Powered by Jetty:// > > From searching a little, I'm assuming this is a Java memory issue. > When I first looked at the box, I saw a java process taking a ton of > resources. > This one is still taking constant CPU. > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 32404 sipxchan 19 0 1354m 137m 9080 S 3.0 1.7 6:24.26 java > > Is there something that i safe to kill or restart without kicking > everyone off their calls? > _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
