[JBoss JIRA] (JBTIS-950) Cannot connect to fuse runtime after installing by the installer
by Lars Heinemann (JIRA)
[ https://issues.jboss.org/browse/JBTIS-950?page=com.atlassian.jira.plugin.... ]
Lars Heinemann commented on JBTIS-950:
--------------------------------------
I am ok with that. The process of how to create a server and to edit the user.properties file is already in the documentation.
> Cannot connect to fuse runtime after installing by the installer
> ----------------------------------------------------------------
>
> Key: JBTIS-950
> URL: https://issues.jboss.org/browse/JBTIS-950
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 10.0.0.CR1
> Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar
> Reporter: Andrej Podhradsky
> Assignee: Lars Heinemann
> Priority: Critical
>
> Cannot connect to fuse runtime after installing by the installer. The problem is that the runtime doesn't specify any user by default. This is important if you need to execute a command in the terminal (Terminal view).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4150) org.eclipse.thym.ui :: Could not load Hybrid Mobile quickstart: NoClassDefFound: org/apache/http/client/cache/HttpCacheStorage
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4150?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4150:
----------------------------------
Latest version of Thym I can find is 2.1.0.201611071511, from http://download.eclipse.org/thym/snapshots/
Going to assume we want this version mirrored and included in the aerogear build.
> org.eclipse.thym.ui :: Could not load Hybrid Mobile quickstart: NoClassDefFound: org/apache/http/client/cache/HttpCacheStorage
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4150
> URL: https://issues.jboss.org/browse/JBDS-4150
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: aerogear-hybrid, build, rhscl, rpm, target-platform
> Affects Versions: 10.2.0.AM2
> Environment: Installed:
> {code}
> Installed Packages
> Name : rh-eclipse46-devstudio
> Arch : x86_64
> Epoch : 0
> Version : 10.2
> Release : 0.20161028.1959.el7
> Size : 371 M
> Repo : @System
> From repo : rh-eclipse46-devstudio-snapshot-10.2
> Summary : Red Hat Developer Studio
> URL : http://developers.redhat.com/products/devstudio/overview/
> License : EPL
> Description : Red Hat Developer Studio.
> {code}
> On Fedora 24 w/ JDK 8.
> Reporter: Nick Boldt
> Assignee: Gorkem Ercan
> Priority: Blocker
> Fix For: 10.2.0.GA
>
> Attachments: hybrid-mobile-quickstart-constraint-violation-ignored-seems-to-work.png, hybrid-mobile-quickstart-constraint-violation.png, jbds4150_irc_log.txt, o.a.httpcomponents.httpclient_rh-eclipse__vs__devstudio_tp.png
>
>
> Trying to run the *Hybrid Mobile Project* quickstart:
> {code}
> Unhandled event loop exception
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NoClassDefFoundError: org/apache/http/client/cache/HttpCacheStorage)
> at org.eclipse.swt.SWT.error(SWT.java:4533)
> at org.eclipse.swt.SWT.error(SWT.java:4448)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4528)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4146)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> Caused by: java.lang.NoClassDefFoundError: org/apache/http/client/cache/HttpCacheStorage
> at org.eclipse.thym.ui.plugins.internal.CordovaPluginSelectionPage.<init>(CordovaPluginSelectionPage.java:99)
> at org.eclipse.thym.ui.plugins.internal.CordovaPluginSelectionPage.<init>(CordovaPluginSelectionPage.java:129)
> at org.eclipse.thym.ui.wizard.project.NewHybridProjectWizard.addPages(NewHybridProjectWizard.java:183)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:585)
> at org.eclipse.jface.window.Window.create(Window.java:426)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1095)
> at org.eclipse.jface.window.Window.open(Window.java:783)
> at org.jboss.tools.central.internal.WizardSupport.openWizard(WizardSupport.java:71)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$9.run(GettingStartedHtmlPage.java:431)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> ... 24 more
> Caused by: java.lang.ClassNotFoundException: org.apache.http.client.cache.HttpCacheStorage cannot be found by org.eclipse.thym.core_2.0.0.201607041526
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 35 more
> eclipse.buildId=4.6.1.v20160920-1429
> java.version=1.8.0_65
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_CA
> Command-line arguments: -os linux -ws gtk -arch x86_64 -consolelog -console -debug -data /tmp/wksp-20161101-1105
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4133) org.jboss.tools.ws.jaxrs.core :: error occurred during JAX-RS Metamodel build - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4133?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4133:
----------------------------------
TP changes to move to Lucene 5.4.1 (and keep 3.5.0, too) now building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >= 598
When done, you can verify your PR and apply it.
(Note that in Oxygen, Eclipse/Orbit/Fedora/RHSCL moves to Lucene 6 so we'll have to revisit this problem again in about 4-5 months to adopt that new version.)
> org.jboss.tools.ws.jaxrs.core :: error occurred during JAX-RS Metamodel build - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4133
> URL: https://issues.jboss.org/browse/JBDS-4133
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, target-platform, webservices
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Blocker
> Fix For: 10.2.0.GA
>
> Attachments: image-2016-11-08-19-07-53-492.png, lucene3.5corevs.5.4.1analyzers-common.png, lucene3.5corevs.5.4.1queryparser.png, org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt, osgi-console-lucene.png, TEST-org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.xml
>
>
> I'm getting this problem after running the HTML5 quickstart. I've installed this [1] version of the rpm.
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2016-10-26 16:22:07.578
> !MESSAGE An internal error occurred during: "JAX-RS Metamodel build...".
> !STACK 0
> java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.<init>(JaxrsMetamodel.java:163)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.create(JaxrsMetamodel.java:278)
> at org.jboss.tools.ws.jaxrs.core.metamodel.domain.JaxrsMetamodelLocator.get(JaxrsMetamodelLocator.java:120)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedBuildJob.run(ResourceChangedBuildJob.java:68)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: org.apache.lucene.analysis.standard.StandardAnalyzer cannot be found by org.jboss.tools.ws.jaxrs.core_1.9.2.v20161011-1002
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 5 more
> {code}
> [1] https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/20...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23481) build target platform sources site (for use with PDE Source Lookup)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23481?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23481:
-------------------------------
Fix Version/s: 4.4.x
> build target platform sources site (for use with PDE Source Lookup)
> -------------------------------------------------------------------
>
> Key: JBIDE-23481
> URL: https://issues.jboss.org/browse/JBIDE-23481
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.2.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.x
>
>
> So that dev and qe can use Fred's PDE source lookup tool [1] to grab source bundles on demand (instead of having to build a target platform locally w/ all the sources [2]), we need to:
> [1] https://github.com/fbricon/pde.source.lookup/
> [2] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ...
> * build a targetplatform with all the sources
> * split that repo into two pieces: all the .source files, and everything else
> * regen the metadata (featureandbundlepublisher) in each new repo so that all the features/plugins are uncategorized
> OR...
> * build a targetplatform without the sources
> * transform the .target file so that each IU ends with .source
> * build the target platform repo from the new .target file
> * verify that sources repo includes the sources of nested features, and those features' plugins' sources too
> ----
> Then once we have the targetplatform.source repo, publish that and verify it works with the PDE Source Lookup plugin:
> 1. install the PDE source lookup plugin
> 2. Window > Prefs > Update > Avail Software Sites > Add the new tp.source site
> 3. for something you want sources, use the plugin and see if it can resolve soources
> ----
> Then, if that works, we can consider adding the new tp.source site into the JBT/devstudio composite sites, along with jbt + tp + central + central tp (or ds + ds tp + central + central tp) as a 5th child site.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBTIS-950) Cannot connect to fuse runtime after installing by the installer
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-950?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-950:
----------------------------------
[~lhein] [~apodhrad] - We've discussed this - for this release we're not shipping the fat installer w/ Fuse runtime anyway. Long term (Devstudio IS 10.1.0) we'll have to document the fact that the users.properties file needs to be edited. Ultimately - we'll likely ned to modufty the installer to have the user establish a new user. So for now - I'd like to reeduce the severity of this Jira. wdyt?
> Cannot connect to fuse runtime after installing by the installer
> ----------------------------------------------------------------
>
> Key: JBTIS-950
> URL: https://issues.jboss.org/browse/JBTIS-950
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 10.0.0.CR1
> Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar
> Reporter: Andrej Podhradsky
> Assignee: Lars Heinemann
> Priority: Critical
>
> Cannot connect to fuse runtime after installing by the installer. The problem is that the runtime doesn't specify any user by default. This is important if you need to execute a command in the terminal (Terminal view).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBTIS-950) Cannot connect to fuse runtime after installing by the installer
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-950?page=com.atlassian.jira.plugin.... ]
Paul Leacu edited comment on JBTIS-950 at 11/10/16 11:33 AM:
-------------------------------------------------------------
[~lhein] [~apodhrad] - We've discussed this - for this release we're not shipping the fat installer w/ Fuse runtime anyway. Long term (Devstudio IS 10.1.0) we'll have to document the fact that the users.properties file needs to be edited. Ultimately - we'll likely need to modifty the installer to have the user establish a new user. So for now - I'd like to reduce the severity of this Jira. wdyt?
was (Author: pleacu):
[~lhein] [~apodhrad] - We've discussed this - for this release we're not shipping the fat installer w/ Fuse runtime anyway. Long term (Devstudio IS 10.1.0) we'll have to document the fact that the users.properties file needs to be edited. Ultimately - we'll likely ned to modufty the installer to have the user establish a new user. So for now - I'd like to reeduce the severity of this Jira. wdyt?
> Cannot connect to fuse runtime after installing by the installer
> ----------------------------------------------------------------
>
> Key: JBTIS-950
> URL: https://issues.jboss.org/browse/JBTIS-950
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 10.0.0.CR1
> Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar
> Reporter: Andrej Podhradsky
> Assignee: Lars Heinemann
> Priority: Critical
>
> Cannot connect to fuse runtime after installing by the installer. The problem is that the runtime doesn't specify any user by default. This is important if you need to execute a command in the terminal (Terminal view).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23481) build target platform sources site (for use with PDE Source Lookup)
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23481?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-23481:
----------------------------------------
We could only add the sources to the JBoss Tools TP site, not to the JBDS one. So the installer remains slimer but devs can easily access sources (I imagine they mostly use the JBT TP site_.
> build target platform sources site (for use with PDE Source Lookup)
> -------------------------------------------------------------------
>
> Key: JBIDE-23481
> URL: https://issues.jboss.org/browse/JBIDE-23481
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.2.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> So that dev and qe can use Fred's PDE source lookup tool [1] to grab source bundles on demand (instead of having to build a target platform locally w/ all the sources [2]), we need to:
> [1] https://github.com/fbricon/pde.source.lookup/
> [2] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ...
> * build a targetplatform with all the sources
> * split that repo into two pieces: all the .source files, and everything else
> * regen the metadata (featureandbundlepublisher) in each new repo so that all the features/plugins are uncategorized
> OR...
> * build a targetplatform without the sources
> * transform the .target file so that each IU ends with .source
> * build the target platform repo from the new .target file
> * verify that sources repo includes the sources of nested features, and those features' plugins' sources too
> ----
> Then once we have the targetplatform.source repo, publish that and verify it works with the PDE Source Lookup plugin:
> 1. install the PDE source lookup plugin
> 2. Window > Prefs > Update > Avail Software Sites > Add the new tp.source site
> 3. for something you want sources, use the plugin and see if it can resolve soources
> ----
> Then, if that works, we can consider adding the new tp.source site into the JBT/devstudio composite sites, along with jbt + tp + central + central tp (or ds + ds tp + central + central tp) as a 5th child site.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23429) Jolokia JMX connection
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23429?page=com.atlassian.jira.plugi... ]
Martin Malina edited comment on JBIDE-23429 at 11/10/16 11:13 AM:
------------------------------------------------------------------
I installed the PR on top of jbt master.
I started wildfly 10.1, deployed jolokia-war-1.3.5.war and then tried to create a jolokia jmx connection.
I entered http://localhost:8081/jolokia-war-1.3.5/ as the url, used POST and finished.
(My server runs on 8081.)
And I was able to connect.
was (Author: mmalina):
I installed the PR on top of jbt master.
I started wildfly 10.1, deployed jolokia-war-1.3.5.war and then tried to create a jolokia jmx connection.
I entered http://localhost:8080/jolokia-war-1.3.5/ as the url, used POST and finished.
Immediately, I got:
{code}
An error occurred while opening the connection.
org.jolokia.client.exception.J4pConnectException: Cannot connect to http://localhost:8080/jolokia-war-1.3.5/: Connect to localhost:8080 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1, localhost/fe80:0:0:0:0:0:0:1%1] failed: Connection refused
{code}
> Jolokia JMX connection
> ----------------------
>
> Key: JBIDE-23429
> URL: https://issues.jboss.org/browse/JBIDE-23429
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jmx
> Affects Versions: 4.4.2.AM2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.2.Final
>
>
> A jolokia JMX connection would be useful for some users, and could also be used to connect to JMX for an EAP behind openshift / cdk.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months