[JAMES-9] JamesSpoolManager doesn't shutdown gracefully

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Fix Version/s: 2.2.0
• Component/s: SpoolManager & Processors
• Environment: Operating System: Other; Platform: Other
• Bugzilla Id: 4033
• Assignee: Unassigned
• Reporter: Serge Knystautas
• Created: 09/Oct/01 02:58
• Updated: 07/Jun/04 00:38
• Resolved: 14/Apr/04 04:21

Description

On Sat, 29 Sep 2001 06:36, Matthew Pangaro wrote:
> java.lang.IllegalStateException: Using a stale object reference to call a
> disposed Block. at
> org.apache.avalon.phoenix.components.application.BlockInvocationHandler.inv
>oke(BlockInvocationHandler.java:92) at $Proxy9.log(Unknown Source)
> at org.apache.mailet.GenericMailet.log(GenericMailet.java:148)
> at
> org.apache.james.transport.mailets.RemoteDelivery.run(RemoteDelivery.java:3
>71) at java.lang.Thread.run(Thread.java:484)
> I don't know if the same occurs from a timeout of a connection to any of
> the other services. Still shuts down ok, but seems like it should be
> caught, or the object reference should be cleaned up. Sorry if this should
> have been posted to Avalon list, but I wasn't really sure where it
> belonged.

The problem is that transport.JamesSpoolManager does not implement the
dispose method. It should implement dispose() to wait till all currently
executing processors shutdown gracefully. Todo this it will need to make sure
run() shuts down properly.