nexcra / sipservlets

Automatically exported from code.google.com/p/sipservlets
0 stars 0 forks source link

Failovered ServletTimer couldn't be canceled #213

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
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.

Original issue reported on code.google.com by yukinobu...@gmail.com on 29 May 2013 at 8:59

Attachments:

GoogleCodeExporter commented 9 years ago
JBCP is not supported anymore, can you reach out to us by filling out this form 
http://www.telestax.com/contactus/#InquiryForm for a migration path to TelScale 
which is the equivalent ?

Original comment by jean.deruelle on 3 Jul 2013 at 8:48

GoogleCodeExporter commented 9 years ago

Original comment by jean.deruelle on 5 Jul 2013 at 7:44

GoogleCodeExporter commented 9 years ago

Original comment by jean.deruelle on 18 Apr 2014 at 10:27

GoogleCodeExporter commented 9 years ago

Original comment by jean.der...@telestax.com on 25 Aug 2014 at 10:53