[JBoss JIRA] (JBIDE-25854) JMX error after start of devstudio: "Update timer canceled."
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25854?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-25854.
---------------------------------
Closing. Issue is fixed.
Verified in:
Red Hat JBoss Developer Studio
Version: 11.3.0.GA
Build id: GA-v20180410-1152-B2341
Build date: 20180410-1152
> JMX error after start of devstudio: "Update timer canceled."
> ------------------------------------------------------------
>
> Key: JBIDE-25854
> URL: https://issues.jboss.org/browse/JBIDE-25854
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.5.3.AM3
> Environment: F28 + Java8 + DevStudio 11.3.0.AM3-v20180322-1027-B2194
> Reporter: Josef Kopriva
> Assignee: Rob Stryker
> Fix For: 4.5.3.Final
>
>
> {code:java}
> eclipse.buildId=11.3.0.AM3-v20180322-1027-B2194
> java.version=1.8.0_161
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B2194_4/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.jmx.jvmmonitor.tools
> Error
> Fri Mar 23 09:53:59 CET 2018
> Update timer canceled.
> java.lang.ArrayIndexOutOfBoundsException: 0
> at org.jboss.tools.common.jdt.debug.JavaUtilities.getMajorMinor(JavaUtilities.java:55)
> at org.jboss.tools.common.jdt.debug.JavaUtilities.isJigsawRunning(JavaUtilities.java:33)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsLoader(Tools.java:110)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:101)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:69)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:60)
> at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:181)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (JBIDE-25871) Server adapter: spring-boot-camel-xml adapter cannot rsync: no rsync nor tar available
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25871?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-25871.
---------------------------------
Closing, I was also not able to reproduce same error message.
Verified in:
Red Hat JBoss Developer Studio
Version: 11.3.0.GA
Build id: GA-v20180410-1152-B2341
Build date: 20180410-1152
> Server adapter: spring-boot-camel-xml adapter cannot rsync: no rsync nor tar available
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-25871
> URL: https://issues.jboss.org/browse/JBIDE-25871
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: rsync, server_adapter, springboot
> Fix For: 4.5.3.Final
>
> Attachments: fuse-on-openshift.zip, pod-running.png, rsync-fails.png
>
>
> # ASSERT: have project *camel-ose-springboot-xml* imported to your workspace (from attached archive fuse-on-openshift)
> # ASSERT: have a connection to https://console.starter-us-east-2.openshift.com with a project *<username>-stage*
> # EXEC: deploy project *camel-ose-springboot-xml* project via fabric-8 maven plugin:
> {code}
> mvn clean install fabric8:deploy \
> -Dkubernetes.master=https://console.starter-us-east-2.openshift.com \
> -Dkubernetes.namespace=adietish-stage \
> -Dkubernetes.auth.basic.username=<username> \
> -Dkubernetes.auth.basic.password=<password> \
> -Dfabric8.mode=openshift \
> -Dkubernetes.trust.certificates=true \
> -Dfabric8.build.strategy=s2i \
> -Dkubernetes.auth.tryServiceAccount=false \
> -Dfabric8.generator.from=fabric8/s2i-java \
> -Dfabric8.generator.fromMode=docker \
> -Dkubernetes.auth.tryKubeConfig=false
> {code}
> # ASSERT: you have a pod running for a service *camel-ose-springboot-xml*
> !pod-running.png!
> # EXEC: create a server adapter for your service *camel-ose-springboot-xml*
> # ASSERT: adapter starts automatically and starts to sync local project to OpenShift
> Result:
> RSync fails, you're told that the container has no strategy for syncing, neither rsync nor tar are available.
> !rsync-fails.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (JBIDE-25672) Server adapter: spring-boot-camel-xml adapter throws "null" error when starting (open.paas.redhat.com)
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25672?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-25672.
---------------------------------
Closing: I do not get *null argument* error, but error mentioned here: JBIDE-25700
Verified in:
Red Hat JBoss Developer Studio
Version: 11.3.0.GA
Build id: GA-v20180410-1152-B2341
Build date: 20180410-1152
> Server adapter: spring-boot-camel-xml adapter throws "null" error when starting (open.paas.redhat.com)
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25672
> URL: https://issues.jboss.org/browse/JBIDE-25672
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: server_adapter
> Fix For: 4.5.3.Final
>
> Attachments: image-2018-01-29-15-48-29-101.png
>
>
> # ASSERT: have a connection to open.paas.redhat.com
> # EXEC: create a new app based on the "s2i-spring-boot-camel-xml" template. Have the project imported to your workspace and the server adapter created
> # ASSERT: a server adapter "s2i-spring-boot-camel-xml" is created
> # EXEC: wait for the adapter to get "[started]"
> Result:
> After some waiting time the adapter throws the following error:
> !image-2018-01-29-15-48-29-101.png!
> In the Eclipse log you find the following:
> {code}
> !MESSAGE Could not launch server s2i-spring-boot-camel-xml (DeploymentConfig) at OpenShift 3 (open.paas.redhat.com)
> !STACK 0
> org.eclipse.core.runtime.AssertionFailedException: null argument:
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
> at org.jboss.tools.openshift.internal.core.server.debug.DebugContext.<init>(DebugContext.java:64)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.createDebugContext(OpenShiftLaunchController.java:199)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:93)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (JBIDE-25892) Label truncated when downloading CDK runtime
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25892?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-25892:
------------------------------------
On Fedora seems the label is truncated:
!screenshot-2.png|thumbnail!
> Label truncated when downloading CDK runtime
> --------------------------------------------
>
> Key: JBIDE-25892
> URL: https://issues.jboss.org/browse/JBIDE-25892
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.3.AM3
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Labels: cdk, cdk_server_adapter, cdk_server_adapter_wizard
> Fix For: 4.5.3.Final
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> When downloading the CDK runtime, once you selected a specific CDK version the URL and a message are displayed. But the message is truncated
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-25303.
---------------------------------
Just note: project needs to be build before publishing.
Works as expected and without perm issues.
Thank you [~adietish] :)
Verified in:
Red Hat JBoss Developer Studio
Version: 11.3.0.GA
Build id: GA-v20180410-1152-B2341
Build date: 20180410-1152
> Server adapter: support hot-deployment on OpenShift for SpringBoot app
> ----------------------------------------------------------------------
>
> Key: JBIDE-25303
> URL: https://issues.jboss.org/browse/JBIDE-25303
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.1.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.3.AM3
>
> Attachments: Image+Pasted+at+2018-1-16+10-58.png, docker-explorer-inspect-image.png, fuse-on-openshift.zip, project-deployment-assembly.png, screenshot-1.png, spring-boot-demo.zip
>
>
> currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file.
> The requirements are:
> - rsync unpacked jar
> - rsync without the jar name as folder
> - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated)
> use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools":
> - there is a SpringBoot app deployed on OpenShift
> - the developer want to develop evolution of the SpringBoot app
> -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance
> -- Remote java debug should be available when the OpenShift server adapter is in debug mode.
> Steps:
> # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot)
> # EXEC: Import project within fuse-on-openshift.zip into your workspace
> # EXEC: open launch configuration and change:
> ** -Dkubernetes.master= so that it first your cdk instance
> ** -Dkubernetes.namespace= to the name of the project that you create in step 1.
> ** -Dfabric8.generator.from=fabric8/s2i-java
> # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk)
> # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running.
> # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service)
> # ASSERT: server adapter is created and is *[started]*
> # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service)
> # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end
> {code}
> simple-route - >>> 455
> simple-route - >>> 695
> simple-route - >>> 935
> {code}
> # EXEC: In Project Explorer: open class MyTransformer and change the transform method
> # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months