[Milind Rao]

I followed the Struts tutorial at http://www.myeclipseide.com/images/tutorials/StrutsTutorial.htm
and when I click on the Finish dialog of the Create Form and Action wizard, eclipse just hangs. I have to kill it from Task Manager.

The only change I made was that I changed the base from com.yourcompany.struts to myeclipse.strutstutorial. Another person posted a similar problem (except he got an exception). The resolution to that was to use a UseCase name. I do have that specified as “login”.

Machine Config
Windows XP+SP1
Eclipse 3.0
MyEclipse 3.8 Beta 1

[Riyad Kalla]

Is your processor pegged when you kill the process? There is currently an open bug against Eclipse (that Scott posted on in another forum) where it will completely lock up. As far as the Struts tutorials locking up Eclipse, they are used quite often and every day here and we haven’t seen any behavior like this.

I also just tried your use case you gave (with the same package and everything) and it worked as expected. Can you check your log file for any exceptions for us.

[Milind Rao]

The CPU is not pegged. This is the exception from the log file.

!ENTRY XMLBuilderPlugin 4 0 Jul 12, 2004 13:02:48.813
!MESSAGE Stopping after fatal error: Element type “action” must be followed by either attribute specifications, “>” or “/>”.
!STACK 0
org.xml.sax.SAXException: Stopping after fatal error: Element type “action” must be followed by either attribute specifications, “>” or “/>”.
at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1228)
at org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:579)
at org.apache.xerces.framework.XMLDocumentScanner.abortMarkup(XMLDocumentScanner.java:628)
at org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanner.java:1800)
at org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java:1182)
at org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:381)
at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1081)
at com.genuitec.eclipse.j2eedt.core.builder.XMLResourceParser.parse(Unknown Source)
at com.genuitec.eclipse.j2eedt.core.builder.XMLResourceParser.parse(Unknown Source)
at com.genuitec.eclipse.j2eedt.core.builder.XMLValidationChecker.checkFile(Unknown Source)
at com.genuitec.eclipse.j2eedt.core.builder.DeploymentDescriptorValidator.�(Unknown Source)
at com.genuitec.eclipse.j2eedt.core.builder.DeploymentDescriptorValidator.access$0(Unknown Source)
at com.genuitec.eclipse.j2eedt.core.builder.DeploymentDescriptorValidator$A.visit(Unknown Source)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:68)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49)
at com.genuitec.eclipse.j2eedt.core.builder.DeploymentDescriptorValidator.�(Unknown Source)
at com.genuitec.eclipse.j2eedt.core.builder.DeploymentDescriptorValidator.build(Unknown Source)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:564)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:615)
at org.eclipse.core.runtime.Platform.run(Platform.java:747)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:157)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:249)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:202)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:229)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:615)
at org.eclipse.core.runtime.Platform.run(Platform.java:747)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:232)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:268)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:297)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:155)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:212)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)

[Milind Rao]

I deleted the log file and retried. This time the log file is empty although I still end up with the hang. So I think that the log was probably generated after I re-started eclipse and built the project again.

When it hangs, the status ‘bar’ in the wizard says “Searching… Creating type LoginAction (Xslt generator for Eclipse JDT) . After I kill Eclipse and restart, I see the following in the project

1. The LoginAction class gets created, but doesn’t have the imports correctly declared so has errors which are fixed with a Ctrl-Shift-O.
2. The LoginForm class is created without any errors.
3. The form directory is not created (and hence there is no /form/login.jsp either)
4. There is no change to the struts-config.xml file. ie. There is no action element in the action-mappings element.

I have screen shots of the form and action pages of the wizard. Is there a way to attach screen shots in the message? Else I could mail it to you if you would find it useful.

[Riyad Kalla]

Let me check with the dev team about this briefly to see if we can figure out what the problem may or maynot be. Then we could probably ask you for a few reosurces all at once and have them email them to us.

[Scott Anderson]

Actually, we did see this is very isolated instances during the development of 3.8 Beta 2, although we did not think the issue existed in Beta 1. However, it might have just been harder to trigger. The problem is related to a race condition that is created in the JDT class cache during the execution of the wizard. We diagnosed it during Beta 2 development and although the issue appears to be a bug in the JDT, we worked around it in Beta 2. I believe this problem will be resolved with an upgrade, once Beta 2 is available later tonight. Sorry for the inconvenience, but thanks for reporting it.

[Milind Rao]

I’m afraid it’s still broken. Beta 2 on a different machine in a fresh workspace still exhibits the same problem.

[Riyad Kalla]

Oyvey… are you sure you are using Beta 2? (Help > About > Click the MyEclipse button). I’ll notify the devs, I’m sorry again that this is giving you so much trouble…

[Scott Anderson]

Also, please ensure you’re using Eclipse 3.0 Final, and not one of the preceeding RC or milestone builds.

[Milind Rao]

I’m using Eclipse 3.0.0 (pretty much never user a milestone build) and Genuitec 3.7.200
BTW. MyEclipse.AboutMyEclipse doesn’t display the version number. I got the above version number from the from the plugin’s list.

[Riyad Kalla]

os2baba, what is the build date for your install of Eclipse? All through development it was called 3.0.0, so that doesn’t tell us much.

[Milind Rao]

Oh. I see. Build id: 200406251208

Regards
Milind

[Riyad Kalla]

Milind,
I talked with one of the developers last night about it this and as it turns out there is a bug in the JDT (From Eclipse) that given certain conditions can cause the race condition and lockup like Scott explained. The thing that had us stumped was how you are able to encounter it over and over again without fail, while our developers had to go out of their way to create the condition in order to see the lockup. We do have a future plan for working around this, but it won’t be ready for 3.8 GA (as its a larger scale change), I honestly don’t know where to direct you on this one. Let me check with anyone to see if there is any band-aid we can throw on this for you until we get our workaround in place.

[Milind Rao]

Thanks. I can’t really proceed with a Struts app (without manually creating the files) can I?

[Riyad Kalla]

Probably not if the Wizards keep locking the platform up on you. If its any consolation I don’t use the Wizards and get along just fine, I’m a sucker for good autocomplete myself.

[Author]

Posts