[JBoss JIRA] (JBIDE-25297) Improve CDK itests so that user do not need to have all CDK versions downloaded himself
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25297?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-25297:
---------------------------------------
There is no more need for setting up CDK version < 3.2 and CDK 2.x, also, no need for passing minishift/vagrantfile arguments into test. Mock files added instead.
> Improve CDK itests so that user do not need to have all CDK versions downloaded himself
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-25297
> URL: https://issues.jboss.org/browse/JBIDE-25297
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests
> Affects Versions: 4.5.1.Final
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Labels: cdk
> Fix For: 4.5.3.AM1
>
>
> Add mock files that would substitute CDK 2.x Vagrantfile and CDK 3.1.1 binary for purposes of testing UI. These files will be placed in project path in resources/cdk-files.
> Let user to pass his vagrant file and cdk-3.1.1 binary path via agrument -Dvagrantfile and -Dminishift in cases where he needs to do so. This argument's values will have priority over files from resources folder.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (JBIDE-25671) Investigate and fix libvirt on F27 slaves
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25671?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-25671.
---------------------------------
Resolution: Done
Closing. MR is merged, new image is created.
> Investigate and fix libvirt on F27 slaves
> -----------------------------------------
>
> Key: JBIDE-25671
> URL: https://issues.jboss.org/browse/JBIDE-25671
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests
> Affects Versions: 4.5.3.AM1
> Environment: F27 OpenStack slave
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Fix For: 4.5.3.AM1
>
>
> Error log:
> {code:java}
> ------------------------------------------
> Started by upstream project "openshift.itests.jkopriva" build number 2
> originally caused by:
> Started by user Josef
> [EnvInject] - Loading node environment variables.
> Building remotely on fedora27-x64-large-219 (fedora27-x64-large) in workspace <https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/openshif...>
> [WS-CLEANUP] Deleting project workspace...
> Cloning the remote Git repository
> Cloning repository git@github.com:jbosstools/jbosstools-openshift.git
> > git init <https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/openshif...> # timeout=10
> Fetching upstream changes from git@github.com:jbosstools/jbosstools-openshift.git
> > git --version # timeout=10
> > git fetch --tags --progress git@github.com:jbosstools/jbosstools-openshift.git +refs/heads/*:refs/remotes/origin/*
> > git config remote.origin.url git@github.com:jbosstools/jbosstools-openshift.git # timeout=10
> > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> > git config remote.origin.url git@github.com:jbosstools/jbosstools-openshift.git # timeout=10
> Fetching upstream changes from git@github.com:jbosstools/jbosstools-openshift.git
> > git fetch --tags --progress git@github.com:jbosstools/jbosstools-openshift.git +refs/heads/*:refs/remotes/origin/*
> Checking out Revision 10846ca4a5b89f306f965d1a9acdc19752c34a70 (origin/master)
> Commit message: "JBIDE-25195 ITests refactoring, removing duplicated code, Fixes for OC (#1654)"
> > git config core.sparsecheckout # timeout=10
> > git checkout -f 10846ca4a5b89f306f965d1a9acdc19752c34a70
> First time build. Skipping changelog.
> Cloning the remote Git repository
> Cloning repository https://github.com/odockal/cdk-scripts.git
> > git init <https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/openshif...> # timeout=10
> Fetching upstream changes from https://github.com/odockal/cdk-scripts.git
> > git --version # timeout=10
> > git fetch --tags --progress https://github.com/odockal/cdk-scripts.git +refs/heads/*:refs/remotes/origin/*
> > git config remote.origin.url https://github.com/odockal/cdk-scripts.git # timeout=10
> > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> > git config remote.origin.url https://github.com/odockal/cdk-scripts.git # timeout=10
> Fetching upstream changes from https://github.com/odockal/cdk-scripts.git
> > git fetch --tags --progress https://github.com/odockal/cdk-scripts.git +refs/heads/*:refs/remotes/origin/*
> Checking out Revision 5a42b90f63f5308266b67c39faf344237d7585aa (origin/master)
> Commit message: "Merge pull request #20 from odockal/fix-virt-win7"
> > git config core.sparsecheckout # timeout=10
> > git checkout -f 5a42b90f63f5308266b67c39faf344237d7585aa
> First time build. Skipping changelog.
> Run condition [Boolean condition] enabling prebuild for step [BuilderChain]
> Starting xvnc
> [fedora27-x64-large] $ /usr/bin/vncserver :68 -geometry 1280x720
> New 'fedora27-x64-large-219.localdomain:68 (hudson)' desktop is fedora27-x64-large-219.localdomain:68
> Creating default startup script /home/hudson/.vnc/xstartup
> Creating default config /home/hudson/.vnc/config
> Starting applications specified in /home/hudson/.vnc/xstartup
> Log file is /home/hudson/.vnc/fedora27-x64-large-219.localdomain:68.log
> [fedora27-x64-large] $ /bin/sh -xe /tmp/jenkins2084425906506295546.sh
> + ./cdk-scripts/scripts/cdk3-virt.sh
> [INFO] Virtualization is enabled on this host...
> [INFO] Script cdk3-virt is finished sucessfully...
> ++ pwd
> + CONTENT=WORKSPACE2=<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/openshif...>
> + echo WORKSPACE2=<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/openshif...>
> + HYPERVISOR=HYPERVISOR=
> + BASEFILE_NAME=BASEFILE_NAME=minishift
> ++ uname
> + [[ Linux == *Darwin* ]]
> ++ uname
> + [[ Linux == *Linux* ]]
> + HYPERVISOR=HYPERVISOR=kvm
> + echo HYPERVISOR=kvm
> + echo BASEFILE_NAME=minishift
> ++ uname
> + [[ Linux == *Linux* ]]
> + echo MINISHIFT_HTTP_PROXY=http://cdkuser:cdkpass123@10.37.161.139:3128
> + echo 'Print out env. variables containing word PROXY'
> Print out env. variables containing word PROXY
> + printenv
> + grep PROXY
> MINISHIFT_PROXY=http://cdkuser:cdkpass123@10.37.161.139:3128
> USE_PROXY=true
> MINISHIFT_PROXY_FLAG=--http-proxy
> [EnvInject] - Injecting environment variables from a build step.
> [EnvInject] - Injecting as environment variables the properties file path 'local_env.properties'
> [EnvInject] - Variables injected successfully.
> [fedora27-x64-large] $ /bin/sh -xe /tmp/jenkins4244368038443559514.sh
> + cd <https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/openshif...>
> + ./cdk3-cleanup.sh --path <https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/openshif...> --url http://cdk-builds.usersys.redhat.com/builds/weekly/16-Jan-2018.cdk-3.3.0/ -e
> [WARNING] <https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/openshif...> does not exist, will be created
> [INFO] Trying to reach http://cdk-builds.usersys.redhat.com/builds/weekly/16-Jan-2018.cdk-3.3.0/
> [INFO] URL status: 200
> [WARNING] Erase mode is on!!!
> [INFO] User's home folder is at /home/hudson
> [WARNING] Minishift home does not exist, cannot clean old minishift configuration
> + SETUP='--force '
> ++ uname
> + [[ Linux == *CYGWIN* ]]
> + ./cdk3-install.sh -u http://cdk-builds.usersys.redhat.com/builds/weekly/16-Jan-2018.cdk-3.3.0/ -p <https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/openshif...> --setup '--force '
> [INFO] Trying to reach http://cdk-builds.usersys.redhat.com/builds/weekly/16-Jan-2018.cdk-3.3.0/
> [INFO] URL status: 200
> [WARNING] <https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/openshif...> does not exist, will be created
> [INFO] Creating <https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/openshif...>
> [INFO] Basefile name is: minishift
> [INFO] Downloading minishift from http://cdk-builds.usersys.redhat.com/builds/weekly/16-Jan-2018.cdk-3.3.0/...
> [INFO] to <https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/openshif...>
> [INFO] Minishift setup-cdk --force will be called
> % Total % Received % Xferd Average Speed Time Time Time Current
> Dload Upload Total Spent Left Speed
> 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 1 459M 1 5591k 0 0 5591k 0 0:01:24 --:--:-- 0:01:24 60.6M 19 459M 19 90.4M 0 0 90.4M 0 0:00:05 0:00:01 0:00:04 83.0M 37 459M 37 174M 0 0 87.0M 0 0:00:05 0:00:02 0:00:03 83.2M 56 459M 56 260M 0 0 86.6M 0 0:00:05 0:00:03 0:00:02 84.1M 75 459M 75 346M 0 0 86.6M 0 0:00:05 0:00:04 0:00:01 84.7M 94 459M 94 432M 0 0 86.5M 0 0:00:05 0:00:05 --:--:-- 85.4M100 459M 100 459M 0 0 91.8M 0 0:00:05 0:00:05 --:--:-- 86.0M
> [INFO] Make the file executable
> [INFO] Minishift was not initialized
> [INFO] Running <https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/openshif...> setup-cdk --force
> Setting up CDK 3 on host using '/home/hudson/.minishift' as Minishift's home directory
> Copying minishift-rhel7.iso to '/home/hudson/.minishift/cache/iso/minishift-rhel7.iso'
> Copying oc to '/home/hudson/.minishift/cache/oc/v3.7.14/linux/oc'
> Creating configuration file '/home/hudson/.minishift/config/config.json'
> Creating marker file '/home/hudson/.minishift/cdk'
> Default add-ons anyuid, admin-user, xpaas, registry-route, che installed
> Default add-ons anyuid, admin-user, xpaas enabled
> CDK 3 setup complete.
> [INFO] Script cdk3-install was finished successfully
> [Boolean condition] checking [true] against [^(1|y|yes|t|true|on|run)$] (origin token: $TEST_CDK_CLI)
> Run condition [Boolean condition] enabling perform for step [BuilderChain]
> [fedora27-x64-large] $ /bin/sh -xe /tmp/jenkins5726194721206119597.sh
> + cd <https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/openshif...>
> + cd minishift
> + export MINISHIFT_USERNAME=odockal-tc
> + MINISHIFT_USERNAME=odockal-tc
> + export MINISHIFT_PASSWORD=klavesnice
> + MINISHIFT_PASSWORD=klavesnice
> + printenv
> + grep -i minishift
> MINISHIFT_PROXY=http://cdkuser:cdkpass123@10.37.161.139:3128
> BASEFILE_NAME=minishift
> CDK3_MINISHIFT_URL=http://cdk-builds.usersys.redhat.com/builds/weekly/16-...
> PWD=<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/openshif...>
> MINISHIFT_HTTP_PROXY=http://cdkuser:cdkpass123@10.37.161.139:3128
> MINISHIFT_USERNAME=odockal-tc
> MINISHIFT_PROXY_FLAG=--http-proxy
> MINISHIFT_PASSWORD=klavesnice
> + PROXY=
> + '[' true == true ']'
> + PROXY='--http-proxy http://cdkuser:cdkpass123@10.37.161.139:3128'
> + LOG=
> + '[' true == true ']'
> + LOG='--show-libmachine-logs --v=5'
> + START_PARAMETERS='--show-libmachine-logs --v=5 --http-proxy http://cdkuser:cdkpass123@10.37.161.139:3128 --skip-registration'
> + ./minishift version
> minishift v1.11.0+d7f374a
> CDK v3.3.0-1
> + ./minishift config view
> - iso-url : file:///home/hudson/.minishift/cache/iso/minishift-rhel7.iso
> - memory : 4096
> - vm-driver : kvm
> + echo 'Starting parameters: --show-libmachine-logs --v=5 --http-proxy http://cdkuser:cdkpass123@10.37.161.139:3128 --skip-registration'
> Starting parameters: --show-libmachine-logs --v=5 --http-proxy http://cdkuser:cdkpass123@10.37.161.139:3128 --skip-registration
> + ./minishift version
> minishift v1.11.0+d7f374a
> CDK v3.3.0-1
> + ./minishift start --show-libmachine-logs --v=5 --http-proxy http://cdkuser:cdkpass123@10.37.161.139:3128 --skip-registration
> -- minishift version: v1.11.0+d7f374a
> -- Starting profile 'minishift'
> -- Checking if requested hypervisor 'kvm' is supported on this platform ... OK
> -- Checking if KVM driver is installed ...
> Driver is available at /usr/local/bin/docker-machine-driver-kvm ...
> Checking driver binary is executable ... OK
> -- Checking if Libvirt is installed ... FAIL
> See the 'Setting Up the Driver Plug-in' topic (https://docs.openshift.org/latest/minishift/getting-started/setting-up-dr...) for more information
> Build step 'Conditional steps (multiple)' marked build as failure
> Terminating xvnc.
> $ /usr/bin/vncserver -kill :68
> Killing Xvnc process ID 1531
> Archiving artifacts
> Recording test results
> [PostBuildScript] - Execution post build scripts.
> [fedora27-x64-large] $ /bin/sh -xe /tmp/jenkins920568332914163715.sh
> + cd <https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/openshif...>
> + ./cdk3-stop.sh -p <https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/openshif...>
> [INFO] Trying to stop cdk with <https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/openshif...>
> [INFO] Minishift status: Does Not Exist
> [INFO] Do nothing here
> [INFO] cdk3-stop script finished successfully...{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (JBIDE-25616) Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-25616:
-----------------------------------------
it seems that the image can be pulled by anonymous users (even if they don't have access to the registry-console).
!screenshot-1.png|thumbnail!
if you can't grab it, [~tcunning] should be able to give you some rights to browse this registry and have access to it.
> Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-25616
> URL: https://issues.jboss.org/browse/JBIDE-25616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Fix For: 4.5.3.AM1
>
> Attachments: java, screenshot-1.png
>
>
> Starting of server ends with error:
> {code:java}
> eclipse.buildId=11.2.0.GA-v20180122-2025-B1884
> java.version=1.8.0_151
> 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_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Wed Jan 24 11:21:45 CET 2018
> Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com)
> org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 45933 on localhost
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100)
> 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)
6 years, 4 months
[JBoss JIRA] (JBIDE-25616) Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ]
Aurélien Pupier updated JBIDE-25616:
------------------------------------
Attachment: screenshot-1.png
> Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-25616
> URL: https://issues.jboss.org/browse/JBIDE-25616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Fix For: 4.5.3.AM1
>
> Attachments: java, screenshot-1.png
>
>
> Starting of server ends with error:
> {code:java}
> eclipse.buildId=11.2.0.GA-v20180122-2025-B1884
> java.version=1.8.0_151
> 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_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Wed Jan 24 11:21:45 CET 2018
> Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com)
> org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 45933 on localhost
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100)
> 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)
6 years, 4 months
[JBoss JIRA] (JBIDE-25674) NPE in JolokiaConnectionWrapper.extractStatus
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25674?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-25674:
-------------------------------------
After trying to craft an email for a bit, I realized we really need to know exactly what's happening in the client before I can do so. Can you trace through and get me some color on what exactly is happening before the npe? Maybe breakpoint at the J4pRemoteException constructors? We should try to find out WHY there's no response.
> NPE in JolokiaConnectionWrapper.extractStatus
> ---------------------------------------------
>
> Key: JBIDE-25674
> URL: https://issues.jboss.org/browse/JBIDE-25674
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Reporter: Aurélien Pupier
>
> {noformat}
> !ENTRY org.eclipse.core.jobs 4 2 2018-01-29 15:56:34.020
> !MESSAGE An internal error occurred during: "Connect Job".
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.extractStatus(JolokiaConnectionWrapper.java:340)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {noformat}
> I put a breakpoint in org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable() to see which exception it was and it is a "503 Service Unavailable"
> in this case the "response" is null
> 2 possibilities:
> - it is normal that it is null in this case Jboss Tools need to handle this case
> - it is not normal that it is null and in this case, it needs to be reported upstream (even if a null check might nice as a workaround for now)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (JBIDE-25674) NPE in JolokiaConnectionWrapper.extractStatus
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25674?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-25674:
-------------------------------------
Opened https://github.com/jbosstools/jbosstools-server/pull/557 for the npe.
Will investigate with upstream cdk / openshift.
> NPE in JolokiaConnectionWrapper.extractStatus
> ---------------------------------------------
>
> Key: JBIDE-25674
> URL: https://issues.jboss.org/browse/JBIDE-25674
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Reporter: Aurélien Pupier
>
> {noformat}
> !ENTRY org.eclipse.core.jobs 4 2 2018-01-29 15:56:34.020
> !MESSAGE An internal error occurred during: "Connect Job".
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.extractStatus(JolokiaConnectionWrapper.java:340)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {noformat}
> I put a breakpoint in org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable() to see which exception it was and it is a "503 Service Unavailable"
> in this case the "response" is null
> 2 possibilities:
> - it is normal that it is null in this case Jboss Tools need to handle this case
> - it is not normal that it is null and in this case, it needs to be reported upstream (even if a null check might nice as a workaround for now)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months