[JBoss JIRA] (JBIDE-18628) NPE when creating Connection Profile using forge wizard
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18628?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-18628:
------------------------------------
I don't get what is so different on JBDS against JBT that it triggers this bug for me.
> NPE when creating Connection Profile using forge wizard
> -------------------------------------------------------
>
> Key: JBIDE-18628
> URL: https://issues.jboss.org/browse/JBIDE-18628
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.CR2
> Reporter: Pavol Srna
> Priority: Blocker
> Labels: regression
> Fix For: 4.2.0.CR2
>
>
> {code}
> java.lang.NullPointerException
> at java.util.Hashtable.put(Hashtable.java:459)
> at java.util.Properties.setProperty(Properties.java:166)
> at org.jboss.tools.forge.ui.internal.ext.database.ConnectionProfileManagerImpl.createProperties(ConnectionProfileManagerImpl.java:172)
> at org.jboss.tools.forge.ui.internal.ext.database.ConnectionProfileManagerImpl.saveExistingProfile(ConnectionProfileManagerImpl.java:82)
> at org.jboss.tools.forge.ui.internal.ext.database.ConnectionProfileManagerImpl.saveConnectionProfile(ConnectionProfileManagerImpl.java:73)
> at org.jboss.tools.forge.ui.internal.ext.database.ConnectionProfileManagerImpl.saveConnectionProfiles(ConnectionProfileManagerImpl.java:142)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
> at org.jboss.forge.addon.database.tools.connections.ConnectionProfileManager_$$_javassist_38d8b832-4a59-46f2-bc9d-eb9ff785daba.saveConnectionProfiles(ConnectionProfileManager_$$_javassist_38d8b832-4a59-46f2-bc9d-eb9ff785daba.java)
> at org.jboss.forge.addon.database.tools.connections.ui.CreateConnectionProfileCommandImpl.execute(CreateConnectionProfileCommandImpl.java:62)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
> at org.jboss.forge.addon.database.tools.connections.ui.CreateConnectionProfileCommandImpl_$$_javassist_e7993baf-c96e-4b2e-9196-875229a146df.execute(CreateConnectionProfileCommandImpl_$$_javassist_e7993baf-c96e-4b2e-9196-875229a146df.java)
> at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.execute(SingleCommandControllerImpl.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
> at org.jboss.forge.addon.ui.controller.CommandController_$$_javassist_7a19049c-bb8a-4bcc-9fab-671730e3e0e2.execute(CommandController_$$_javassist_7a19049c-bb8a-4bcc-9fab-671730e3e0e2.java)
> at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizard$1.run(ForgeWizard.java:113)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18628) NPE when creating Connection Profile using forge wizard
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18628?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-18628:
------------------------------------
I purge .forge .eclipse, tried new workspace and even restarted my computer. And I've been able to reproduce all the time.
My machine is ubuntu 14.04 LTS - x86_64.
java version "1.8.0_20"
Java(TM) SE Runtime Environment (build 1.8.0_20-b26)
Java HotSpot(TM) 64-Bit Server VM (build 25.20-b23, mixed mode)
And I also managed to reproduce it on macosx 10.8. -- [~vpakan] can confirm what he saw.
But I admit that it is a strange bug because [~rawagner] could not reproduce on ubuntu 12.04.
We need to find a root cause for this. Any more ideas?
> NPE when creating Connection Profile using forge wizard
> -------------------------------------------------------
>
> Key: JBIDE-18628
> URL: https://issues.jboss.org/browse/JBIDE-18628
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.CR2
> Reporter: Pavol Srna
> Priority: Blocker
> Labels: regression
> Fix For: 4.2.0.CR2
>
>
> {code}
> java.lang.NullPointerException
> at java.util.Hashtable.put(Hashtable.java:459)
> at java.util.Properties.setProperty(Properties.java:166)
> at org.jboss.tools.forge.ui.internal.ext.database.ConnectionProfileManagerImpl.createProperties(ConnectionProfileManagerImpl.java:172)
> at org.jboss.tools.forge.ui.internal.ext.database.ConnectionProfileManagerImpl.saveExistingProfile(ConnectionProfileManagerImpl.java:82)
> at org.jboss.tools.forge.ui.internal.ext.database.ConnectionProfileManagerImpl.saveConnectionProfile(ConnectionProfileManagerImpl.java:73)
> at org.jboss.tools.forge.ui.internal.ext.database.ConnectionProfileManagerImpl.saveConnectionProfiles(ConnectionProfileManagerImpl.java:142)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
> at org.jboss.forge.addon.database.tools.connections.ConnectionProfileManager_$$_javassist_38d8b832-4a59-46f2-bc9d-eb9ff785daba.saveConnectionProfiles(ConnectionProfileManager_$$_javassist_38d8b832-4a59-46f2-bc9d-eb9ff785daba.java)
> at org.jboss.forge.addon.database.tools.connections.ui.CreateConnectionProfileCommandImpl.execute(CreateConnectionProfileCommandImpl.java:62)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
> at org.jboss.forge.addon.database.tools.connections.ui.CreateConnectionProfileCommandImpl_$$_javassist_e7993baf-c96e-4b2e-9196-875229a146df.execute(CreateConnectionProfileCommandImpl_$$_javassist_e7993baf-c96e-4b2e-9196-875229a146df.java)
> at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.execute(SingleCommandControllerImpl.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
> at org.jboss.forge.addon.ui.controller.CommandController_$$_javassist_7a19049c-bb8a-4bcc-9fab-671730e3e0e2.execute(CommandController_$$_javassist_7a19049c-bb8a-4bcc-9fab-671730e3e0e2.java)
> at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizard$1.run(ForgeWizard.java:113)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBDS-2869) 3rd party certification for JBDS 8.0.0.GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2869?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2869 at 10/15/14 9:59 AM:
------------------------------------------------------------
Changes for CR2a/b:
* JBIDE-18567: Update to latest THyM 0.1.0.201410092351
* JBIDE-18571: Update to latest Luna SR1 (RC4a)
* JBDS-3179: Update to latest PMD 4.0.4
was (Author: nickboldt):
Changes for CR2b:
* JBIDE-18571: Update to latest Luna SR1 (RC4a)
* JBDS-3179: Update to latest PMD 4.0.4
> 3rd party certification for JBDS 8.0.0.GA
> -----------------------------------------
>
> Key: JBDS-2869
> URL: https://issues.jboss.org/browse/JBDS-2869
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: 3rd-party-certification, 3rd-party-dependencies, requirements, target-platform
> Affects Versions: 8.0.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.0.GA
>
>
> For JBDS 8.0.0.GA, we need to ensure this list is as current and up to date as possible.
> Upstream question about JDK 7 support:
> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=423834
> Proposed *new* connectors for JBDS 8.0:
> * SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) :: *DROPPED FOR 7.1, TBD for 8.0*
> Connectors we could update:
> * Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature 1.1.1.v20130917-0100
> * m2e-wro4j 1.0.2 connector
> * atlassian/3.2.2.v20130909 (affects JBT/JBDS/Central TP)
> * pmd/4.0.1
> * testng/6.8.6.20130914_0724 (affects JBDS installer/Central TP)
> * VJET/0.10.0.201309201624
> * eclipsecs/5.6.1.201306282206
> * springide/3.4.0.201310051539-RELEASE
> * gwt/3.4.2.v201310081834-rel-*r43 ONLY* (affects JBT/JBDS/Central TP)
> * subclipse/1.10.3_1.8.0.r10086_v20131126_1344/
> * findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
> Additionally (Target Platform):
> * swtbot 2.1.1.201305311053 (included in JBT TP; needed for running UI tests; move to 2.1.2?)
> JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
> * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
> * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
> See comments below for latest site URLs.
> [1] https://github.com/jbosstools/jbosstools-locus/
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
> [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
> ¥ - These issues did not block the release of JBDS 7.1.0.GA, and therefore would not block 8.0.0 either
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18457) EAP 6.1 fails to start on Windows 7 - prefer most closely matched java if strict-compatible is unavailable
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18457?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-18457.
---------------------------------
So the fix that Rob committed here is really a very very specific use case:
1) a user has an eap using java 6 as exedcution env
2) user has no java6 in workspace
3) user has java7 and java8 as installed jre's
4) neither the java7 nor java8 are workspace default
5) neither the java7 nor java8 are default for the java6 exec-env
You always have a default, so the only way all of the conditions can be met is if you have java 5 or java 4 jre defined. So it's very close to no fix at all :)
In other words, it's still up to the user to make sure that the right jdk is being used - the best way is to select a specific jre instead of the pre-defined exec env.
> EAP 6.1 fails to start on Windows 7 - prefer most closely matched java if strict-compatible is unavailable
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18457
> URL: https://issues.jboss.org/browse/JBIDE-18457
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
>
> This is followup of Brian's comments in JBIDE-16066 where he couldn't get EAP 6.1 to start on Windows 7. I tried the same and get the same result. Everything works fine on my mac.
> 1. Start JBDS 8.0.0.CR1
> 2. Download EAP 6.1 via runtime detection
> 3. Start the server
> In my case, at first I got "Starting jboss-eap-6.1: (0 %)" in the status bar and nothing else for like 5 minutes, then the server console showed up and showed:
> {code}
> 15:28:51,082 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1
> 15:28:51,704 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
> 15:28:51,824 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting
> {code}
> And with this the status bar changed to 100 % and the progress view shows:
> Preparing launch deletage.
> It's been like this at least 5 minutes now. The server is not started.
> I checked with Brian and he just didn't witness the first part where there was no console, but he did get what I got after 5 minutes - his server was stuck and would never really start.
> ATM I only tried this the one way - EAP 6.1 downloaded via runtime detection.
> In my case I have Oracle jdk 1.8, in Brian's case it was 1.7, so it doesn't seem to matter.
> Right now I haven't tried other server versions.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBDS-2869) 3rd party certification for JBDS 8.0.0.GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2869?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2869:
----------------------------------
Changes for CR2b:
* JBIDE-18571: Update to latest Luna SR1 (RC4a)
* JBDS-3179: Update to latest PMD 4.0.4
> 3rd party certification for JBDS 8.0.0.GA
> -----------------------------------------
>
> Key: JBDS-2869
> URL: https://issues.jboss.org/browse/JBDS-2869
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: 3rd-party-certification, 3rd-party-dependencies, requirements, target-platform
> Affects Versions: 8.0.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.0.GA
>
>
> For JBDS 8.0.0.GA, we need to ensure this list is as current and up to date as possible.
> Upstream question about JDK 7 support:
> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=423834
> Proposed *new* connectors for JBDS 8.0:
> * SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) :: *DROPPED FOR 7.1, TBD for 8.0*
> Connectors we could update:
> * Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature 1.1.1.v20130917-0100
> * m2e-wro4j 1.0.2 connector
> * atlassian/3.2.2.v20130909 (affects JBT/JBDS/Central TP)
> * pmd/4.0.1
> * testng/6.8.6.20130914_0724 (affects JBDS installer/Central TP)
> * VJET/0.10.0.201309201624
> * eclipsecs/5.6.1.201306282206
> * springide/3.4.0.201310051539-RELEASE
> * gwt/3.4.2.v201310081834-rel-*r43 ONLY* (affects JBT/JBDS/Central TP)
> * subclipse/1.10.3_1.8.0.r10086_v20131126_1344/
> * findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
> Additionally (Target Platform):
> * swtbot 2.1.1.201305311053 (included in JBT TP; needed for running UI tests; move to 2.1.2?)
> JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
> * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
> * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
> See comments below for latest site URLs.
> [1] https://github.com/jbosstools/jbosstools-locus/
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
> [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
> ¥ - These issues did not block the release of JBDS 7.1.0.GA, and therefore would not block 8.0.0 either
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBDS-2948) Improve Performance of small and large projects
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2948?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2948:
--------------------------------------
Fix Version/s: 8.0.x
9.0.x
(was: 8.0.0.GA)
> Improve Performance of small and large projects
> -----------------------------------------------
>
> Key: JBDS-2948
> URL: https://issues.jboss.org/browse/JBDS-2948
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: integration
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Labels: f2f2014
> Fix For: 8.0.x, 9.0.x
>
>
> Users have had noticable issues when importing projects having many schemas, many annotations and dependencies in past. Our and WTP validators seem to be causing issues - some are actual performance issues and others seem to be more perceived than actual issues.
> Unfortunately perceived issues for the user feels just as slow as real issues.
> Suggestion:
> Look in jira for performance issues and add "performance" label to them
> Allocate dev to use profiler to spot hotspots and get these findings reported/documented and then triage based on these findings
> Work with QE to setup performance measurements for end user common operations related to these issues (example: import project, run validation etc.) for small (quickstarts), medium (ticketmonster) and large (wildfly) projects and publish these numbers over time and keep track if getting better/worse.
> Setup goals to reach for these performance measurements.
> Don’t add new features that make performance worse. For example don’t introduce one more slow validation feature to the validator which already has performance issues until those issues are solved.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBDS-2948) Improve Performance of small and large projects
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2948?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2948:
--------------------------------------
Labels: f2f2014 (was: )
> Improve Performance of small and large projects
> -----------------------------------------------
>
> Key: JBDS-2948
> URL: https://issues.jboss.org/browse/JBDS-2948
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: integration
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Labels: f2f2014
> Fix For: 8.0.x, 9.0.x
>
>
> Users have had noticable issues when importing projects having many schemas, many annotations and dependencies in past. Our and WTP validators seem to be causing issues - some are actual performance issues and others seem to be more perceived than actual issues.
> Unfortunately perceived issues for the user feels just as slow as real issues.
> Suggestion:
> Look in jira for performance issues and add "performance" label to them
> Allocate dev to use profiler to spot hotspots and get these findings reported/documented and then triage based on these findings
> Work with QE to setup performance measurements for end user common operations related to these issues (example: import project, run validation etc.) for small (quickstarts), medium (ticketmonster) and large (wildfly) projects and publish these numbers over time and keep track if getting better/worse.
> Setup goals to reach for these performance measurements.
> Don’t add new features that make performance worse. For example don’t introduce one more slow validation feature to the validator which already has performance issues until those issues are solved.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months