Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 51060 invoked from network); 5 May 2006 03:32:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 5 May 2006 03:32:56 -0000 Received: (qmail 89132 invoked by uid 500); 5 May 2006 03:32:53 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 89081 invoked by uid 500); 5 May 2006 03:32:53 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 89070 invoked by uid 99); 5 May 2006 03:32:53 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 May 2006 20:32:53 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 May 2006 20:32:52 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 529D071429D for ; Fri, 5 May 2006 03:32:17 +0000 (GMT) Message-ID: <8681672.1146799937286.JavaMail.jira@brutus> Date: Fri, 5 May 2006 03:32:17 +0000 (GMT+00:00) From: "Prasad Kashyap (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Commented: (GERONIMO-1974) Listing WARs portlet broken after a redeploy using CLI In-Reply-To: <7502529.1146673846851.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/GERONIMO-1974?page=comments#action_12377947 ] Prasad Kashyap commented on GERONIMO-1974: ------------------------------------------ I bumped the version number in our welcome-jetty plan. It's the same 1.1 plan we have. C:\Apache\geronimo\configs\welcome-jetty\target\plan\plan.xml I was trying to mimic a customer scenario of the customer redeploying another version of his app. The command I used is pasted in an earlier comment. One other thing - after redeploying 1.2 version of welcome-jetty against 1.1 version already installed, in our var/config/config.xml, the geronimo/welcome-jetty/1.1-SNAPSHOT/car is unloaded but the 1.2 is never loaded into the config file. However, the 1.2 resources are installed in the repo along with the 1.1 version resources This worked differently yesterday. Until y'day, the files were in the repo and the latest version was loaded in the config. The earlier versions were left behind in the repo and the config.xml had the earlier version set to load=false. > Listing WARs portlet broken after a redeploy using CLI > ------------------------------------------------------ > > Key: GERONIMO-1974 > URL: http://issues.apache.org/jira/browse/GERONIMO-1974 > Project: Geronimo > Type: Bug > Security: public(Regular issues) > Components: console > Versions: 1.1 > Reporter: Prasad Kashyap > Assignee: Aaron Mulder > Priority: Blocker > Fix For: 1.1 > Attachments: redeploy-stacktrace.txt > > After a redeploy is done by CLI, the portlet in the console that displays the list is broken. > (http://localhost:8080/console/portal/apps/apps_war). It shows the message, "Error occurred in portlet!" . It needs a server restart to fix this problem. Stacktrace attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira