- This topic has 19 replies, 5 voices, and was last updated 20 years, 6 months ago by
.
-
Posts
-
i installed everything fresh the day before yesterday (latest 2.x eclipse, latest myeclipse, jdk 1.4.2, tomcat 4.1.29). since doing the fresh install, it seems that everytime i close eclipse and reopen it, the deployments that i have set up are “forgotten”. i have to “re-set” them up everytime i restart eclipse. is this normal?
when i select a project from the dropdown list, the server that it is associated with is not listed any longer in the list below. so i have to “add” it again and eveything works from then on till i shutdown and restart eclipse.
to be honest, it seems like there might have been once or twice that this has not happened. but the other 20 times i have restarted eclipse i have had to do this.
any suggestions? thanks for you help.
No, it’s certainly not normal for deployments to be forgotten. Can you post all the information we request in the posting guidelines thread at the top of the forum? That will give us enough context to determine what the problem is.
I’m interested in the .log file, see if there are any exceptions writing out the state of the deployment tool. Are you working on a domain machine, or are you logged in as local admin? (aka its your own computer)
ok. here is the situation. i have to work on two different computers. the one at my work place and my home computer. i telecommute some days. so i basically will zip up the workspace directory and take that between the two computers. except for the OS, both computer are setup exactly the same.
What operating system and version are you running?
my workplace computer:
Win2k sp4
my home computer:
WinXP sp1– What Eclipse version and build id are you using?
Version: 2.1.2
Build id: 200311030802
– Was Eclipse freshly installed for MyEclipse?
yes
– Are any other external plugins installed?
yes
– How many plugins in the <eclipse>/plugins directory are like org.eclipse.pde.* ?
6
What MyEclipse version are you using?
2.6.200 (download name 020700RC2)
What JDK version are you using to run Eclipse? (java -version)
j2sdk 1.4.2 (1.4.2-b28)
What JDK version are you using to launch your application server?
j2sdk 1.4.2
What steps did you take that resulted in the issue?
start eclipse, setup deployments, shutdown eclipse, zip workspace, move to other computer, unzip, start eclipse, deployments gone
What application server are you using?
tomcat 5.0.18, 4.1.29mrzeld,
can you post the last 2 “!SESSION——————–” entries from the respective log files of each machine for us and label which one is from which computer? They are in the <eclipse install>\workspace\.metadata\.log file.We had another gentleman a while back that zipped up his workspace for backup reasons, and every time he did it, it corrupted a core MyEclipse configuration file that was just straight XML… we never figured out why but I’m wondering if this is what is happening to you.
@support-rkalla wrote:
I’m interested in the .log file, see if there are any exceptions writing out the state of the deployment tool. Are you working on a domain machine, or are you logged in as local admin? (aka its your own computer)
nope, nothing in the .log file upon initial start up. and i did have the error today when i initally started up eclipse (the deployment list was empty).
i am logged into my local machine (win xp home) as an admin user (but not as administrator). it is just in a local network with one other computer and a linksys router connected to my cable modem.
I’ll ask Scott if we ever figured out why that other gentleman was getting corrupted workspaces and see if that is the same thing occuring here. (Note that this other user tried raring, taring, zipping, arj’ing and just about every other compression routine available, and they all corrupted the file for some reason.)
@support-rkalla wrote:
mrzeld,
can you post the last 2 “!SESSION——————–” entries from the respective log files of each machine for us and label which one is from which computer? They are in the <eclipse install>\workspace\.metadata\.log file.like i said, i zip up the entire workspace directory. so the .log file goes between the two computers also.
below, you can just ignore the error message about that ROOT directory and being unable to delete it. that is winXP and win2k file protection at work. damn MS. at least winXP is a lot better about it than win2k.
oh, also, since i looked at the .log file, i have also fixed the error message about not including “org.jdt.jdtcommons” for one of my other plugins.
just for reference, i was at work yesterday (1/29) and home today (1/30).
.log from home (the first entry below is from yesterday when i started eclipse at work)
!SESSION Jan 29, 2004 11:34:10.468 --------------------------------------------- java.version=1.4.2 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 -install file:C:/progfile/eclipse/ !ENTRY org.eclipse.core.runtime 2 1 Jan 29, 2004 11:34:10.484 !MESSAGE Problems encountered loading the plug-in registry. !SUBENTRY 1 org.eclipse.core.runtime 2 1 Jan 29, 2004 11:34:10.484 !MESSAGE Plug-in "tcpTunnelMonitor" was disabled due to missing or disabled prerequisite plug-in "org.jdt.jdtcommons". !SUBENTRY 1 org.eclipse.core.runtime 2 1 Jan 29, 2004 11:34:10.484 !MESSAGE Plug-in "eclipsetail" was disabled due to missing or disabled prerequisite plug-in "org.jdt.jdtcommons". !SESSION Jan 30, 2004 12:20:19.475 --------------------------------------------- java.version=1.4.2 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 -install file:C:/progfile/eclipse/ !ENTRY org.eclipse.core.runtime 2 1 Jan 30, 2004 12:20:19.475 !MESSAGE Problems encountered loading the plug-in registry. !SUBENTRY 1 org.eclipse.core.runtime 2 1 Jan 30, 2004 12:20:19.475 !MESSAGE Plug-in "tcpTunnelMonitor" was disabled due to missing or disabled prerequisite plug-in "org.jdt.jdtcommons". !SUBENTRY 1 org.eclipse.core.runtime 2 1 Jan 30, 2004 12:20:19.475 !MESSAGE Plug-in "eclipsetail" was disabled due to missing or disabled prerequisite plug-in "org.jdt.jdtcommons". !SESSION Jan 30, 2004 13:00:22.756 --------------------------------------------- java.version=1.4.2 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 -install file:C:/progfile/eclipse/ !ENTRY com.genuitec.eclipse.ast.deploy.core 1 1 Jan 30, 2004 13:00:22.756 !MESSAGE Error building all on webProject !STACK 0 java.io.IOException: Directory C:\progfile\jakarta-tomcat-5.0.18\webapps\ROOT unable to be deleted. at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1130) at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1111) at com.genuitec.eclipse.ast.deploy.core.WebDeployment.resyncAll(Unknown Source) at com.genuitec.eclipse.ast.deploy.core.ModuleDeployment.deployAsExplodedArchive(Unknown Source) at com.genuitec.eclipse.ast.deploy.core.Deployment.deploy(Unknown Source) at com.genuitec.eclipse.ast.deploy.core.ui.wizard.NewDeploymentWizard$1.run(Unknown Source) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101) !ENTRY com.genuitec.eclipse.ast.deploy.core 1 1 Jan 30, 2004 13:00:22.756 !MESSAGE Deploy failed !STACK 0 com.genuitec.eclipse.core.R: Unable to copy deployed directory C:\progfile\eclipse\workspace\ROOT\WebRoot at com.genuitec.eclipse.ast.deploy.core.WebDeployment.resyncAll(Unknown Source) at com.genuitec.eclipse.ast.deploy.core.ModuleDeployment.deployAsExplodedArchive(Unknown Source) at com.genuitec.eclipse.ast.deploy.core.Deployment.deploy(Unknown Source) at com.genuitec.eclipse.ast.deploy.core.ui.wizard.NewDeploymentWizard$1.run(Unknown Source) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101) Caused by: java.io.IOException: Directory C:\progfile\jakarta-tomcat-5.0.18\webapps\ROOT unable to be deleted. at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1130) at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1111) ... 5 more !SESSION Jan 30, 2004 13:09:43.287 --------------------------------------------- java.version=1.4.2 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 -install file:C:/progfile/eclipse/ !ENTRY org.eclipse.core.runtime 2 1 Jan 30, 2004 13:09:43.287 !MESSAGE Problems encountered loading the plug-in registry. !SUBENTRY 1 org.eclipse.core.runtime 2 1 Jan 30, 2004 13:09:43.287 !MESSAGE Plug-in "tcpTunnelMonitor" was disabled due to missing or disabled prerequisite plug-in "org.jdt.jdtcommons". !SUBENTRY 1 org.eclipse.core.runtime 2 1 Jan 30, 2004 13:09:43.287 !MESSAGE Plug-in "eclipsetail" was disabled due to missing or disabled prerequisite plug-in "org.jdt.jdtcommons"..log from work (the first two entries below with times starting at 00:… are from my home computer, i was working late 🙂 )
!SESSION Jan 29, 2004 00:36:32.693 --------------------------------------------- java.version=1.4.2 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 -install file:C:/progfile/eclipse/ !ENTRY com.genuitec.eclipse.ast.deploy.core 1 1 Jan 29, 2004 00:36:32.693 !MESSAGE Error building all on webProject !STACK 0 java.io.IOException: Directory C:\progfile\jakarta-tomcat-5.0.18\webapps\ROOT unable to be deleted. at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1130) at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1111) at com.genuitec.eclipse.ast.deploy.core.WebDeployment.resyncAll(Unknown Source) at com.genuitec.eclipse.ast.deploy.core.ModuleDeployment.deployAsExplodedArchive(Unknown Source) at com.genuitec.eclipse.ast.deploy.core.Deployment.deploy(Unknown Source) at com.genuitec.eclipse.ast.deploy.core.ui.wizard.NewDeploymentWizard$1.run(Unknown Source) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101) !ENTRY com.genuitec.eclipse.ast.deploy.core 1 1 Jan 29, 2004 00:36:32.725 !MESSAGE Deploy failed !STACK 0 com.genuitec.eclipse.core.R: Unable to copy deployed directory C:\progfile\eclipse\workspace\ROOT\WebRoot at com.genuitec.eclipse.ast.deploy.core.WebDeployment.resyncAll(Unknown Source) at com.genuitec.eclipse.ast.deploy.core.ModuleDeployment.deployAsExplodedArchive(Unknown Source) at com.genuitec.eclipse.ast.deploy.core.Deployment.deploy(Unknown Source) at com.genuitec.eclipse.ast.deploy.core.ui.wizard.NewDeploymentWizard$1.run(Unknown Source) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101) Caused by: java.io.IOException: Directory C:\progfile\jakarta-tomcat-5.0.18\webapps\ROOT unable to be deleted. at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1130) at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1111) ... 5 more !SESSION Jan 29, 2004 00:40:03.600 --------------------------------------------- java.version=1.4.2 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 -install file:C:/progfile/eclipse/ !ENTRY com.genuitec.eclipse.ast.deploy.core 1 1 Jan 29, 2004 00:40:03.600 !MESSAGE Error building all on webProject !STACK 0 java.io.IOException: Directory C:\progfile\jakarta-tomcat-5.0.18\webapps\ROOT unable to be deleted. at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1130) at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1111) at com.genuitec.eclipse.ast.deploy.core.WebDeployment.resyncAll(Unknown Source) at com.genuitec.eclipse.ast.deploy.core.ModuleDeployment.deployAsExplodedArchive(Unknown Source) at com.genuitec.eclipse.ast.deploy.core.Deployment.deploy(Unknown Source) at com.genuitec.eclipse.ast.deploy.core.ui.wizard.NewDeploymentWizard$1.run(Unknown Source) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101) !ENTRY com.genuitec.eclipse.ast.deploy.core 1 1 Jan 29, 2004 00:40:03.600 !MESSAGE Deploy failed !STACK 0 com.genuitec.eclipse.core.R: Unable to copy deployed directory C:\progfile\eclipse\workspace\ROOT\WebRoot at com.genuitec.eclipse.ast.deploy.core.WebDeployment.resyncAll(Unknown Source) at com.genuitec.eclipse.ast.deploy.core.ModuleDeployment.deployAsExplodedArchive(Unknown Source) at com.genuitec.eclipse.ast.deploy.core.Deployment.deploy(Unknown Source) at com.genuitec.eclipse.ast.deploy.core.ui.wizard.NewDeploymentWizard$1.run(Unknown Source) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101) Caused by: java.io.IOException: Directory C:\progfile\jakarta-tomcat-5.0.18\webapps\ROOT unable to be deleted. at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1130) at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1111) ... 5 more !SESSION Jan 29, 2004 11:34:10.468 --------------------------------------------- java.version=1.4.2 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 -install file:C:/progfile/eclipse/ !ENTRY org.eclipse.core.runtime 2 1 Jan 29, 2004 11:34:10.484 !MESSAGE Problems encountered loading the plug-in registry. !SUBENTRY 1 org.eclipse.core.runtime 2 1 Jan 29, 2004 11:34:10.484 !MESSAGE Plug-in "tcpTunnelMonitor" was disabled due to missing or disabled prerequisite plug-in "org.jdt.jdtcommons". !SUBENTRY 1 org.eclipse.core.runtime 2 1 Jan 29, 2004 11:34:10.484 !MESSAGE Plug-in "eclipsetail" was disabled due to missing or disabled prerequisite plug-in "org.jdt.jdtcommons".@support-rkalla wrote:
I’ll ask Scott if we ever figured out why that other gentleman was getting corrupted workspaces and see if that is the same thing occuring here. (Note that this other user tried raring, taring, zipping, arj’ing and just about every other compression routine available, and they all corrupted the file for some reason.)
i use winrar and usually make .rar’s. but i have NEVER had that corrupt anything, and i use it quite a lot. which file specifically are you thinking is getting corrupted?
i found the file below that seems to contain the infomation and it rars and unrars just fine…
<eclipse-install-dir>\workspace\.metadata\.plugins\com.genuitec.eclipse.ast.deploy.core\pref_store.inioh, btw, thanks for all the help. i usually do all my jsp editing in a text editor. but recently we starting using cocoon and it does a really damn good job of hiding all the error messages produced from invalid JSP. so i had used eclipse before and decided to give the myeclipse plugin a try. i convinced my boss that we desperately need it so we will be buying it soon. thanks again.
so how hard is it to convert a project we did using lomboz to myeclipse?
I think I may know what’s going on if this is what you’re doing
start eclipse, setup deployments, shutdown eclipse, zip workspace, move to other computer, unzip, start eclipse
For a deployment to be recognized as valid, two things have to occur. First, a valid entry needs to be in your deployment preferences file, which should be the case given these steps. However, the second condition is that the deployment directory that should be created by the deployment must exist. If the deployment directory does not exist under the server, the deployment is immediately discarded as invalid. This second check exists because a user may manually go out to their file system and delete the deployment directory. If that occurs, we need MyEclipse to realize that the deployment no longer exists, even it if remembers having deployed to that location. This will allow the user to then use MyEclipse to deploy the application again, rather than having it report that the deployment still exists after the user deleted it manually. Does that make sense?
So, what I think is happening is when you change machines the deployment path is not being found so your deployments are being discarded. This actually may be a benefit since the exploded deployer only deploys project changes, and only deploys the entire project on first deployment. So, if you made a bunch of changes on one machine and then moved to the other one, all deployments are hopelessly out of date anyway and need a full redeployment.
ahhhh. ok, here it is. Scott, i took what you said and i started playing around. here is what i found.
when i unrar the workspace and start eclipse, eclipse goes and starts compling ALL the jsp’s in my workspace (which is REALLY annoying). then when i select the deployments list, it is empty (doesn’t matter whether or not i deleted the webapps dir’s in tomcat). before starting eclipse i looked in the .ini file (refer to my last post) and it has all the correct information in it. myeclipse seems to ignore this .ini file on the FIRST startup.
so not having chagned anything. i shut down eclipse and restart. the jsp’s aren’t touched this time and the deployment list has all the correct items in it now (if i haven’t deleted the webapp dir’s in tomcat).
if i had deleted the webapp dir’s in tomcat, then the deployment list is empty in eclipse, but the .ini file still contains the entries that it did before.
i can understand what you said about myeclipse’s behaviour. so i guess the only real bug here is that first startup of eclipse and the deployment list being empty even though the dir’s do exist in the tomcat webapp dir.
seems like the deployment popup window should keep its list of deployments that you have setup and enable the redeploy button for the ones that don’t have a webapp dir in tomcat.
to summarize: 1 bug, 1 enhancement request
(looking at it from a user’s point of view) it is not very nice of myeclipse to delete from the list deployments entries that i have taken the time to set up. i am only working with three webapps right now which is sort of a pain to redo. but if i had 10-20 or more webapps then this behaviour could be very annoying (especially since now that i know those deployment definitions are already in the .ini file).
We will look into this matter more closely. I hypothesize that your problems occur because Eclipse (not MyEclipse) believes the workbench has been modified, similar to a makefile. So it goes about rebuilding all files that have been touched. For example in the JDT, build state info is persisted. When the workbench changes in anyway then the JDT’s persisted state is out of date and thus rebuilding begins. While I don’t yet know why the deployer’s pref_store.ini is being reset. I’m assuming the workbench is out of date (you effectively touched every file with the workspace jar/unjar)
@support-michael wrote:
We will look into this matter more closely. I hypothesize that your problems occur because Eclipse (not MyEclipse) believes the workbench has been modified, similar to a makefile. So it goes about rebuilding all files that have been touched. For example in the JDT, build state info is persisted. When the workbench changes in anyway then the JDT’s persisted state is out of date and thus rebuilding begins.
actually, file date/times stay the same. they are preserved through the zip/unzip process. the only things that have different date/times are the directories.
@support-michael wrote:
While I don’t yet know why the deployer’s pref_store.ini is being reset. I’m assuming the workbench is out of date (you effectively touched every file with the workspace jar/unjar)
the pref_store.ini isn’t being reset. it maintains all of it’s data. even when i delete the webapp dirs in tomcat, then start eclipse, and they dont’ show up on the deploy menu in eclipse, the .ini file still contains the info from before when there were webapp dir’s in tomcat. beside, even if i did touch every file in the workbench, why should that mess up the deploy menu?
if you read my previous post, the deploy menu is empty the first time you start eclipse (even though the info is in the .ini file and the webapp dir’s exist in tomcat). then if you dont change anything, shut down, restart… the deploy menu is back to normal. <– “first time you start eclipse” refers to the first time that eclipse is started after unzipping the workspace into the eclipse directory.
