Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Google Groups by Roberto, 1 year ago
%3A3gpp-application.ims.iari.gsma-is" > Date: Mon, 11 Jan 2010 10:38:06 GMT > P-Associated-URI: > <sip:+346...@rcs.alcatel-lucent.com>,<tel:+3460000000000> > Server: Alcatel-Lucent-HPSS/3.0.3 > Content-Length: 0 > > at
org.mobicents.servlet.sip.core.dispatchers.DispatcherException: Unexpected
>> exception while processing response : SIP/2.0 200 OK
>> Call-ID: 17f8ab6df40d3244...@192.168.1.65
>> CSeq: 3 REGISTER
>> From:
>> <sip:+3460...@rcs.alcatel-lucent.com>;tag=41081757_85c9a2a2_48934332311391
>> To:
>> <sip:+346...@rcs.alcatel-lucent.com>;tag=SD799ba99-4a78064c-1263206286238790
>> Via: SIP/2.0/UDP
>> 192.168.1.65:5080;branch=z9hG4bK48934332311391_85c9a2a2_48958179429610
>> Contact:
>> <sip:192.168.1.65:5080;transport=udp>;expires=0;+g.oma.sip-im;+g.3gpp.app_ref="urn%3Aurn-7%3A3gpp-application.ims.iari.gsma-is"
>> Date: Mon, 11 Jan 2010 10:38:06 GMT
>> P-Associated-URI:
>> <sip:+346...@rcs.alcatel-lucent.com>,<tel:+3460000000000>
>> Server: Alcatel-Lucent-HPSS/3.0.3
>> Content-Length: 0
>>
>>
 at
>> org.mobicents.servlet.sip.core.dispatchers.ResponseDispatcher$1.dispatch(ResponseDispatcher.java:314)
 at
>> org.mobicents.servlet.sip.core.dispatchers.DispatchTask.dispatchAndHandleExceptions(DispatchTask.java:55)
 at
>> org.mobicents.servlet.sip.core.dispatchers.DispatchTask.run(DispatchTask.java:50)
 at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)	at java.lang.Thread.run(Thread.java:619)