cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
search
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0
Upvote

Extensions don't work

ToeJam
Explorer ,
Mar 02, 2010 Mar 02, 2010

Copy link to clipboard

Copied

I can not run any extensions, I have tried a clean install and still no luck, any ideas?

3.5 JEE version, cfbuilder beta3, winxp pro

org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: No more handles [Could not detect registered XULRunner to use])

at org.eclipse.swt.SWT.error(SWT.java:3884)

at org.eclipse.swt.SWT.error(SWT.java:3799)

at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137)

at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3885)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3506)

at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)

at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)

at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)

at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)

at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)

at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)

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:194)

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:368)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)

at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)

at org.eclipse.equinox.launcher.Main.run(Main.java:1311)

Caused by: org.eclipse.swt.SWTError: No more handles [Could not detect registered XULRunner to use]

at org.eclipse.swt.SWT.error(SWT.java:3910)

TOPICS
Builder

Views

1.4K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
replies 4 Replies 4
latest latest Jump to latest reply
Guest
Mar 02, 2010 Mar 02, 2010

Copy link to clipboard

Copied

Hi ,

Can you turn off debug output in your coldfusion server and then try to run the extensions.

Thanks

Evelin Varghese

Adobe ColdFusion Builder Team

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
ToeJam
Explorer ,
Mar 03, 2010 Mar 03, 2010

Copy link to clipboard

Copied

In Response To Deleted User

Doesn't seem to help as I am still getting an Unhandled Loop Event Exception error:

org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: No more handles [Could not detect registered XULRunner to use])
    at org.eclipse.swt.SWT.error(SWT.java:3884)
    at org.eclipse.swt.SWT.error(SWT.java:3799)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3885)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3506)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
    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:194)
    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:368)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
Caused by: org.eclipse.swt.SWTError: No more handles [Could not detect registered XULRunner to use]
    at org.eclipse.swt.SWT.error(SWT.java:3910)
    at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:473)
    at org.eclipse.swt.browser.Browser.<init>(Browser.java:119)
    at com.adobe.ide.coldfusion.appcodegeneration.runtime.dialogs.HTMLContentDialog.createDialogArea(HTMLContentDialog.java:111)
    at org.eclipse.jface.dialogs.TitleAreaDialog.createContents(TitleAreaDialog.java:147)
    at com.adobe.ide.coldfusion.appcodegeneration.runtime.dialogs.HTMLContentDialog.createContents(HTMLContentDialog.java:164)
    at org.eclipse.jface.window.Window.create(Window.java:431)
    at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
    at org.eclipse.jface.window.Window.open(Window.java:790)
    at com.adobe.ide.coldfusion.appcodegeneration.runtime.CFMenuHandler$6.run(CFMenuHandler.java:473)
    at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:155)
    at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:158)
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
    ... 22 more

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
ToeJam
Explorer ,
Mar 03, 2010 Mar 03, 2010

Copy link to clipboard

Copied

In Response To ToeJam

I am getting closer to the problem. I unchecked the "Use Mozilla Browser" in preferences and now I see the errors complaining about path locations on extensions. I have uninstalled the extensions and reinstall using default webroot path of my server, some work some don't. This has only been a problem since I upgraded to CF9 from an existing CF8 installation.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
ToeJam
Explorer ,
Mar 05, 2010 Mar 05, 2010

Copy link to clipboard

Copied

LATEST
In Response To ToeJam

Ok, I found the cause and solution to this problem. This was caused by the CF9 install script on an existing CF8 installation with an already configured web connector for IIS.  When installing CF9 the location of the CFIDE directory was somehow located to c:/insetpub/wwwroot/CFIDE/CFIDE and the existing virtual directory on IIS was also modified (not sure if it was the install script or not). I ended up moving the CFIDE directory and updated  [cf9 home]\lib\neo-runtime.xml with new location of CFIDE and then updated the IIS virtual directory location and all my extensions now work. I do find it odd that the extension didn't work even when the CF9 was aware of the path to the CFIDE and only started working when I moved it to the "default".

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
Documentation
ColdFusion User Guide
Copyright © 2024 Adobe. All rights reserved.
Using the Community Experience League Terms of Use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices