[JBoss JIRA] (JBIDE-17484) Trying to start a EAP/AS server in JBDS 8.beta2/JBT 420.beta2 raises exception
by Len DiMaggio (JIRA)
Len DiMaggio created JBIDE-17484:
------------------------------------
Summary: Trying to start a EAP/AS server in JBDS 8.beta2/JBT 420.beta2 raises exception
Key: JBIDE-17484
URL: https://issues.jboss.org/browse/JBIDE-17484
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Beta2
Environment: RHEL 6.5
OpenJDK 1.7
4.2.0.beta2
Reporter: Len DiMaggio
Priority: Critical
Trying to start a EAP/AS server in JBDS 8.beta2/JBT 420.beta2 raises this exception:
May 29, 2014 3:32:09 PM org.xnio.ChannelListeners invokeChannelListener
ERROR: A channel event listener threw an exception
java.security.ProviderException: Could not initialize NSS
at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:223)
at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:103)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:224)
at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:206)
at java.security.AccessController.doPrivileged(Native Method)
at sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:206)
at sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:187)
at sun.security.jca.ProviderList.loadAll(ProviderList.java:281)
at sun.security.jca.ProviderList.removeInvalid(ProviderList.java:298)
at sun.security.jca.Providers.getFullProviderList(Providers.java:176)
at java.security.Security.getProviders(Security.java:458)
at org.xnio.sasl.SaslUtils.getFactories(SaslUtils.java:123)
at org.xnio.sasl.SaslUtils.getSaslClientFactories(SaslUtils.java:100)
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:362)
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:227)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:180)
at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
at org.xnio.nio.NioHandle.run(NioHandle.java:90)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:187)
Caused by: java.io.IOException: /jboss/local/JBT/420.beta2/eclipse/plugins/org.mozilla.xulrunner.gtk.linux.x86_64_1.9.2.19pre/xulrunner/libnssutil3.so: version `NSSUTIL_3.13' not found (required by /usr/lib64/libnss3.so)
at sun.security.pkcs11.Secmod.nssLoadLibrary(Native Method)
at sun.security.pkcs11.Secmod.initialize(Secmod.java:209)
at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:218)
... 28 more
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17484) Trying to start a EAP/AS server in JBDS 8.beta2/JBT 420.beta2 raises exception
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17484?page=com.atlassian.jira.plugi... ]
Len DiMaggio commented on JBIDE-17484:
--------------------------------------
Workaround:
Disable Visual Editor by adding the option –Dorg.jboss.tools.vpe.loadxulrunner=false to the eclipse.ini (or jbdevstudio.ini if you use JBoss Developer Studio).
> Trying to start a EAP/AS server in JBDS 8.beta2/JBT 420.beta2 raises exception
> ------------------------------------------------------------------------------
>
> Key: JBIDE-17484
> URL: https://issues.jboss.org/browse/JBIDE-17484
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta2
> Environment: RHEL 6.5
> OpenJDK 1.7
> 4.2.0.beta2
> Reporter: Len DiMaggio
> Priority: Critical
>
> Trying to start a EAP/AS server in JBDS 8.beta2/JBT 420.beta2 raises this exception:
> May 29, 2014 3:32:09 PM org.xnio.ChannelListeners invokeChannelListener
> ERROR: A channel event listener threw an exception
> java.security.ProviderException: Could not initialize NSS
> at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:223)
> at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:103)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:224)
> at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:206)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:206)
> at sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:187)
> at sun.security.jca.ProviderList.loadAll(ProviderList.java:281)
> at sun.security.jca.ProviderList.removeInvalid(ProviderList.java:298)
> at sun.security.jca.Providers.getFullProviderList(Providers.java:176)
> at java.security.Security.getProviders(Security.java:458)
> at org.xnio.sasl.SaslUtils.getFactories(SaslUtils.java:123)
> at org.xnio.sasl.SaslUtils.getSaslClientFactories(SaslUtils.java:100)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:362)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:227)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:180)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.nio.NioHandle.run(NioHandle.java:90)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:187)
> Caused by: java.io.IOException: /jboss/local/JBT/420.beta2/eclipse/plugins/org.mozilla.xulrunner.gtk.linux.x86_64_1.9.2.19pre/xulrunner/libnssutil3.so: version `NSSUTIL_3.13' not found (required by /usr/lib64/libnss3.so)
> at sun.security.pkcs11.Secmod.nssLoadLibrary(Native Method)
> at sun.security.pkcs11.Secmod.initialize(Secmod.java:209)
> at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:218)
> ... 28 more
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17483) Quick Fix for Console configuration "" does not exist
by Burr Sutter (JIRA)
Burr Sutter created JBIDE-17483:
-----------------------------------
Summary: Quick Fix for Console configuration "" does not exist
Key: JBIDE-17483
URL: https://issues.jboss.org/browse/JBIDE-17483
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Burr Sutter
When using Maven import on "someone else's" project, it is fairly common to get a complaint about the missing Console Configuration. Numerous workarounds have been documented and can be found via Google - some work, some do not - ideally we would offer a quickfix to help address this common error message inside of the IDE.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17482) Listing of the Cordova plugins do not work behind a proxy
by Gorkem Ercan (JIRA)
Gorkem Ercan created JBIDE-17482:
------------------------------------
Summary: Listing of the Cordova plugins do not work behind a proxy
Key: JBIDE-17482
URL: https://issues.jboss.org/browse/JBIDE-17482
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: aerogear-hybrid
Affects Versions: 4.2.0.Beta1
Reporter: Gorkem Ercan
Priority: Critical
When the Cordova plug-in discovery wizard is started the list of Cordova plugins are not retrieved if working behind a proxy server. The list is cached so once the list is retrieved installation seems to go as expected.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-14803) eclipse CSS outling resulting in Null pointer exception
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14803?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-14803.
-------------------------------
Verified with JBDS 8.0.0.Beta2-v20140525-2146-B104
> eclipse CSS outling resulting in Null pointer exception
> -------------------------------------------------------
>
> Key: JBIDE-14803
> URL: https://issues.jboss.org/browse/JBIDE-14803
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream, visual-page-editor-core
> Affects Versions: 4.2.0.Beta2
> Environment: Windows, Mac OS X
> Reporter: Max Rydahl Andersen
> Assignee: Denis Golovin
> Fix For: 4.2.0.Beta2
>
>
> EXECUTE: open screen.css from kitchensink mobile.
> EXECUTE: double click on #members.row in outline
> asssert: screen.css editor higlights members.row
> what happens: multiple errors + dialogs logged with:
> java.lang.NullPointerException
> at org.eclipse.wst.sse.ui.internal.contentoutline.ConfigurableContentOutlinePage$5.getShowInContext(ConfigurableContentOutlinePage.java:444)
> at org.eclipse.ui.internal.services.WorkbenchSourceProvider.getContext(WorkbenchSourceProvider.java:418)
> at org.eclipse.ui.internal.services.WorkbenchSourceProvider.updateActivePart(WorkbenchSourceProvider.java:484)
> at org.eclipse.ui.internal.services.WorkbenchSourceProvider.updateActivePart(WorkbenchSourceProvider.java:445)
> at org.eclipse.ui.internal.services.WorkbenchSourceProvider.getCurrentState(WorkbenchSourceProvider.java:134)
> at org.eclipse.ui.internal.services.WorkbenchSourceProvider$6.handleEvent(WorkbenchSourceProvider.java:684)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1080)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4163)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1470)
> at org.eclipse.swt.widgets.Shell.windowDidBecomeKey(Shell.java:2157)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5602)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:214)
> at org.eclipse.swt.widgets.Widget.becomeKeyWindow(Widget.java:366)
> at org.eclipse.swt.widgets.Shell.becomeKeyWindow(Shell.java:523)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5426)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSWindow.close(NSWindow.java:54)
> at org.eclipse.swt.widgets.Shell.destroyWidget(Shell.java:797)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1318)
> at org.eclipse.swt.widgets.Control.release(Control.java:2848)
> at org.eclipse.swt.widgets.Widget.dispose(Widget.java:671)
> at org.eclipse.jface.window.Window.close(Window.java:336)
> at org.eclipse.jface.dialogs.Dialog.close(Dialog.java:994)
> at org.eclipse.ui.internal.statushandlers.InternalDialog.close(InternalDialog.java:710)
> at org.eclipse.jface.dialogs.Dialog.okPressed(Dialog.java:955)
> at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:476)
> at org.eclipse.ui.internal.statushandlers.InternalDialog.buttonPressed(InternalDialog.java:190)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4164)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4010)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3649)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> 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:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBDS-3016) Support multiple versions of jQuery in the jQuery Mobile Palette
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBDS-3016?page=com.atlassian.jira.plugin.... ]
Vlado Pakan closed JBDS-3016.
-----------------------------
Verified with JBDS 8.0.0.Beta2-v20140525-2146-B104
> Support multiple versions of jQuery in the jQuery Mobile Palette
> ----------------------------------------------------------------
>
> Key: JBDS-3016
> URL: https://issues.jboss.org/browse/JBDS-3016
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 8.0.0.Beta1
> Reporter: Vineet Reynolds
> Assignee: Alexey Kazakov
> Fix For: 8.0.0.Beta2
>
>
> The version of jQuery used in the snippet created by the jQM palette is 1.10.2. We should plan to support multiple versions of jQuery (1.x and 2.x) because:
> * JBoss WFK is planning to deprecate jQuery 1.x and move to jQuery 2.x.
> * jQuery 1.x support would still be required by end-users that wish to support their apps and sites on older browsers (notably MSIE 6-8 that are unsupported in jQuery 2+).
> N.B: Cordova apps are expected to use jQuery 2+ - the jQuery team does not support 1.x usage in this environment.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-16881) VPE crashes workbench on Fedora 19
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16881?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-16881.
-------------------------------
> VPE crashes workbench on Fedora 19
> ----------------------------------
>
> Key: JBIDE-16881
> URL: https://issues.jboss.org/browse/JBIDE-16881
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: xulrunner
> Affects Versions: 4.2.0.Beta1
> Environment: Fedora 19, 64-bit, java version "1.7.0_51", OpenJDK Runtime Environment (fedora-2.4.5.0.fc19-x86_64 u51-b31)
> Reporter: Michelle Murray
> Fix For: 4.2.0.Beta2
>
>
> Most of IDE seems to be working acceptably on F19. But trying to open a file (e.g. html file) throws up error message:
> "Could not open the Visual Page Editor:
> No more handles [Browser style SWT.MOZILLA and Java system property org.eclipse.swt.browser.DefaultType=mozilla are not supported with GTK 3 as XULRunner is not ported for GTK 3 yet]
> No more handles [Browser style SWT.MOZILLA and Java system property org.eclipse.swt.browser.DefaultType=mozilla are not supported with GTK 3 as XULRunner is not ported for GTK 3 yet]"
> After clicking OK, the error message closes and the editor opens. Just the visual part of the visual/source tab shows an error message. But switching away to the source tab and then back to the visual/source tab causes the error message to be shown again.
> I know we know there are Luna-Linux issues. But I'm reporting this here as it seems we weren't sure if Fedora 19 would be affected. Also JBIDE-16280 seems to report the issue as being resolved in 4.2.0.Alpha2 but I'm finding it isn't in Beta1.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17154) HTML5 Palette Version popup window wrong placement
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17154?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-17154.
-------------------------------
Verified with JBDS 8.0.0.Beta2-v20140525-2146-B104
> HTML5 Palette Version popup window wrong placement
> --------------------------------------------------
>
> Key: JBIDE-17154
> URL: https://issues.jboss.org/browse/JBIDE-17154
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta2
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Priority: Minor
> Fix For: 4.2.0.Beta2
>
> Attachments: JQueryMobileVersionWrongPlace.png
>
>
> Test case:
> EXECUTE:
> 1. Create test.html file:
> {code}
> <!doctype html>
> <body>
> </body>
> {code}
> 2. Open file test.html in Visual Page Editor
> ASSERT:
> jQueryMobile and HTML Palettes appear
> 3. Scroll palette down
> 4. Click on HTML Palette Folder Version (5.0)
> FAIL:
> Version popup window appears in wrong place:
> !JQueryMobileVersionWrongPlace.png!
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months