[TAP5-1287] Some services require a notification that they have been reloaded, so they can clean up external dependencies

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.2.2
• Fix Version/s: 5.2.2
• Component/s: tapestry-ioc
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 01/Oct/10 01:36
• Updated: 01/Oct/10 22:13
• Resolved: 01/Oct/10 20:34

Description

Been working on an application that uses a lot of JMS. I noticed that reloads did not appear to happen as expected.

DEBUG MessageSinkSource - Invoking constructor public com.fivoosh.services.activemq.MessageSinkSourceImpl(org.slf4j.Logger,com.fivoosh.services.activemq.ActiveMQConnectionSource,org.apache.tapestry5.ioc.services.PerthreadManager,com.fivoosh.services.TimeService,java.util.Map).
DEBUG MessageSinkSource - BEGIN Analyzing com.fivoosh.services.activemq.MessageSinkSourceImpl$1
DEBUG MessageSinkSource - END Analyzing com.fivoosh.services.activemq.MessageSinkSourceImpl$1
DEBUG MessageSinkSource - BEGIN Analyzing com.fivoosh.services.activemq.MessageSinkSourceImpl$TextQueueSender
DEBUG MessageSinkSource - END Analyzing com.fivoosh.services.activemq.MessageSinkSourceImpl$TextQueueSender
DEBUG MasterMessageHandler - Processing message 'ID:Howards-Mighty-Tool.local-56885-1285896586008-3:0:9:1:1' from queue 'echo'
Message received on thread ActiveMQ Session Task:
{
"foo" : "bar"
}

I then changed the code (it affects the logging message that starts "Processing message ....":

DEBUG MasterMessageHandler - Implementation class com.fivoosh.services.activemq.MasterMessageHandlerImpl has changed and will be reloaded on next use.
DEBUG MasterMessageHandler - Processing message 'ID:Howards-Mighty-Tool.local-56885-1285896586008-3:0:10:1:1' from queue 'echo'
Message received on thread ActiveMQ Session Task:
{
"foo" : "bar"
}

Note that the message indicates the implementation class changed, but the old behavior is stuck.

Later changes to the code and new messages sent:

DEBUG MasterMessageHandler - Processing message 'ID:Howards-Mighty-Tool.local-56885-1285896586008-3:0:12:1:1' from queue 'echo'
Message received on thread ActiveMQ Session Task:
{
"foo" : "baz"
}

... do not even register that a change occured.