[markburrett]

Hi,

I have suddenly started experiencing problems deploying my web app (J2EE 1.4 with Struts 1.2.9) into Tomcat (4.1.31) using MyEclipse 4.1.1 GA.

Normally, whenever I save a change to a JSP, it deploys automatically into the correct location in the Tomcat webapps directory (the app is configured as an exploded deployment.)

This worked fine for the last however-many months, but suddenly this is not happening. Not only do the JSP’s not deploy automatically any more (since 3 days ago), even if I stop Tomcat, and go ‘Project’ -> ‘Clean’ then restart Tomcat, any recent changes still do not show up.

I have noticed that when I modify a JSP and check the properties of the file in the working directory (either in MyEclipse or Windows explorer) the ‘last modified’ attribute is not being updated any more. All the JSP’s are showing ‘June 16th 2006’, which is actually when they were last deploying properly. If I edit the JSP in another editor, the ‘last modified date’ is updated in MyEclipse when the file is reloaded, but it still does not deploy, even if I do a ‘Project’ -> ‘Clean’.

Config:

*** Date: Mon Jun 19 17:27:52 CEST 2006

*** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_06

*** MyEclipse details:
MyEclipse Enterprise Workbench

Version: 4.1.1 GA
Build id: 20060309-4.1.1-GA

*** Eclipse details:
Eclipse SDK

Version: 3.1.2
Build id: M20060118-1600

Eclipse Platform

Version: 3.1.2
Build id: M20060118-1600

Eclipse Java Development Tools

Version: 3.1.2
Build id: M20060118-1600

Eclipse Project SDK

Version: 3.1.2
Build id: M20060118-1600

Eclipse Graphical Editing Framework

Version: 3.1
Build id: 200509301327

Eclipse RCP

Version: 3.1.2
Build id: M20060118-1600

Eclipse Plug-in Development Environment

Version: 3.1.2
Build id: M20060118-1600

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
D:\eclipse\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
b90_2c
-vm
C:\WINDOWS\system32\javaw.exe

From Error log:

!ENTRY com.genuitec.eclipse.wdt.jsp.debug 1 1 2006-06-19 17:26:03.822
!MESSAGE
19-Jun-2006 17:26:03 com.genuitec.eclipse.wdt.jsp.jasper.compiler.Compiler ?
SEVERE: Javac exception
Error running javac.exe compiler
at org.apache.tools.ant.taskdefs.compilers.DefaultCompilerAdapter.executeExternalCompile(DefaultCompilerAdapter.java:473)
at org.apache.tools.ant.taskdefs.compilers.JavacExternal.execute(JavacExternal.java:47)
at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:931)
at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:757)
at com.genuitec.eclipse.wdt.jsp.jasper.compiler.Compiler.?(Unknown Source)
at com.genuitec.eclipse.wdt.jsp.jasper.compiler.Compiler.compile(Unknown Source)
at com.genuitec.eclipse.wdt.jsp.jasper.compiler.Compiler.compile(Unknown Source)
at com.genuitec.eclipse.wdt.jsp.jasper.driver.MyEclipseJspC.?(Unknown Source)
at com.genuitec.eclipse.wdt.jsp.jasper.driver.MyEclipseJspC.parse(Unknown Source)
at com.genuitec.eclipse.wdt.jsp.validation.JSPValidator.validate(Unknown Source)
at com.genuitec.eclipse.wdt.jsp.validation.ValidateAction$1.run(Unknown Source)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1721)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1741)
at com.genuitec.eclipse.wdt.jsp.validation.ValidateAction.validate(Unknown Source)
at com.genuitec.eclipse.wdt.jsp.validation.ValidateAction.run(Unknown Source)
at com.genuitec.eclipse.wdt.jsp.validation.Validator.validate(Unknown Source)
at com.genuitec.eclipse.wdt.jsp.validation.Validator.validateIfNeeded(Unknown Source)
at com.genuitec.eclipse.wdt.jsp.validation.Validator.validate(Unknown Source)
at com.ibm.etools.validation.ValidatorLauncher.start(ValidatorLauncher.java:58)
at com.ibm.etools.validate.ValidationOperation.launchValidator(ValidationOperation.java:1275)
at com.ibm.etools.validate.ValidationOperation.internalValidate(ValidationOperation.java:1099)
at com.ibm.etools.validate.ValidationOperation.validate(ValidationOperation.java:1014)
at com.ibm.etools.validate.ValidationOperation.run(ValidationOperation.java:731)
at com.ibm.etools.validate.ValidationBuilder.performFullBuild(ValidationBuilder.java:204)
at com.ibm.etools.validate.ValidationBuilder.performFullBuild(ValidationBuilder.java:197)
at com.ibm.etools.validate.ValidationBuilder.build(ValidationBuilder.java:141)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:593)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044)
at org.eclipse.core.runtime.Platform.run(Platform.java:783)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:168)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:202)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:231)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044)
at org.eclipse.core.runtime.Platform.run(Platform.java:783)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:234)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:253)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:282)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:139)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:200)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)

<SNIP>

[Riyad Kalla]

I have suddenly started experiencing problems deploying my web app (J2EE 1.4 with Struts 1.2.9) into Tomcat (4.1.31) using MyEclipse 4.1.1 GA.

Tomcat 4 cannot accept a J2EE 1.4 project (JSP 2.0 and Web 2.4 specs, Tomcat 4 only supports JSP 1.2 and Web 2.3 specs respectively)

I have noticed that when I modify a JSP and check the properties of the file in the working directory (either in MyEclipse or Windows explorer) the ‘last modified’ attribute is not being updated any more. All the JSP’s are showing ‘June 16th 2006’, which is actually when they were last deploying properly. If I edit the JSP in another editor, the ‘last modified date’ is updated in MyEclipse when the file is reloaded, but it still does not deploy, even if I do a ‘Project’ -> ‘Clean’.

Have you tried removing and readding the deployment while the app server is stopped?

Also with regard to all the exceptions in the log file, you need to add your JDK’s /bin directory to your system path and restart MyEclipse, it is trying to execute the javac executable to validate your JSPs and cannot find it. This is changed in MyEclipse 5.0.

[markburrett]

Thanks for the quick response.

I have upgraded to Tomcat 5.5.17 and am still experiencing similar problems.
I also tried to remove and re-add the deployment with Tomcat stopped, as suggested, but to no avail.

When I modify and save a JSP within MyEclipse, it is still not automatically deployed.
As in the original post, the ‘last modified’ date for all JSPs is still stuck on June 16th, which is when my JSPs were last deploying properly.

Since switching to Tomcat 5, I have noticed one change in the deployment behaviour: if I stop Tomcat, manually redeploy and then
restart Tomcat, the JSP is deployed ok. With Tomcat 4, even this had stopped working.

Note: as a test I created a simple project containing just a text file and have found that the ‘last modified date’ does not update
when I edit the file in MyEclipse.

Note also that I made the suggested change to the system path and am not seeing those exceptions any more.

Thanks in advance.

[Riyad Kalla]

When I modify and save a JSP within MyEclipse, it is still not automatically deployed.
As in the original post, the ‘last modified’ date for all JSPs is still stuck on June 16th, which is when my JSPs were last deploying properly.

Just a quick observation… you said that you had your original deployment in Tomcat 4 from June 16th, and you just said you installed Tomcat 5.5.17 and still have the same June 16th deployment date… which doesn’t make sense assuming you had to create a new deployment for your new Tomcat 5.5 install, which makes me think you are actually looking at the wrong directory and possibly even running the wrong instancen of Tomcat. I would also point out in your original post you mention your project working for “months” even though it was a J2EE 1.4 project on Tomcat 4, which wouldn’t have worked at all. So either you are looking at the wrong install of TOmcat, or you are missing out on some big details here about your setup for me. My guess is something is getting confused in the process here.

You know, the deployment is tied into the build cycle. So let’s just make sure automatic building is still turned on. Go to Window > Preferences > General > Workspace, and make sure “Build automatically” is checked.

Also try this, remove your deployment to Tomcat 5, right click on the root of your project, do a Refresh. Then recreate your project deployment as exploded. Now wait a few minutes, now open a JSP, change it and save it, go check the timestamp on the deployed file by opening the deployment tool and selecting your deployment hitting “Browse”, did the timestamp update?

[markburrett]

OK… Everything is working normally now.

The only thing I did differently since my last post was to ‘refresh’ at the project root before recreating the deployment, as suggested.

However… interesting footnote:

I have a very sneaking suspicion something else was responsible… Friday 16 2006 (the date when all my timestamps got stuck and my problems began) was the same day I installed a very flaky release of ZoneAlarm (v. 65 714 000). Many reports on the internet of ZoneAlarm suddenly interacting haphazardly with some 3rd party software, especially with regards to Windows timestamps… Today I installed the fix (v. 6.5.722.000) and lo, my timestamps are updating and JSPs deploying perfectly. Coincidence? Well, considering I didn’t change any settings today and everything suddenly works fine once again, I doubt it.

From http://www.warp2search.net/modules.php?name=News&file=article&sid=28834
“The latest version of the ZoneAlarm Internet Security Suite 6.5 is having massive problems with the AntiSpyware component not updating properly and the Date Modified Attribute not beeing saved in Windows Explorer. Apparently the ZoneLabs developers felt it was ok to release BETA software as an Official Release. Either that or the person in charge of Quality Control should be fired. Enough is Enough”

See also http://news.zdnet.co.uk/software/applications/0,39020384,39276454,00.htm
etc. etc.

Thanks for your help, and sorry for the hassle when it wasn’t your fault.

[markburrett]

http://forum.zonelabs.org/zonelabs/board/message?board.id=inst&message.id=50617

Any more needs to be said?

[Riyad Kalla]

Oh my gosh what a pain. Thanks for following up with so much detail, atleast this will be helpful to the other folks running into the same problem.

[Author]

Posts