[JBoss JIRA] (JBIDE-23429) Jolokia JMX connection
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23429?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-23429:
-------------------------------------
Here are some basic examples to test:
Standalone / on wf - eap
1) Start wildfly or eap on localhost / standalone.sh
2) Deploy jolokia's jolokia-war-1.3.5.war to the standalone/deployments
3) Open jmx explorer and create new jmx connection
4) Give a name, put http://localhost:8080/jolokia-war-1.3.5/ as url, and use POST method
5) Connect to the new connection, expand it, play in the UI
Behind CDK + EAP:
Reference doc: http://developers.redhat.com/blog/2016/03/30/jolokia-jvm-monitoring-in-op...
1) Start CDK
2) Enable port forwarding on openshift connection
3) Create jolokia connection as above, except:
4) Use this as url: https://<master_host>:8443/api/v1/namespaces/<project_name>/pods/https:<pod_name>:8778/proxy/jolokia
5) Make sure to use GET (POST doesn't fully work in this case)
6) Make sure to add Authorization / Bearer: blahblah to the headers section, as per the above document. This can be discoverd by using oc whoami –t after oc login
7) Expand jmx tree, play in UI, call an operation or two, probably shouldn't call jmx shutdown operation though ;)
> 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.AM3
>
>
> 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.2#72004)
8 years, 11 months
[JBoss JIRA] (JBIDE-23358) OpenShift Explorer: Pod status is not reflecting reality
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23358?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov commented on JBIDE-23358:
------------------------------------------
It turned out that the logic is more difficult, than just showing `status.phase`.
https://github.com/openshift/origin-web-console/blob/7c57218bb83964ba0aab...
I'll try to implement it
> OpenShift Explorer: Pod status is not reflecting reality
> --------------------------------------------------------
>
> Key: JBIDE-23358
> URL: https://issues.jboss.org/browse/JBIDE-23358
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Assignee: Dmitrii Bocharov
> Labels: openshift_v3
> Fix For: 4.4.x
>
> Attachments: pod_status.png
>
>
> When I have a pod with failed status, it is not correctly displayed in tooling. Pod under a service has status Running (as styled next next to tree item as well as property value in property view). Current status is failed, precisely "Crash loop back off" (happens often when there are problems with fetching an image...). The correct status is shown in Web-UI as well as from oc binary "oc get pods". Refresh of a project or service does not help.
> !pod_status.png!
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years, 11 months
[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4077:
----------------------------------
Possible PR to fix the above issue: https://github.com/jbosstools/jbosstools-integration-tests/pull/1652
> Cannot run integration tests against Devstudio with latest target platform
> --------------------------------------------------------------------------
>
> Key: JBDS-4077
> URL: https://issues.jboss.org/browse/JBDS-4077
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 10.2.0.AM1
> Reporter: Jan Richter
> Assignee: Rastislav Wagner
> Priority: Blocker
> Fix For: 10.2.0.AM3
>
> Attachments: .log, jbosstools-integration-tests.log.txt.zip, no_devstudio.jpg, no_devstudio.png, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt, org.jboss.tools.deltaspike.ui.bot.test.log.txt, org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png, Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png, Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png, Screenshot_2016-10-05_10-01-32.png, shell.png, TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png
>
>
> Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards.
> A full devstudio should open when the tests are run. Instead it looks like this:
> !tpfail.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years, 11 months
[JBoss JIRA] (JBTIS-973) BPMN2: Delete SWTBot launchers
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-973:
---------------------------------------
Summary: BPMN2: Delete SWTBot launchers
Key: JBTIS-973
URL: https://issues.jboss.org/browse/JBTIS-973
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: BPMN2, QE
Affects Versions: 4.4.0.Alpha1
Reporter: Andrej Podhradsky
Assignee: Jozef Marko
tests/org.jboss.tools.bpmn2.ui.bot.test/launcher
- AllEditorTests.launch
- AllWizardTests.launch
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years, 11 months
[JBoss JIRA] (JBTIS-972) The category 'Integration and SOA Development' doesn't contain fuse nor switchyard
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-972:
---------------------------------------
Summary: The category 'Integration and SOA Development' doesn't contain fuse nor switchyard
Key: JBTIS-972
URL: https://issues.jboss.org/browse/JBTIS-972
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: distribution
Affects Versions: 9.0.3.GA
Reporter: Andrej Podhradsky
The category 'Integration and SOA Development' should contain all integration and soa tools except the deprecated ones such as SOA 5.x. Currenly, the fuse and switchyard tooling is commented out.
{code:title=com.jboss.devstudio.integration-stack.soa.feature_9.0.3.GA-v20161028-1314-B73.jar}
<requires>
<import plugin="com.jboss.devstudio.core.project.examples"/>
<import plugin="com.jboss.devstudio.core.usage.branding"/>
<import plugin="com.jboss.devstudio.core.central"/>
<import plugin="org.jboss.tools.usage"/>
<import feature="org.jboss.tools.central.feature"/>
<import feature="org.jboss.tools.project.examples.feature"/>
<import feature="org.jboss.tools.bpel.feature"/>
<import feature="org.eclipse.bpmn2.feature"/>
<import feature="org.eclipse.bpmn2.modeler"/>
<import feature="org.eclipse.bpmn2.modeler.runtime.jboss"/>
<import feature="org.drools.eclipse.feature"/>
<import feature="org.guvnor.tools.feature"/>
<import feature="org.jbpm.eclipse.feature"/>
<import feature="org.kie.eclipse.feature"/>
<import feature="org.kie.eclipse.navigator.feature"/>
<import feature="org.jboss.tools.runtime.drools.detector.feature"/>
<import feature="org.jboss.tools.runtime.jbpm.detector.feature"/>
<!--
<import feature="org.fusesource.ide.camel.editor.feature"/>
<import feature="org.fusesource.ide.core.feature"/>
<import feature="org.fusesource.ide.jmx.feature"/>
<import feature="org.fusesource.ide.server.extensions.feature"/>
<import feature="org.jboss.tools.fuse.transformation.feature"/>
<import feature="org.switchyard.tools.feature"/>
<import feature="org.switchyard.tools.bpel.feature"/>
<import feature="org.switchyard.tools.bpmn2.feature"/>
-->
</requires>
{code}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years, 11 months
[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ]
Rastislav Wagner commented on JBDS-4077:
----------------------------------------
[~nickboldt] We dont install on top of some eclipse - we use devstudio jar installer
I tried running mvn build with -X switch and this is org.eclipse.osgi reference from output
{code}
06:08:29 [DEBUG] org.eclipse.tycho:tycho-maven-plugin:jar:0.26.0:
06:08:29 [DEBUG] org.eclipse.tycho:tycho-core:jar:0.26.0:compile
06:08:29 [DEBUG] org.apache.maven:maven-core:jar:3.0:compile
06:08:29 [DEBUG] org.apache.maven:maven-model:jar:3.0:compile
06:08:29 [DEBUG] org.apache.maven:maven-settings:jar:3.0:compile
06:08:29 [DEBUG] org.apache.maven:maven-settings-builder:jar:3.0:compile
06:08:29 [DEBUG] org.apache.maven:maven-repository-metadata:jar:3.0:compile
06:08:29 [DEBUG] org.apache.maven:maven-artifact:jar:3.0:compile
06:08:29 [DEBUG] org.apache.maven:maven-model-builder:jar:3.0:compile
06:08:29 [DEBUG] org.apache.maven:maven-aether-provider:jar:3.0:runtime
06:08:29 [DEBUG] org.sonatype.aether:aether-impl:jar:1.7:compile
06:08:29 [DEBUG] org.sonatype.aether:aether-spi:jar:1.7:compile
06:08:29 [DEBUG] org.sonatype.aether:aether-api:jar:1.7:compile
06:08:29 [DEBUG] org.sonatype.aether:aether-util:jar:1.7:compile
06:08:29 [DEBUG] org.sonatype.sisu:sisu-inject-plexus:jar:1.4.2:compile
06:08:29 [DEBUG] org.sonatype.sisu:sisu-inject-bean:jar:1.4.2:compile
06:08:29 [DEBUG] org.sonatype.sisu:sisu-guice:jar:noaop:2.1.7:compile
06:08:29 [DEBUG] org.codehaus.plexus:plexus-interpolation:jar:1.14:compile
06:08:29 [DEBUG] org.codehaus.plexus:plexus-classworlds:jar:2.2.3:compile
06:08:29 [DEBUG] org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3:compile
06:08:29 [DEBUG] org.sonatype.plexus:plexus-cipher:jar:1.7:compile
06:08:29 [DEBUG] org.apache.maven:maven-plugin-api:jar:3.0:compile
06:08:29 [DEBUG] org.codehaus.plexus:plexus-utils:jar:3.0.7:compile
06:08:29 [DEBUG] org.codehaus.plexus:plexus-archiver:jar:2.9.1:compile
06:08:29 [DEBUG] org.codehaus.plexus:plexus-io:jar:2.4.1:compile
06:08:29 [DEBUG] commons-io:commons-io:jar:2.2:compile
06:08:29 [DEBUG] org.apache.commons:commons-compress:jar:1.9:compile
06:08:29 [DEBUG] org.eclipse.tycho:org.eclipse.osgi.compatibility.state:jar:1.0.200.v20160504-1419:compile
06:08:29 [DEBUG] org.eclipse.tycho:sisu-equinox-embedder:jar:0.26.0:compile
06:08:29 [DEBUG] org.eclipse.tycho:org.eclipse.osgi:jar:3.11.0.v20160603-1336:compile
06:08:29 [DEBUG] org.eclipse.tycho:sisu-equinox-api:jar:0.26.0:compile
06:08:29 [DEBUG] org.eclipse.tycho:tycho-metadata-model:jar:0.26.0:compile
06:08:29 [DEBUG] de.pdark:decentxml:jar:1.3:compile
06:08:29 [DEBUG] org.eclipse.tycho:tycho-embedder-api:jar:0.26.0:compile
06:08:29 [DEBUG] org.eclipse.tycho:org.eclipse.tycho.embedder.shared:jar:0.26.0:compile
06:08:29 [DEBUG] org.eclipse.tycho:org.eclipse.tycho.core.shared:jar:0.26.0:compile
06:08:29 [DEBUG] org.eclipse.tycho:tycho-p2-facade:jar:0.26.0:compile
06:08:29 [DEBUG] org.codehaus.plexus:plexus-component-annotations:jar:1.5.5:compile
06:08:29 [DEBUG] org.eclipse.tycho:org.eclipse.tycho.p2.resolver.shared:jar:0.26.0:compile
06:08:29 [DEBUG] org.eclipse.tycho:org.eclipse.tycho.p2.tools.shared:jar:0.26.0:compile
06:08:29 [DEBUG] Created new class realm maven.api
{code}
Its referencing org.eclipse.tycho:org.eclipse.osgi:jar:3.11.0.v20160603-1336:compile - the old version. You can also check it here https://github.com/eclipse/tycho/blob/master/pom.xml#L91
And i saw that it is downloaded from http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6... which is defined in parent pom.xml as TARGET_PLATFORM_VERSION_MIN https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
The next thing I tired was to run maven build with -Dtpc.version=${TARGET_PLATFORM_VERSION_MAX} and it worked! I get the correct devstudio and tests are working.
Im not sure if this is tycho's fault or default target platform version should be set MAX or is it something else ?
> Cannot run integration tests against Devstudio with latest target platform
> --------------------------------------------------------------------------
>
> Key: JBDS-4077
> URL: https://issues.jboss.org/browse/JBDS-4077
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 10.2.0.AM1
> Reporter: Jan Richter
> Assignee: Rastislav Wagner
> Priority: Blocker
> Fix For: 10.2.0.AM3
>
> Attachments: .log, jbosstools-integration-tests.log.txt.zip, no_devstudio.jpg, no_devstudio.png, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt, org.jboss.tools.deltaspike.ui.bot.test.log.txt, org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png, Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png, Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png, Screenshot_2016-10-05_10-01-32.png, shell.png, TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png
>
>
> Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards.
> A full devstudio should open when the tests are run. Instead it looks like this:
> !tpfail.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years, 11 months
[JBoss JIRA] (JBDS-4149) Could not use Maven - NoClassDefFoundError: org/slf4j/Logger
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4149?page=com.atlassian.jira.plugin.... ]
Lukáš Valach updated JBDS-4149:
-------------------------------
Attachment: eclipse.log
> Could not use Maven - NoClassDefFoundError: org/slf4j/Logger
> ------------------------------------------------------------
>
> Key: JBDS-4149
> URL: https://issues.jboss.org/browse/JBDS-4149
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.2.0.AM3
> Environment: RHEL7 64bit
> Reporter: Lukáš Valach
> Attachments: eclipse.log, rh-eclipse46-devstudio-snapshots-10_2.repo, rh-eclipse46.repo
>
>
> I am not able to use embedded Maven. When I try to run Maven clean (or whatever else) I get following error message:
> {code}
> Exception in thread "main" java.lang.NoClassDefFoundError: org/slf4j/Logger
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
> at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
> at java.lang.Class.getMethod0(Class.java:3018)
> at java.lang.Class.getMethod(Class.java:1784)
> at org.codehaus.plexus.classworlds.launcher.Launcher.getEnhancedMainMethod(Launcher.java:172)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:268)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: java.lang.ClassNotFoundException: org.slf4j.Logger
> at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
> ... 10 more
> {code}
> Standalone maven installation works fine.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years, 11 months