incubator-lokahi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Feist (JIRA)" <j...@apache.org>
Subject [jira] Updated: (LOKAHI-6) Fix "move context" to first undeploy context before moving
Date Tue, 30 Oct 2007 13:09:50 GMT

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

Jeff Feist updated LOKAHI-6:
----------------------------

    Attachment: move_context.txt

Instead of only installing and deploying configs to the new tomcat pool, I added a check to
see if the old pool and the new pool are different. If they are different, the old context
is undeployed and the updated configs are deployed to the old pool. Then, the new context
is installed and updated.

> Fix "move context" to first undeploy context before moving
> ----------------------------------------------------------
>
>                 Key: LOKAHI-6
>                 URL: https://issues.apache.org/jira/browse/LOKAHI-6
>             Project: Lokahi
>          Issue Type: Improvement
>            Reporter: Jeff Feist
>         Attachments: move_context.txt
>
>
> "moving contexts" option has the bad side effect of only moving the context in the database
- it doesn't stop the context in the original jvm before moving it, so we end up with 2 instances
of the application running - one in the original jvm, and one in the new JVM. And then because
the context is no longer in the original jvm.conf when you deploy it, you don't have a way
to stop it from running in the original JVM.

-- 
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