Operation timed out when attempting to contact 127.0.0.1

[schifest]

I have a working GWT 'helloworld' application with a trivial 'login' panel. It runs as expected both in hosted mode and compiled.

Environment seems to be correct

Code: Select all

Environment variables:
   MOZILLA_FIVE_HOME = /usr/lib/firefox-1.5.0.12
   LD_LIBRARY_PATH = /usr/java/jdk1.6.0_05/jre/lib/i386/client:/usr/java/jdk1.6.0_05/jre/lib/i386:/usr/java/jdk1.6.0_05/jre/../lib/i386:/usr/java/jdk1.6.0_05/jre/lib/i386/client:/usr/java/jdk1.6.0_05/jre/lib/i386:/usr/lib/firefox-1.5.0.12
>>>Snippet creating SWT.MOZILLA-style Browser
XULRunner path: /opt/xulrunner-1.9.0.4.en-US/xulrunner-sdk/bin/libxpcom.so
>>>succeeded


When the 'Design' tab is clicked on the visual class (the login panel), a 'Progress information' popup panel comes up with message 'Initializing GWT'
A few seconds later, an alert 'The operation timed out when attempting to contact 127.0.0.1'
After some time, an 'Exception happened' pops up with the following details:

Code: Select all

Plug-in Provider: Instantiations

Plug-in Name: GWT Designer Evaluation

Plug-in ID: com.swtdesigner

Plug-in Version: 5.1.0.200810070819



javax.naming.TimeLimitExceededException: Browser was not initialized during 60000 msec.

    at com.instantiations.designer.gwt.linux.BrowserShellLinux.setUrl(BrowserShellLinux.java:129)

    at com.instantiations.designer.gwt.hosted.odf.HostedModeSupport.startup(HostedModeSupport.java:120)

    at com.swtdesigner.gwt.model.widgets.support.GWTState$1.run(GWTState.java:155)

    at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:458)

    at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:366)

    at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)

...
Designer Configuration Details:



Product: GWT Designer Evaluation

Version: 5.1.0.200810070819

Expected: Eclipse 3.4

Actual: Eclipse 3.4.0.v20080512

Actual Eclipse Build Name:

Actual Eclipse Build ID: M20080911-1700

IDE Actual Name: Eclipse

IDE Actual Version: 3.3.101.v200809111700

IDE Actual NL: en_US

Activation Key: GWTDesignerEval-BE0SG-SM0XX-Q57V1

Physical Address: 00-14-22-C6-C2-F4, HardwareAddress[00-13-CE-E2-D4-5D], HardwareAddress[00-FF-A3-7E-77-21]

Code Gen: Flat Mode, Use Existing, First Assignment, Make Final

Events: Anonymous Class

GWT Home: /opt/gwt-linux-1.5.3

Platform Product: Eclipse
Platform Version: 3.3.101.v200809111700

OS Name: Linux
OS Architecture: i386
OS Version: 2.6.22.14-72.fc6



Any ideas of what's wrong with my environment/set-up will be greately appreciated

Thx.
Esteban

[Eric Clayberg]

Looks like something might be interfereing with localhost communications or JavaScript.

Make sure that anything that might interfere with local communications is disabled (like any proxy configured in your browser settings or any overly aggressive anti-virus or firewall software). If you have a proxy server configured in your browser Settings, make sure to set the browser to bypass the proxy server for local addresses. As a test, you can try disabling the proxy / firewall / anti-virus software completely.

I would also suggest using the latest GWT Designer build rather than the older build (from two months ago) you are using now.

[schifest]

Thanks Eric,
I will (as you suggest) download the latest version and let you know what happens.
In the original test that failed as described, no proxies were configured on the browser, and there's no firewall in localhost (the only one there is, is in another computer that acts as gateway to the public internet).
Would the application itself work if there was any problem with proxies or firewalls ?
Thx.
-E

[Alexander.Mitin]

Do you have any Firefox plugins/extensions installed (such as Firebug)? Try to remove them and remove all firefox profiles (usually located in your home dir, something like '.firefox' or '.mozilla')
If you run the eclipse from the console, can you see the 'window = xxxxxxxx' message at the console while switching to the Design View?

[schifest]

I've downloaded and re-installed the latest version using the linux full installer for Eclipse 3.4.
Interestingly, the installer does not notice if eclipse is running or not (the warning does not appear as it used to). It was however brought down and restarted.
The 4 links are in the 'dropins' directory

com.instantiations.css_v200812111749.link
com.instantiations.designer_v200812111749.link
com.instantiations.shared_v200812111749.link
com.swtdesigner.gwt_v200812111749.link

Upon restarting eclipse, the plugins appear as installed in the 'Installed Software' of the 'Software updates and add-ons' panel in Eclipse
Nevertheless, when opening up the 'Window / Preferences' popup panel, the 'Designer' item has disappeared.
Also, the run configurations for gwt have disappeared as well.

Have I missed something ?
Any ideas ?

[Eric Clayberg]

Upon restarting eclipse, the plugins appear as installed in the 'Installed Software' of the 'Software updates and add-ons' panel in Eclipse
Nevertheless, when opening up the 'Window / Preferences' popup panel, the 'Designer' item has disappeared.
Also, the run configurations for gwt have disappeared as well.
Have I missed something ?

I think you're running into a p2 bug in Eclipse 3.4 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=232094).

You can try restoring your configuration\org.eclipse.equinox.simpleconfigurator and \p2 directories from the original eclipse zip file or start with a fresh install of eclipse.

[schifest]

Installed a fresh Eclipse, updated 'standard' plugins and brought it down
Installed latest stable release of WTP (wtp-sdk-S-3.1M3-20081107233958)
Ran the linux 'full installer'
restarted eclipse

Alexander: yes, a line is output in the console

window = 212789240

Seems to be working now, but when asked to activate the product (is that because a fresh eclipse was installed ?), and upon entering the evaluation activation code you had kindly supplied a few days ago (on Nov 26), the designer vanishes.
My guess is that it's not accepting that activation code.

Almost there...
What next ?

[Eric Clayberg]

when asked to activate the product (is that because a fresh eclipse was installed ?), and upon entering the evaluation activation code you had kindly supplied a few days ago (on Nov 26), the designer vanishes.

The initial eval period is 14 days, so it would have expired today.

You can request an eval extension from our Sales department at sales@instantiations.com.

[schifest]

Hello gentlemen,

Sales dpt. did not reply to our request of an extension to the evaluation period, so we purchased the GWT Designer (perpetual) with one year support.

Now that we purchased the product, Is there any other support procedure besides the forum ? If so, what is the appropriate way to ask for help ?

Still getting "The operation timed out when attempting to contact 127.0.0.1."
Firefox only has the 'libflashplayer.so' plugin (in ~/.mozilla/plugins)
No proxy configured in firefox, nor is there any firewall in this linux box.

Her's the console output:

Code: Select all

window = 173127768
org.apache.commons.lang.exception.NestableError: com.swtdesigner.properties.PropertyException: java.lang.reflect.InvocationTargetException
        at com.swtdesigner.model.parser.factory.JavaInfoFactory.create(JavaInfoFactory.java:120)
        at com.swtdesigner.model.parser.factory.JavaInfoFactory.create(JavaInfoFactory.java:97)
        at com.swtdesigner.model.parser.factory.JavaInfoFactory.create(JavaInfoFactory.java:90)
        at com.swtdesigner.model.parser.JavaInfoParser$ParserVisitor.endVisit(JavaInfoParser.java:1450)
        at org.eclipse.jdt.core.dom.ClassInstanceCreation.accept0(ClassInstanceCreation.java:337)
        at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2478)
        at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2525)
        at org.eclipse.jdt.core.dom.VariableDeclarationFragment.accept0(VariableDeclarationFragment.java:225)
        at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2478)
        at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2548)
        at org.eclipse.jdt.core.dom.FieldDeclaration.accept0(FieldDeclaration.java:287)
        at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2478)
        at com.swtdesigner.model.parser.JavaInfoParser$ParserVisitor.visit(JavaInfoParser.java:2746)
        at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:467)
        at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2478)
        at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2548)
        at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:214)
        at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2478)
        at com.swtdesigner.model.parser.JavaInfoParser.parse(JavaInfoParser.java:323)
        at com.swtdesigner.gef.DesignerEditor.parseCompilationUnit(DesignerEditor.java:1201)
        at com.swtdesigner.gef.DesignerEditor$18.execute(DesignerEditor.java:1126)
        at com.swtdesigner.model.swing.properties.custom.DesignTimeHelper.execute(DesignTimeHelper.java:54)
        at com.swtdesigner.gef.DesignerEditor.handleActivate(DesignerEditor.java:1120)
        at com.swtdesigner.gef.DesignerEditor.handleActivate(DesignerEditor.java:1111)
        at com.swtdesigner.editors.MultiPageEditor.showDesignEditor(MultiPageEditor.java:392)
        at com.swtdesigner.editors.MultiPageEditor$2.widgetSelected(MultiPageEditor.java:178)
        at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1182)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1167)
        at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1007)
        at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3242)
        at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:2017)
        at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:320)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)
        at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033)
        at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
        at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
        at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
        at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
        at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
        at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
        at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
        at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Caused by: com.swtdesigner.properties.PropertyException: java.lang.reflect.InvocationTargetException
        at com.swtdesigner.gwt.model.GWTJavaInfoFactory.create(GWTJavaInfoFactory.java:171)
        at com.swtdesigner.model.parser.factory.JavaInfoFactory.create(JavaInfoFactory.java:114)
        ... 58 more
Caused by: java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
        at com.swtdesigner.gwt.model.GWTJavaInfoFactory.create(GWTJavaInfoFactory.java:163)
        ... 59 more
Caused by: org.apache.commons.lang.exception.NestableError: org.apache.commons.lang.exception.NestableError: java.lang.reflect.InvocationTargetException
        at com.swtdesigner.gwt.model.widgets.UIObjectInfo.classByName(UIObjectInfo.java:193)
        at com.swtdesigner.gwt.model.widgets.UIObjectInfo.<init>(UIObjectInfo.java:68)
        at com.swtdesigner.gwt.model.widgets.WidgetInfo.<init>(WidgetInfo.java:56)
        at com.swtdesigner.gwt.model.widgets.FocusWidgetInfo.<init>(FocusWidgetInfo.java:17)
        at com.swtdesigner.gwt.model.widgets.text.TextBoxBaseInfo.<init>(TextBoxBaseInfo.java:21)
        at com.swtdesigner.gwt.model.widgets.text.TextBoxInfo.<init>(TextBoxInfo.java:17)
        ... 64 more
Caused by: org.apache.commons.lang.exception.NestableError: java.lang.reflect.InvocationTargetException
        at com.swtdesigner.gwt.model.widgets.UIObjectInfo.getState(UIObjectInfo.java:436)
        at com.swtdesigner.gwt.model.widgets.UIObjectInfo.classByName(UIObjectInfo.java:191)
        ... 69 more
Caused by: java.lang.reflect.InvocationTargetException
        at com.swtdesigner.gwt.model.widgets.support.GWTState$1.run(GWTState.java:174)
        at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:458)
        at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:366)
        at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
        at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:275)
        at org.eclipse.ui.internal.progress.ProgressManager.run(ProgressManager.java:1191)
        at com.swtdesigner.gwt.model.widgets.support.GWTState.<init>(GWTState.java:185)
        at com.swtdesigner.gwt.model.widgets.support.GWTState.createState(GWTState.java:1875)
        at com.swtdesigner.gwt.model.widgets.UIObjectInfo.getState(UIObjectInfo.java:429)
        ... 70 more
Caused by: javax.naming.TimeLimitExceededException: While accessing http://127.0.0.1:46084/0/__start.html, browser was not initialized during 60000 msec.
        at com.instantiations.designer.gwt.linux.BrowserShellLinux.setUrl(BrowserShellLinux.java:129)
        at com.instantiations.designer.gwt.hosted.odf.HostedModeSupport.startup(HostedModeSupport.java:120)
        at com.swtdesigner.gwt.model.widgets.support.GWTState$1.run(GWTState.java:164)
        ... 78 more


Environment variables seem to be OK, and creating a mozilla style browser with a trivial snippet works fine

Code: Select all

public class Runner
{
   static String[] __envVars = {"MOZILLA_FIVE_HOME","LD_LIBRARY_PATH"};
   
       public static void main(String[] args)
       {
          System.out.format("Environment variables:\n");
          for (String s:__envVars)
             System.out.format("\t%s = %s\n",s,System.getenv().get(s));
          
           Device.DEBUG = true;
           Display display = new Display();
           Shell shell = new Shell(display);
           System.out.println(">>>Snippet creating SWT.MOZILLA-style Browser");
           try
           {
               new Browser(shell, SWT.MOZILLA);
               System.out.println(">>>succeeded");
           }
           catch (Error e)
           { e.printStackTrace(); }
           display.dispose();
       }
}


Here's the output

Environment variables:
MOZILLA_FIVE_HOME = /usr/lib/firefox-1.5.0.12
LD_LIBRARY_PATH = /usr/java/jdk1.6.0_05/jre/lib/i386/client:/usr/java/jdk1.6.0_05/jre/lib/i386:/usr/java/jdk1.6.0_05/jre/../lib/i386:/usr/java/jdk1.6.0_05/jre/lib/i386/client:/usr/java/jdk1.6.0_05/jre/lib/i386:/usr/lib/firefox-1.5.0.12:/usr/lib/firefox-1.5.0.12
>>>Snippet creating SWT.MOZILLA-style Browser
XULRunner path: /opt/xulrunner-1.9.0.4.en-US/xulrunner-sdk/bin/libxpcom.so
>>>succeeded

[Alexander.Mitin]

We still can't reproduce the error on our side, so we made some diagnostic checks in latest stable build.
Download the latest stable build, install it into new eclipse and run it using console against new workspace. You should see 'window = xxxx' and 'Browser ready' messages.
Also try to increase the memory used by the eclipse, ex. eclipse -vmargs -XX:MaxPermSize=128m -Xms384m -Xmx384m.

UPD. Are you able to run any GWT sample?

[schifest]

Hello Alexander,

"...UPD. Are you able to run any GWT sample?..."
yes, interestingly enough a trivial GWT application works, but GWT designer apparently still has problems.

Following your suggestion, here's what has been done
1) fresh eclipse
2) install latest GWT designer build (2008.12.26)
3) fresh workspace
4) File->new->Other->Designer->GWT->GWT Java project
5) File->new->Other->Designer->GWT->DialogBox (LoginDialog.java)
6) When class appears in IDE, click on 'Design' tab

Here's the screenshot



After the timeout expires, a stacktrace shows in the console

Code: Select all

[schifest@delllaptop ~]$ /opt/eclipse/eclipse -vmargs -XX:MaxPermSize=128m -Xms384m -Xmx384m
window = 191545496
org.apache.commons.lang.exception.NestableError: org.apache.commons.lang.exception.NestableError: java.lang.reflect.InvocationTargetException
        at com.swtdesigner.gwt.model.widgets.UIObjectInfo.classByName(UIObjectInfo.java:193)
        at com.swtdesigner.gwt.model.widgets.UIObjectInfo.<init>(UIObjectInfo.java:68)
        at com.swtdesigner.gwt.model.widgets.WidgetInfo.<init>(WidgetInfo.java:56)
        at com.swtdesigner.gwt.model.widgets.panel.AbstractContainerInfo.<init>(AbstractContainerInfo.java:37)
        at com.swtdesigner.gwt.model.widgets.panel.PanelInfo.<init>(PanelInfo.java:25)
        at com.swtdesigner.gwt.model.widgets.panel.SimplePanelInfo.<init>(SimplePanelInfo.java:35)
        at com.swtdesigner.gwt.model.widgets.panel.PopupPanelInfo.<init>(PopupPanelInfo.java:39)
        at com.swtdesigner.gwt.model.widgets.panel.DialogBoxInfo.<init>(DialogBoxInfo.java:20)
        at com.swtdesigner.gwt.model.GWTJavaInfoFactory.create(GWTJavaInfoFactory.java:214)
        at com.swtdesigner.model.parser.JavaInfoParser$ParserVisitor.visit(JavaInfoParser.java:2763)
        at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:467)
        at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2478)
        at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2548)
        at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:214)
        at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2478)
        at com.swtdesigner.model.parser.JavaInfoParser.parse(JavaInfoParser.java:323)
        at com.swtdesigner.gef.DesignerEditor.parseCompilationUnit(DesignerEditor.java:1201)
        at com.swtdesigner.gef.DesignerEditor$18.execute(DesignerEditor.java:1126)
        at com.swtdesigner.model.swing.properties.custom.DesignTimeHelper.execute(DesignTimeHelper.java:54)
        at com.swtdesigner.gef.DesignerEditor.handleActivate(DesignerEditor.java:1120)
        at com.swtdesigner.gef.DesignerEditor.handleActivate(DesignerEditor.java:1111)
        at com.swtdesigner.editors.MultiPageEditor.showDesignEditor(MultiPageEditor.java:392)
        at com.swtdesigner.editors.MultiPageEditor$2.widgetSelected(MultiPageEditor.java:178)
        at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1182)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1167)
        at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1007)
        at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3242)
        at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:2017)
        at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:320)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)
        at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033)
        at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
        at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
        at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
        at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
        at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
        at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
        at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
        at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Caused by: org.apache.commons.lang.exception.NestableError: java.lang.reflect.InvocationTargetException
        at com.swtdesigner.gwt.model.widgets.UIObjectInfo.getState(UIObjectInfo.java:436)
        at com.swtdesigner.gwt.model.widgets.UIObjectInfo.classByName(UIObjectInfo.java:191)
        ... 55 more
Caused by: java.lang.reflect.InvocationTargetException
        at com.swtdesigner.gwt.model.widgets.support.GWTState$1.run(GWTState.java:174)
        at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:458)
        at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:366)
        at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
        at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:275)
        at org.eclipse.ui.internal.progress.ProgressManager.run(ProgressManager.java:1191)
        at com.swtdesigner.gwt.model.widgets.support.GWTState.<init>(GWTState.java:185)
        at com.swtdesigner.gwt.model.widgets.support.GWTState.createState(GWTState.java:1875)
        at com.swtdesigner.gwt.model.widgets.UIObjectInfo.getState(UIObjectInfo.java:429)
        ... 56 more
Caused by: javax.naming.TimeLimitExceededException: While accessing http://127.0.0.1:36447/0/__start.html, browser was not initialized during 60000 msec.
        at com.instantiations.designer.gwt.linux.BrowserShellLinux.setUrl(BrowserShellLinux.java:129)
        at com.instantiations.designer.gwt.hosted.odf.HostedModeSupport.startup(HostedModeSupport.java:120)
        at com.swtdesigner.gwt.model.widgets.support.GWTState$1.run(GWTState.java:164)
        ... 64 more


And a new popup appears in eclipse

[Alexander.Mitin]

Since the 'Browser ready' message is absent it sounds like that something really prevents JavaScript from running. What if try to delete mozilla's profile, so it will starts with default one? Usually it resides in ~/.mozilla directory.

[schifest]

Hello Alexander, and thanks for your help.

1) The ~/.mozilla directory was deleted, and eclipse restarted.
Exactly the same behaviour was observed.
2) The "helloworld" GWT application which I had been playing around with, continues to work without problems, both in hosted and compiled modes.

This makes me think that the problem is perhaps not just the mozilla browser configuration, but some kind of weird combination of factors that might include both the browser configuration, AND the assumptions GWT designer relies on.

I would be happy to lend a hand to find the causes of this scenario, but lack the basic knowledge and instruments to do so. At the same time, I'm assuming you and others in your organization are experts both in the knowledge of how a browser works, Javascript, Ajax, and the way GWT designer itself works, so let me just throw some (probably unrelated) loose facts that have occurred during this frustrating experience of trying to make the GWT designer plugin work in my environment.

a) the popup "...The operation timed out when attempting to contact 127.0.0.1. " has been appearing since day one when clicking the 'Design' tab that GWT designer offers. None of the suggestions made by Instantiations and followed by us down here, have changed that.
b) when testing the evaluation of your 'SWT designer' the 'Design' tab worked without problems. Do these products share a basic common toolset ? Unfortunately not much can be inferred in a 4 day product trial period
c) I have never in the past had to deal with this "... operation timed out when attempting to contact 127.0.0.1. ", neither in my Eclipse environment, nor while playing around with the WTP sdk, nor in any other circumstance
d) inclined to think the problem is not javascript or ajax or mozilla, as never had a problem with other GWT applications we had been working on, that do not rely on the GWT designer. Nevertheless, I reckon you guys as the experts

The full stacktrace has been included in previous posts. Can't anything be inferred from it ? Can more 'debug' output be added to help you figure out what's going on ? Can you think of a simple code snippet that can help pin point what the problem is with my environment ? (such as environment variables, mozilla configuration, library versions, etc )

You know that when it takes too long to set up the initial environment with any software product (especially development tools), one is inclined to look at alternate solutions.
I still believe that GWT designer is the product we should be using, but even after paying for the perpetual license and one year support, still won't be able to get it working without your help.
We will very much appreciate your active participation until we find out what the heck is going on.

Thanks.

Esteban

[Eric Clayberg]

At this point we have almost completely exhausted any suggestions that we have. About the only other thing we can suggest is trying it with a much newer version of Linux.

You appear to be using a FedoraCore 6 based system which is more than two years old a this point. We just tried it with FedoraCore 10, and it worked immediately with no changes required. We have also tried it with a number of other current Linux distrubutions, and it works fine.

It may be that we are somehow relying on a bug fix or behavior of some sort in later versions of Linux, but there is really no way for us to figure out what that might be. With the large number of incompatible Linux distributions out there, the only thing we are going to try and do is test on and support the most recent releases of the top 3-4 distributions. At the moment, we have not had any problems with the most recent releases of FedoraCore, Ubuntu, RedHat and SuSE.

[schifest]

You might be right Eric. Your guess makes sense, especially if you tried it and it works right out of the bat.
I will update the Fedora version and let you know how that works out.
Thank you very much for your help.

Esteban