June 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3058) Workaround to JBDS-3054 causes the blank/white welcome screen bug to return

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3058?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3058: ------------------------------- Attachment: workaround_bug.png > Workaround to JBDS-3054 causes the blank/white welcome screen bug to return > --------------------------------------------------------------------------- > > Key: JBDS-3058 > URL: https://issues.jboss.org/browse/JBDS-3058 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: welcome > Affects Versions: 8.0.0.Beta2 > Environment: JBDS 8.0.beta2.respin-a > RHEL 6.5 > OpenJDK 1.7 > Reporter: Len DiMaggio > Assignee: Snjezana Peco > Attachments: workaround_bug.png > > > If the workaround defined in JBDS-3054 is used (-Dorg.jboss.tools.vpe.loadxulrunner=false), then the welcome screen becomes blank. See attached screenshot. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17509) NPE in ModuleSlotManifestUtil

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17509?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17509. --------------------------------- Assignee: Rob Stryker Resolution: Done Committed what I think is a fix. It's not obvious how this null is getting there, though. There's only 2 entry points for these methods and I don't see any obvious code that can set a null. It checks if the key is in the map, and if it's not, it generates a clean array as the value. The only way this NPE can be hit is if someone previously did a set(project, null), or something like that. Anyway, added null protection as best as I could, but still... confusing. Denis: any steps to replicate? Help QE out a bit here. > NPE in ModuleSlotManifestUtil > ----------------------------- > > Key: JBIDE-17509 > URL: https://issues.jboss.org/browse/JBIDE-17509 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.2.0.Beta3 > > > {code}java.lang.NullPointerException > at java.util.Arrays$ArrayList.<init>(Arrays.java:2842) > at java.util.Arrays.asList(Arrays.java:2828) > at org.jboss.ide.eclipse.as.classpath.core.runtime.modules.manifest.ModuleSlotManifestUtil.esureInCache(ModuleSlotManifestUtil.java:58) > at org.jboss.ide.eclipse.as.classpath.core.runtime.internal.ManifestChangeListener.resourceChanged(ManifestChangeListener.java:69) > at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285) > at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149) > at org.eclipse.core.internal.resources.Workspace.broadcastBuildEvent(Workspace.java:384) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:139) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17505) Unable to download runtime to nonexisting folder

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17505?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17505: ---------------------------------- Assignee: Snjezana Peco > Unable to download runtime to nonexisting folder > ------------------------------------------------ > > Key: JBIDE-17505 > URL: https://issues.jboss.org/browse/JBIDE-17505 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, runtime-detection > Affects Versions: 4.2.0.Beta2 > Reporter: Rastislav Wagner > Assignee: Snjezana Peco > Labels: respin-b > Fix For: 4.2.0.Beta2 > > > Download folder does not exist or is not writable. It will be created for you. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3054) Seeing recurring, almost constant core dumps with JBDS 8.0.beta2 on RHEL 6.5

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBDS-3054?page=com.atlassian.jira.plugin.... ] Snjezana Peco resolved JBDS-3054. --------------------------------- Fix Version/s: 8.0.0.Beta2 Resolution: Duplicate Issue A duplicate of JBDS-3022. > Seeing recurring, almost constant core dumps with JBDS 8.0.beta2 on RHEL 6.5 > ---------------------------------------------------------------------------- > > Key: JBDS-3054 > URL: https://issues.jboss.org/browse/JBDS-3054 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build > Affects Versions: 8.0.0.Beta2 > Environment: JBDS 8.0.beta2 > RHEL 6.5 > uname -a > Linux 2.6.32-431.11.2.el6.x86_64 #1 SMP Mon Mar 3 13:32:45 EST 2014 x86_64 x86_64 x86_64 GNU/Linux > OpenJDK 1.7 > Reporter: Len DiMaggio > Assignee: Snjezana Peco > Priority: Critical > Fix For: 8.0.0.Beta2 > > Attachments: eclipse.log.WedMay28_111225EDT2014.txt > > > After installing JBDS 8.0.beta2 on RHEL 6.5, I am seeing JBDS core dump and exit while performing simple tasks such as defining a new server, or sometimes even when just opening the IDE. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3054) Seeing recurring, almost constant core dumps with JBDS 8.0.beta2 on RHEL 6.5

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBDS-3054?page=com.atlassian.jira.plugin.... ] Snjezana Peco commented on JBDS-3054: ------------------------------------- Nick, The exception you got is related to WebKit. This issue is related to XULRunner. Could you, please, create a new jira? > Seeing recurring, almost constant core dumps with JBDS 8.0.beta2 on RHEL 6.5 > ---------------------------------------------------------------------------- > > Key: JBDS-3054 > URL: https://issues.jboss.org/browse/JBDS-3054 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build > Affects Versions: 8.0.0.Beta2 > Environment: JBDS 8.0.beta2 > RHEL 6.5 > uname -a > Linux 2.6.32-431.11.2.el6.x86_64 #1 SMP Mon Mar 3 13:32:45 EST 2014 x86_64 x86_64 x86_64 GNU/Linux > OpenJDK 1.7 > Reporter: Len DiMaggio > Assignee: Snjezana Peco > Priority: Critical > Attachments: eclipse.log.WedMay28_111225EDT2014.txt > > > After installing JBDS 8.0.beta2 on RHEL 6.5, I am seeing JBDS core dump and exit while performing simple tasks such as defining a new server, or sometimes even when just opening the IDE. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17480) Error in validation of jboss-deployment-structure.xml

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17480?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-17480: ----------------------------------- Component/s: server > Error in validation of jboss-deployment-structure.xml > ----------------------------------------------------- > > Key: JBIDE-17480 > URL: https://issues.jboss.org/browse/JBIDE-17480 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Environment: Version: 8.0.0.Beta1 > Build id: Beta1-v20140408-2350-B93 > Build date: 20140408-2350 > Reporter: Emil Cervenan > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.Beta3 > > > Wrong validation error on jboss-deployment-structure.xml file: > {code} > <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> > <deployment> > <dependencies> > <module name="org.apache.log4j" slot="main" export="true"/> > </dependencies> > <exclusions> > <module name="org.hibernate"/> > </exclusions> > </deployment> > </jboss-deployment-structure> > {code} > Error: > {code} > cvc-complex-type.2.4.b: The content of element 'deployment' is not complete. One of '{"urn:jboss:deployment-structure:1.2":module-alias, "urn:jboss:deployment-structure:1.2":exports, "urn:jboss:deployment-structure:1.2":resources, "urn:jboss:deployment-structure:1.2":transformers, "urn:jboss:deployment-structure:1.2":local-last, "urn:jboss:deployment-structure:1.2":exclude-subsystems}' is expected. > {code} > Same for urn:jboss:deployment-structure:1.1. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17484) Trying to start a EAP/AS server in JBDS 8.beta2/JBT 420.beta2 raises exception

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17484?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-17484: --------------------------------------- Rob is right. This is a problem with XULRunner that happens when using OpenJDK in specific environments. I think this issue is a duplicate of JBDS-3022, JBDS-3054 and JBIDE-11410. I haven't succeeded to reproduce it on RHEL 6.5 either using Oracle JDK or OpenJDK. I have tested USB LiveOS without any updates and additional packages. Len, Can you reproduce the issue using Oracle JDK? > 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, xulrunner > Affects Versions: 4.2.0.Beta2 > Environment: RHEL 6.5 > OpenJDK 1.7 > 4.2.0.beta2 > Reporter: Len DiMaggio > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.2.0.Beta3 > > > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-17509) NPE in ModuleSlotManifestUtil

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-17509: ------------------------------------- Summary: NPE in ModuleSlotManifestUtil Key: JBIDE-17509 URL: https://issues.jboss.org/browse/JBIDE-17509 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.2.0.Beta2 Reporter: Denis Golovin {code}java.lang.NullPointerException at java.util.Arrays$ArrayList.<init>(Arrays.java:2842) at java.util.Arrays.asList(Arrays.java:2828) at org.jboss.ide.eclipse.as.classpath.core.runtime.modules.manifest.ModuleSlotManifestUtil.esureInCache(ModuleSlotManifestUtil.java:58) at org.jboss.ide.eclipse.as.classpath.core.runtime.internal.ManifestChangeListener.resourceChanged(ManifestChangeListener.java:69) at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149) at org.eclipse.core.internal.resources.Workspace.broadcastBuildEvent(Workspace.java:384) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:139) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17509) NPE in ModuleSlotManifestUtil

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17509?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17509: ---------------------------------- Fix Version/s: 4.2.0.Beta3 > NPE in ModuleSlotManifestUtil > ----------------------------- > > Key: JBIDE-17509 > URL: https://issues.jboss.org/browse/JBIDE-17509 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Fix For: 4.2.0.Beta3 > > > {code}java.lang.NullPointerException > at java.util.Arrays$ArrayList.<init>(Arrays.java:2842) > at java.util.Arrays.asList(Arrays.java:2828) > at org.jboss.ide.eclipse.as.classpath.core.runtime.modules.manifest.ModuleSlotManifestUtil.esureInCache(ModuleSlotManifestUtil.java:58) > at org.jboss.ide.eclipse.as.classpath.core.runtime.internal.ManifestChangeListener.resourceChanged(ManifestChangeListener.java:69) > at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285) > at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149) > at org.eclipse.core.internal.resources.Workspace.broadcastBuildEvent(Workspace.java:384) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:139) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17508) Cordova config.xml editor stays open with unidentified error after HMT project is deleted

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17508?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17508: ---------------------------------- Attachment: cordova-config.png > Cordova config.xml editor stays open with unidentified error after HMT project is deleted > ----------------------------------------------------------------------------------------- > > Key: JBIDE-17508 > URL: https://issues.jboss.org/browse/JBIDE-17508 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Attachments: cordova-config.png > > > Now after HMT project is created, config.xml is opened by default for it. Wen project is deleted, config.xml editor stays opened in broken state -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2014