Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Sip-Servlets MSS-2.1.0.FINAL
Roadmap-Fix
New issue 213 by [email protected]: Failovered ServletTimer couldn't be
canceled
http://code.google.com/p/sipservlets/issues/detail?id=213
What steps will reproduce the problem?
1. start clustered JBCPs
2. create a SipApplicationSession
3. create a ServletTimer
4. shutdown a JBCP
5. The SipApplicationSession is failed over to the other JBCP
6. reschedule the ServletTimer
7. cancel the ServletTimer
What is the expected output? What do you see instead?
ServletTimer couldn't be canceled at step7.
What version of the product are you using? On what operating system?
JBCP5.1.5.GA
RHEL5.6
Please provide any additional information below.
FaultTolerantScheduler couldn't cancel the ServletTimer,
because ServletTimer is created with an another id at step 6.
I create the patch for this problem.
Attachments:
FaultTolerantTimerServiceImpl.diff 904 bytes
ServletTimerImpl.diff 1.6 KB
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "mobicents-all-issues-changes" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
