facebook

Deployment if out of date, manual redeployment error msg

  1. MyEclipse Archived
  2.  > 
  3. General
Viewing 15 posts - 1 through 15 (of 26 total)
  • Author
    Posts
  • #235411 Reply

    ddistasio
    Member

    Hi,
    I just upgraded to the new version of MyEclipse amd I have been getting an error message when I try to redeploy code to my tomcat app server. I get the error msg: “Deployment is out of date due to changes in the underlying project contents. You’ll need to manually ‘Redeploy’ the project to update the deployed archive”. I have been unable to figure out what is causing this but redeploying requires that closing out of MyEclipse, deleting the archive from the webapps directory on the tomcat server, and restarting MyEclipse to deploy and rerun tomcat. Is there an easier way around this problem?

    #235414 Reply

    Riyad Kalla
    Member

    1) If you are using an exploded deployment, you will likely never get these messages as your changes are synced immediately.

    2) If you are using custom Ant scripts to generate files in your project, you MUST manually Refresh after running the scripts, this will cause this problem to arise as the file system comes out of sync after the script runs.

    3) You don’t need to close MyEclipse to redeploy, you only need to shut down your app server. The problem is to avoid read-locks on the files by the app server.

    #249447 Reply

    jkva
    Member

    @support-rkalla wrote:

    1) If you are using an exploded deployment, you will likely never get these messages as your changes are synced immediately.

    I am also using an exploded deployment, but I still get these errors. Usually when I manually redeploy, but also somtimes when I change something in Java code. My appserver is JBoss 4.0.2.

    #249507 Reply

    Thomas SMETS
    Member

    I use exploded archive and after moving the log4j.jar from <ProjectBase>/lib to <ProjectBase>/WebRoot/WEB-INF/lib I got the message when I tried to force a deployement

    Deployment is out of date due to changes in the underlying project contents. You'll need to manually 'Redeploy' the project to update the deployed archive.

    I now moved the lib back to <ProjectBase>/lib but it still fails…

    If I try to remove the TOMCAT in the potential target, it is not possible anymore…

    Any ideas … ?

    \T,

    #249529 Reply

    Riyad Kalla
    Member

    Thomas,
    Try and shut down your app server, remove your deployment then right click on the root of your project and do a Refresh. Then recreate your deployment.

    #249828 Reply

    Thomas SMETS
    Member

    @support-rkalla wrote:

    Thomas,
    Try and shut down your app server, remove your deployment then right click on the root of your project and do a Refresh. Then recreate your deployment.

    I think the main problem comes from the fact that I start TOMCAT with the following switch :

    
    Windows --> Preferences :
      MyEclipse 
       |_ Application Servers
            |_ Tomcat 4.0
    Optionnal Program Arguments
    

    I provide the following argument :

     -config /Projects/UseP6SpyInContainer/config/server.xml 

    The server.xml contains the following :

    
            <!-- Tomcat Application Context -->
            <Context path="/UseP6SpyInContainer" 
                     docBase="/Projects/UseP6SpyInContainer/WebRoot" 
                     reloadable="true" 
                     crossContext="true">
    

    In the menu :

    
    Windows --> Preferences :
      MyEclipse 
       |_ Application Servers
            |_ Tomcat 4.0
    

    I set the TOMCAT_BASE directory to :

    /Projects/UseP6SpyInContainer

    \T,

    #249840 Reply

    Riyad Kalla
    Member

    OHHH, this isn’t good. If you are actually using your project directory AS your context driectory, then you cannot create a deployment or if you do, it won’t really be a real deployment. Can you just try and work without a deployment, since you are already using the project dir as the context dir, all your changes should be immediate.

    Unfortunately I don’t think hotsync of classes will work…

    #250007 Reply

    for prevent the error “out of date deploy” add the property antiResourceLocking=”true” at the context.xml file located at META-INF directory of your web aplication, because default value for this property is “false” (this configuration used in Windows, Linux is desnecessary) the Windows locking any resource modifications, such as:

    <Context debug=”0″ displayName=”Base de dados sistema”
    path=”/sistema”
    docBase=”sistema” reloadable=”true” crossContext=”true” antiResourceLocking=”true” antiJARLocking=”true”>
    </Context>

    And so.

    😆

    #250324 Reply

    idfbins
    Member

    I added that to the context.xml. And that seems to solve the problem. However, it still does not sync automatically. I must redeploy my application each time I make a change to the struts MessageResources.properties file.

    #250326 Reply

    Riyad Kalla
    Member

    idfbins,
    If you are using an exploded deployment and you watch the time stamp on the file, chances are that MyEclipse is actually deploying this every time, it’s just the program you are using (ActionServlet in this case) isn’t written to poll and reload a changed properties file (or it is, and you haven’t turned the property on. I’m not sure if it supports it).

    #251334 Reply

    saran_v
    Member

    I’m getting the same ‘Deployment is out of date’ error. I uninstalled myeclipse, eclipse and tomcat and restarted from scratch. Still I’m getting the same error. But I have imported the .project file for my project from a source control. I don’t see a place where there is a out of sync issue.
    Trying to resolve this issue for the past few days, no luck so far. Any help will be highly appreciated.
    Thanks

    #251335 Reply

    Riyad Kalla
    Member

    Saran,
    Please right click on the root of your project and perform a “Refresh”, this will get files in sync with Eclipse again.

    #251339 Reply

    saran_v
    Member

    I did refresh. Its does not solve the issue. Also I do not see the “Deploy Location” edit field getteing enabled when I choose Tomcat 5 as my server in the “New Deployment” dialog. I always choose “<Custom Location>”. Is that a problem?

    Thanks for your fast response.

    #251340 Reply

    Riyad Kalla
    Member

    If you refresh your project *from the root*, then remove your deployment and create a new one, you are saying that it still shows “out of date”?

    Also the text box for specific app server deployments is not meant to be edited, that is what Custom Location is for and it’s fine if you’d rather us a custom location deployment.

    #251341 Reply

    saran_v
    Member

    Riyad,

    Yes. I did refresh my project from the root, then remove the deployment, create a new one. Unfortunatly I still get the ‘Deployment out of date error’.

    As I said earlier, not only refreshing the project, I uninstalled myeclipse, eclipse and tomcat and started with fresh tools.

Viewing 15 posts - 1 through 15 (of 26 total)
Reply To: Deployment if out of date, manual redeployment error msg

You must be logged in to post in the forum log in