Return-Path: Delivered-To: apmail-tapestry-commits-archive@minotaur.apache.org Received: (qmail 9831 invoked from network); 1 Oct 2010 01:36:58 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Oct 2010 01:36:58 -0000 Received: (qmail 58061 invoked by uid 500); 1 Oct 2010 01:36:58 -0000 Delivered-To: apmail-tapestry-commits-archive@tapestry.apache.org Received: (qmail 57933 invoked by uid 500); 1 Oct 2010 01:36:57 -0000 Mailing-List: contact commits-help@tapestry.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tapestry.apache.org Delivered-To: mailing list commits@tapestry.apache.org Received: (qmail 57918 invoked by uid 99); 1 Oct 2010 01:36:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Oct 2010 01:36:57 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Oct 2010 01:36:54 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o911aXQw010380 for ; Fri, 1 Oct 2010 01:36:33 GMT Message-ID: <6078467.490561285896993003.JavaMail.jira@thor> Date: Thu, 30 Sep 2010 21:36:33 -0400 (EDT) From: "Howard M. Lewis Ship (JIRA)" To: commits@tapestry.apache.org Subject: [jira] Created: (TAP5-1287) Services do not reload even though they should MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org 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 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.