tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Updated: (TAP5-1287) Services do not reload even though they should
Date Fri, 01 Oct 2010 16:54:33 GMT

     [ https://issues.apache.org/jira/browse/TAP5-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship updated TAP5-1287:
---------------------------------------


This could represent the difference between service reloading and proxy reloading; the objects
in question were created via ObjectLocator.proxy().

> Services do not reload even though they should
> ----------------------------------------------
>
>                 Key: TAP5-1287
>                 URL: https://issues.apache.org/jira/browse/TAP5-1287
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-ioc
>    Affects Versions: 5.2.2
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message