This might be related....
During my stress tests (goes ok for +/- 20 minutes) then exception
below sometimes occurs. But I need to restart tomcat to solve the
problem :(
java.lang.IllegalStateException: Timer already cancelled.
at java.util.Timer.sched(Timer.java:354)
at java.util.Timer.schedule(Timer.java:170)
at org.mobicents.servlet.sip.proxy.ProxyBranchImpl.updateTimer
(ProxyBranchImpl.java:587)
at org.mobicents.servlet.sip.proxy.ProxyBranchImpl.start
(ProxyBranchImpl.java:256)
at org.mobicents.servlet.sip.proxy.ProxyImpl.startNextUntriedBranch
(ProxyImpl.java:555)
at org.mobicents.servlet.sip.proxy.ProxyImpl.startProxy
(ProxyImpl.java:446)
at org.mobicents.servlet.sip.proxy.ProxyImpl.proxyTo(ProxyImpl.java:
308)
at
nl.telecats.kasteel.fastvoip.sipservlets.ForwardSipServlet.setupCall
(ForwardSipServlet.java:830)
at nl.telecats.kasteel.fastvoip.sipservlets.ForwardSipServlet.doInvite
(ForwardSipServlet.java:263)
at javax.servlet.sip.SipServlet.doRequest(SipServlet.java:225)
at
nl.telecats.kasteel.fastvoip.sipservlets.ForwardSipServlet.doRequest
(ForwardSipServlet.java:132)
at javax.servlet.sip.SipServlet.service(SipServlet.java:325)
at
org.mobicents.servlet.sip.core.dispatchers.MessageDispatcher.callServlet
(MessageDispatcher.java:243)
at org.mobicents.servlet.sip.core.dispatchers.InitialRequestDispatcher
$1.dispatch(InitialRequestDispatcher.java:424)
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:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:595)
On 7 aug, 20:16, Vladimir Ralev <
vladimir.ra...@gmail.com> wrote:
> OK, this is what i wanted. Thanks. I will check it out.
>
> On Fri, Aug 7, 2009 at 9:10 PM, Raymond Domingo<
raym...@domingo.nl> wrote:
> > sorry, something went wrong.
> > here it is, thnx in advance
>
> > talk to you after my holliday.
>
> > 2009/8/6 Vladimir Ralev <
vladimir.ra...@gmail.com>:
>
> >> I dont see anything attached in this email :)
>
> >> On Thu, Aug 6, 2009 at 6:39 PM, Raymond Domingo<
raym...@domingo.nl> wrote:
>
> >>> retry :)
> >>> is this what you are looking for ?
>
> >>> 2009/8/6 Vladimir Ralev <
vladimir.ra...@gmail.com>:
>
> >>>> Not quite. When you capture it packet by packet in wireshark you
> >>>> should be able to do File -> Save in the so called pcap format that
> >>>> can be opened from wireshark directly. What I need are the headers of
> >>>> the sip message.
>
> >>>> On Thu, Aug 6, 2009 at 6:28 PM, Raymond Domingo<
raym...@domingo.nl> wrote:
> >>>>> This should be it.
>
> >>>>> 2009/8/6 Vladimir Ralev <
vladimir.ra...@gmail.com>:
>
> >>>>>> It is very hard to follow your wireshark, because there seem tobe many
> >>>>>> retransmissions and phones do not OK the CANCEL and it's hard to tell
> >>>>>> what the OK responses are for. Can you send a full wireshark (the
> >>>>>> actual packets) ?
> >>>>>> On Thu, Aug 6, 2009 at 3:09 PM, Raymond Domingo<
raym...@domingo.nl> wrote:
> >>>>>>> It's a better now.
> >>>>>>> But there is still an invite sent after a branch is cancelled, see
> >>>>>>> attached wireshark log.
>
> >>>>>>> You see
> >>>>>>> 1 - invite is send to (dummy host) 74.125.77.121
> >>>>>>> 2 - cancel is send to (dummy host) 74.125.77.121
>
> >>>>>>> 3 - invite is send to (good host) 192.168.23.110
> >>>>>>> 4 - (good host) 192.168.23.110 responses (trying, ringing, ok,....)
>
> >>>>>>> 5 - an other invite is send to (dummy host) 74.125.77.121
>
> >>>>>>> Any idea what causes this ?
>
> >>>>>>> ps: It's my last day for the holliday. So if I don't reply, I will be
> >>>>>>> back 17 aug.
>
> >>>>>>> 2009/8/6 Vladimir Ralev <
vladimir.ra...@gmail.com>:
>
> >>>>>>>> OK. It seems sequential proxying is very poorly covered by our tests
> >>>>>>>> and the 289 TCK. I think they should be working for you now with the
> >>>>>>>> code from trunk. Let me know if you still have problems. Thanks a lot
> >>>>>>>> for the report and the analysis. Feel free to open issues directly in
> >>>>>>>> our tracker.
>
> >>>>>>>> On Thu, Aug 6, 2009 at 10:51 AM, Vladimir Ralev<
vladimir.ra...@gmail.com> wrote:
> >>>>>>>>> Hmm, ok thanks. It will be working soon I promise.
>
> >>>>>>>>> On Thu, Aug 6, 2009 at 10:46 AM, Raymond Domingo<
raym...@domingo.nl> wrote:
> >>>>>>>>>> ok, I updated (my version ProxyImpl.java 7344) and retested.
> >>>>>>>>>> Seems invites are still sended after cancel is sended...
> >>>>>>>>>> see the wireshark log in attachement...
>
> >>>>>>>>>> 2009/8/6 Raymond Domingo <
raym...@domingo.nl>:
> ...
>
> meer lezen »