geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasad Kashyap (JIRA)" <>
Subject [jira] Commented: (GERONIMO-1974) Listing WARs portlet broken after a redeploy using CLI
Date Fri, 05 May 2006 03:32:17 GMT
    [ ] 

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.

I was trying to mimic a customer scenario of the customer redeploying another version of his

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:
>      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
> (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:
For more information on JIRA, see:

View raw message