[SYNAPSE-288] AbstractPollingTransportListener fails to cancel timer on destroy

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: NIGHTLY
• Fix Version/s: 1.2
• Component/s: Transports
• Assignee: Asankha Chamath Perera
• Reporter: Andreas Veithen
• Created: 06/May/08 17:46
• Updated: 04/Jun/08 17:48
• Resolved: 04/Jun/08 17:48

Description

After AbstractPollingTransportListener#destroy is called, the following exception is triggered:

Exception in thread "PollTimer" java.util.concurrent.RejectedExecutionException
at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:1477)
at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:384)
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:856)
at org.apache.synapse.transport.base.threads.NativeWorkerPool.execute(NativeWorkerPool.java:55)
at org.apache.synapse.transport.base.AbstractPollingTransportListener$1.run(AbstractPollingTransportListener.java:81)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)

Obviously the timer still tries to schedule a new task after the worker pool has been shut down. I suspect that the reason is that AbstractTransportListener#stop doesn't call stopListeningForService, given that AbstractPollingTransportListener cancels the timers there.

Issue Links

• is duplicated by: SYNAPSE-331 RejectedExecutionException when stoping the ESB with configured mail transport listener