In trying to understand "where" and "when" CPU spikes were occurring, I
noticed an oddity in the following process (this is not something I'm asking
anyone to do in a production environment)...

In disabling the "default" IM account and renaming it to something more
meaningful (from 200 to jdoe), then re-enabling it, I see a 5 minute long
CPU spike from java.

On a lark (I like to use that term a lot, don't know why), I started to look
at the log sizes and in particular the sipxopenfire log.

Whether I have installed from ISO or on a new Centos system via RPM, leaving
logging at the default levels, I see a constant repeating java exception
error:

JAVA:INFO:sipx.mydomain.com:
PipelineThread-0:00000000:sipxcallwatcher:"[SIPServerTransaction.java:521][SIPTransactionStack.java:1562][SIPTransactionStack.java:1336][TCPMessageChannel.java:510][PipelinedMsgParser.java:361][Thread.java:619]"
"2010-05-19T18:06:11.012000Z":2230826:JAVA:INFO:sipx.mydomain.com:
PipelineThread-0:00000000:sipxcallwatcher:"[SIPTransaction.java:1152][SIPTransactionStack.java:1361][TCPMessageChannel.java:510][PipelinedMsgParser.java:361][Thread.java:619]"
"2010-05-19T18:06:11.013000Z":2230827:JAVA:INFO:sipx.mydomain.com:
PipelineThread-0:00000000:sipxcallwatcher:"[SIPTransaction.java:556][SIPServerTransaction.java:1472][SIPServerTransaction.java:734][TCPMessageChannel.java:515][PipelinedMsgParser.java:361][Thread.java:619]"
"2010-05-19T18:06:11.013000Z":2230828:JAVA:INFO:sipx.mydomain.com:
PipelineThread-0:00000000:sipxcallwatcher:"[SipProviderImpl.java:182][DialogFilter.java:1137][SIPServerTransaction.java:823][TCPMessageChannel.java:515][PipelinedMsgParser.java:361][Thread.java:619]"
"2010-05-19T18:06:11.013000Z":2230829:JAVA:INFO:sipx.mydomain.com:PipelineThread-0:00000000:SubscribeDialog:"[SubscribeDialog
FSM:org.sipfoundry.sipcallwatcher.subscribedialog.subscribedia...@1adf08fgov.nist.javax.sip.stack.sipdialog@142db11]
Incoming event 'processNotifyRequest'"
"2010-05-19T18:06:11.013000Z":2230830:JAVA:INFO:sipx.mydomain.com:PipelineThread-0:00000000:SubscribeDialog:"org.sipfoundry.sipcallwatcher.SubscribeDialog.UnknownTransactionException:
SubscribeDialog::validateServerTransaction: Request associated with null
server transaction"
"2010-05-19T18:06:11.014000Z":2230831:JAVA:ERR:sipx.mydomain.com:PipelineThread-0:00000000:sipxcallwatcher:"Exception
occured"
org.sipfoundry.sipcallwatcher.CallWatcherException:
java.lang.NullPointerException
        at
org.sipfoundry.sipcallwatcher.Subscriber.constructAndSendResponseForRequest(Subscriber.java:325)
        at
org.sipfoundry.sipcallwatcher.SubscribeDialog.SubscribeDialog.processNotifyRequest(SubscribeDialog.java:73)
        at
org.sipfoundry.sipcallwatcher.Subscriber.processRequest(Subscriber.java:140)
        at
gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:224)
        at
gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:192)
        at
gov.nist.javax.sip.DialogFilter.processRequest(DialogFilter.java:1137)
        at
gov.nist.javax.sip.stack.SIPServerTransaction.processRequest(SIPServerTransaction.java:823)
        at
gov.nist.javax.sip.stack.TCPMessageChannel.processMessage(TCPMessageChannel.java:515)
        at
gov.nist.javax.sip.parser.PipelinedMsgParser.run(PipelinedMsgParser.java:361)
        at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.NullPointerException
        at
org.sipfoundry.sipcallwatcher.Subscriber.constructAndSendResponseForRequest(Subscriber.java:322)
        ... 9 more
"2010-05-19T18:06:11.014000Z":2230832:JAVA:INFO:sipx.mydomain.com:
PipelineThread-0:00000000:sipxcallwatcher:"[SIPTransaction.java:1197][SIPTransaction.java:1183][SIPServerTransaction.java:1704][EventScanner.java:255][SipProviderImpl.java:192][DialogFilter.java:1137][SIPServerTransaction.java:823][TCPMessageChannel.java:515][PipelinedMsgParser.java:361][Thread.java:619]"
"2010-05-19T18:06:11.014000Z":2230833:JAVA:INFO:sipx.mydomain.com:
PipelineThread-0:00000000:sipxcallwatcher:"[SIPTransaction.java:1197][SIPTransaction.java:1183][SIPServerTransaction.java:1704][TCPMessageChannel.java:520][PipelinedMsgParser.java:361][Thread.java:619]"

In particular I never got IM to work for that user after changing the IM ID,
so I yanked it and recreated it.

While I don't mean to combine two potential issues, I think they are
inextricably linked.

Why do I see a very constant java exception error in sipxopenfire?



-- 
======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: tgrazi...@voice.myitdepartment.net
Fax: 434.984.8431

Email: tgrazi...@myitdepartment.net

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: helpd...@voice.myitdepartment.net
Fax: 434.984.8427

Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/

Why do mathematicians always confuse Halloween and Christmas?
Because 31 Oct = 25 Dec.
_______________________________________________
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/

Reply via email to