[JBoss JIRA] (JBIDE-24301) Error while building jbosstools-openshift-4.4.3
by jyoti tumsare (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24301?page=com.atlassian.jira.plugi... ]
jyoti tumsare commented on JBIDE-24301:
---------------------------------------
I tried what you said.. after that I got Error
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.tools.jmx.core.test.DefaultProviderTest
[error] Error: Exception thrown by the agent
[error] : java.rmi.server.ExportException: Port already in use: 9999; nested exception is:
java.net.BindException: Address already in use: JVM_Bind
Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 13.475 sec <<< FAILURE! - in org.jboss.tools.jmx.core.test.DefaultProviderTest
testConnection(org.jboss.tools.jmx.core.test.DefaultProviderTest) Time elapsed: 13.406 sec <<< ERROR!
java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: non-JRMP server at remote endpoint]
at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
at sun.rmi.server.UnicastRef.newCall(Unknown Source)
at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
at com.sun.jndi.rmi.registry.RegistryContext.lookup(Unknown Source)
at com.sun.jndi.toolkit.url.GenericURLContext.lookup(Unknown Source)
at javax.naming.InitialContext.lookup(Unknown Source)
at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(Unknown Source)
at javax.management.remote.rmi.RMIConnector.findRMIServer(Unknown Source)
at javax.management.remote.rmi.RMIConnector.connect(Unknown Source)
at javax.management.remote.JMXConnectorFactory.connect(Unknown Source)
at org.jboss.tools.jmx.core.providers.DefaultConnectionWrapper.connect(DefaultConnectionWrapper.java:78)
at org.jboss.tools.jmx.core.test.DefaultProviderTest.testConnection(DefaultProviderTest.java:131)
testProviderExists(org.jboss.tools.jmx.core.test.DefaultProviderTest) Time elapsed: 0 sec
testExtensionExists(org.jboss.tools.jmx.core.test.DefaultProviderTest) Time elapsed: 0 sec
Running org.jboss.tools.jmx.core.test.ErrorRootTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec - in org.jboss.tools.jmx.core.test.ErrorRootTest
testErrorRootConstructor(org.jboss.tools.jmx.core.test.ErrorRootTest) Time elapsed: 0.001 sec
Running org.jboss.tools.jmx.core.test.ImpactTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in org.jboss.tools.jmx.core.test.ImpactTest
testImpactParseInt(org.jboss.tools.jmx.core.test.ImpactTest) Time elapsed: 0 sec
Running org.jboss.tools.jmx.core.test.JMXExceptionTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in org.jboss.tools.jmx.core.test.JMXExceptionTest
testJMXExceptionGetStatus(org.jboss.tools.jmx.core.test.JMXExceptionTest) Time elapsed: 0 sec
Running org.jboss.tools.jmx.core.test.NodeBuilderTestCase
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec - in org.jboss.tools.jmx.core.test.NodeBuilderTestCase
testOneObjectName(org.jboss.tools.jmx.core.test.NodeBuilderTestCase) Time elapsed: 0.016 sec
testHierarchy(org.jboss.tools.jmx.core.test.NodeBuilderTestCase) Time elapsed: 0 sec
testTwoDifferentDomains(org.jboss.tools.jmx.core.test.NodeBuilderTestCase) Time elapsed: 0 sec
testTwoObjectNames(org.jboss.tools.jmx.core.test.NodeBuilderTestCase) Time elapsed: 0 sec
Results :
Tests in error:
DefaultProviderTest.testConnection:131 » IO Failed to retrieve RMIServer stub:...
Tests run: 10, Failures: 0, Errors: 1, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] jbosstools-server .................................. SUCCESS [ 0.069 s]
[INFO] archives.all ....................................... SUCCESS [ 0.015 s]
[INFO] archives.plugins ................................... SUCCESS [ 0.000 s]
[INFO] org.jboss.tools.archives.scanner ................... SUCCESS [ 1.589 s]
[INFO] org.jboss.ide.eclipse.archives.core ................ SUCCESS [ 2.450 s]
[INFO] org.jboss.ide.eclipse.archives.ui .................. SUCCESS [ 1.490 s]
[INFO] org.jboss.ide.eclipse.archives.jdt.integration ..... SUCCESS [ 0.640 s]
[INFO] archives.features .................................. SUCCESS [ 0.016 s]
[INFO] org.jboss.tools.archives.scanner.feature ........... SUCCESS [ 0.134 s]
[INFO] org.jboss.ide.eclipse.archives.feature ............. SUCCESS [ 0.198 s]
[INFO] org.jboss.ide.eclipse.archives.test.feature ........ SUCCESS [ 0.069 s]
[INFO] as.all ............................................. SUCCESS [ 0.015 s]
[INFO] as.plugins ......................................... SUCCESS [ 0.000 s]
[INFO] org.jboss.ide.eclipse.as.dmr ....................... SUCCESS [ 0.248 s]
[INFO] org.jboss.ide.eclipse.as.wtp.core .................. SUCCESS [ 3.435 s]
[INFO] org.jboss.ide.eclipse.as.management.core ........... SUCCESS [ 0.631 s]
[INFO] jmx.all ............................................ SUCCESS [ 0.000 s]
[INFO] jmx.plugins ........................................ SUCCESS [ 0.000 s]
[INFO] org.jboss.tools.jmx.core ........................... SUCCESS [ 0.879 s]
[INFO] org.jboss.ide.eclipse.as.core ...................... SUCCESS [ 4.668 s]
[INFO] org.jboss.tools.jmx.ui ............................. SUCCESS [ 3.513 s]
[INFO] org.jboss.ide.eclipse.as.wtp.ui .................... SUCCESS [ 1.241 s]
[INFO] org.jboss.tools.as.runtimes.integration ............ SUCCESS [ 0.966 s]
[INFO] org.jboss.ide.eclipse.as.ui ........................ SUCCESS [ 4.627 s]
[INFO] org.jboss.ide.eclipse.as.classpath.core ............ SUCCESS [ 1.115 s]
[INFO] org.jboss.ide.eclipse.archives.webtools ............ SUCCESS [ 1.410 s]
[INFO] org.jboss.ide.eclipse.as.classpath.ui .............. SUCCESS [ 1.056 s]
[INFO] org.jboss.ide.eclipse.as.doc.user .................. SUCCESS [ 0.062 s]
[INFO] org.jboss.ide.eclipse.as.ui.mbeans ................. SUCCESS [ 1.081 s]
[INFO] org.jboss.ide.eclipse.as.rse.core .................. SUCCESS [ 0.802 s]
[INFO] org.jboss.ide.eclipse.as.rse.ui .................... SUCCESS [ 1.093 s]
[INFO] org.jboss.tools.jmx.jvmmonitor.core ................ SUCCESS [ 0.870 s]
[INFO] org.jboss.tools.jmx.jvmmonitor.tools ............... SUCCESS [ 0.317 s]
[INFO] org.jboss.tools.jmx.jvmmonitor.ui .................. SUCCESS [ 3.899 s]
[INFO] org.jboss.ide.eclipse.as.jmx.integration ........... SUCCESS [ 1.047 s]
[INFO] org.jboss.ide.eclipse.as.management.as7 ............ SUCCESS [ 1.297 s]
[INFO] org.jboss.ide.eclipse.as.management.eap61plus ...... SUCCESS [ 0.618 s]
[INFO] org.jboss.ide.eclipse.as.management.wildfly9 ....... SUCCESS [ 0.600 s]
[INFO] org.jboss.tools.as.catalog ......................... SUCCESS [ 0.533 s]
[INFO] org.jboss.tools.jmx.local .......................... SUCCESS [ 0.532 s]
[INFO] org.jboss.tools.jmx.jolokia ........................ SUCCESS [ 0.801 s]
[INFO] jmx.tests .......................................... SUCCESS [ 0.000 s]
[INFO] org.jboss.tools.jmx.core.test ...................... FAILURE [ 19.140 s]
[INFO] org.jboss.tools.jmx.ui.test ........................ SKIPPED
[INFO] jmx.features ....................................... SKIPPED
[INFO] org.jboss.tools.jmx.feature ........................ SKIPPED
[INFO] org.jboss.tools.jmx.test.feature ................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:57 min
[INFO] Finished at: 2017-05-15T18:59:02+05:30
[INFO] Final Memory: 219M/805M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test (default-test) on project org.jboss.tools.jmx.core.test: There are test failures.
[ERROR]
[ERROR] Please refer to C:\jbosstools-server-4.4.3.x\jbosstools-server-jbosstools-4.4.3.x\jmx\tests\org.jboss.tools.jmx.core.test\target\surefire-reports for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :org.jboss.tools.jmx.core.test
> Error while building jbosstools-openshift-4.4.3
> -----------------------------------------------
>
> Key: JBIDE-24301
> URL: https://issues.jboss.org/browse/JBIDE-24301
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, openshift
> Affects Versions: 4.4.3.Final
> Reporter: jyoti tumsare
> Assignee: Dmitrii Bocharov
> Fix For: 4.4.4.Final
>
> Attachments: Error.PNG, issues.PNG, issues.txt, jboss-build.png, jbosstools-build.png, org.jboss.ide.eclipse.as.management.as7.png, target-platform.png
>
>
> To build jbosstools-openshift-4.4.3 I followed following steps
> 1. I clone jbosstools-base and jbosstools-server which are required for the building jbosstools-openshift-4.4.3.
> 2. while executing the jbosstools-base I got error "Missing requirement: org.jboss.tools.common.core 3.8.3.qualifier requires 'bundle org.jboss.tools.foundation.core 1.3.3' but it could not be found".
> 3. I build the org.jboss.tools.foundation.core 1.3.3 plugin and add into eclipse plugin folder and restart the eclipse IDE still facing the isuue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24340) CDK3 tools works behind proxy - Test case
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24340?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-24340:
----------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.4.4.Final)
> CDK3 tools works behind proxy - Test case
> -----------------------------------------
>
> Key: JBIDE-24340
> URL: https://issues.jboss.org/browse/JBIDE-24340
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: cdk, docker, openshift
> Affects Versions: 4.4.4.Final
> Environment: Linux (Fedora), Mac OS, Windows
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Fix For: 4.5.0.AM1
>
> Attachments: create_proxy-test_env.sh
>
>
> It is still impossible to test CDK 3 on central-ci and so, it is willing to test CDK 3 tools operated from devstudio via usage of proxy system settings on local machines.
> Steps to follow:
> 1. Setup local firewall/network rules to simulate that machine resides in restricted network and requires proxy to utilize CDK3 features. ( [^create_proxy-test_env.sh] )
> 2. Download/install devstudio
> 3. Download CDK3 minishift binary and prepare the environemnt (run minishift setup-cdk)
> 4. ASSERT: Cannot subscribe minishift-rhel image during minishift start, can be done via cli
> 4. Set env. variable MINISHIFT_HTTP(S)_PROXY
> 5. Start devstudio, add new Container Development Environement server
> 6. Start server adapter
> 7. ASSERT: CDK tools are working properly - CDK started successfully
> * rhel-image was subscribed
> * docker image pulled
> * log into openshift
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24076) NullPointerException in JaxrsApplicationCreationWizardPage.getWebxmlResource
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24076?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-24076:
-------------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.4.4.Final)
> NullPointerException in JaxrsApplicationCreationWizardPage.getWebxmlResource
> ----------------------------------------------------------------------------
>
> Key: JBIDE-24076
> URL: https://issues.jboss.org/browse/JBIDE-24076
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Reporter: Automated Error Reporting Bot
> Assignee: Dmitrii Bocharov
> Fix For: 4.5.0.AM1
>
>
> The following problem was reported via the automated error reporting:
> Message: Unhandled event loop exception
> java.lang.NullPointerException: null
> at org.jboss.tools.ws.jaxrs.ui.wizards.JaxrsApplicationCreationWizardPage.getWebxmlResource(JaxrsApplicationCreationWizardPage.java:596)
> at org.jboss.tools.ws.jaxrs.ui.wizards.JaxrsApplicationCreationWizard.performFinish(JaxrsApplicationCreationWizard.java:84)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:790)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:423)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> Bundles:
> | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 |
> | org.eclipse.swt | 3.105.1.v20160907-0248 | 3.105.1.v20160907-0248 |
> | org.jboss.tools.ws.jaxrs.ui | 1.9.1.v20160608-0648 | 1.9.2.v20160922-1835 |
> Operating Systems:
> | Linux | 3.13.0 | 3.13.0 |
> | Windows | 10.0.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/581152c0e4b00cfabf9... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-23136:
-------------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.4.4.Final)
> Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-23136
> URL: https://issues.jboss.org/browse/JBIDE-23136
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Marián Labuda
> Assignee: Dmitrii Bocharov
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.5.0.AM1
>
> Attachments: FedoraImageStream.png, ImagesWithDigest.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png
>
>
> I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see:
> 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB
> Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411
> Steps to reproduce:
> - have a project with a file named {{Dockerfile}} with the following content (1 line):
> {code}
> FROM fedora:latest
> {code}
> - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}})
> - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}.
> - In the wizard, select the option to push the image to the registry (add a dummy port if needed)
> - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22969?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22969:
-------------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.4.4.Final)
> Make sure OpenShift Tools support proxies
> -----------------------------------------
>
> Key: JBIDE-22969
> URL: https://issues.jboss.org/browse/JBIDE-22969
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Reporter: Alexey Kazakov
> Assignee: Dmitrii Bocharov
> Fix For: 4.5.0.AM1
>
> Attachments: proxy_settings.png, proxy_settings_2.png
>
>
> CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too.
> If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side.
> This issue covers:
> - testing
> - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests)
> - fixing any problems we have in OpenShift tooling regarding proxy support.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24391) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24391?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-24391.
------------------------------
Resolution: Done
> For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x
> ----------------------------------------------------------------------------
>
> Key: JBIDE-24391
> URL: https://issues.jboss.org/browse/JBIDE-24391
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
> Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in jbosstools-4.4.x
> 3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
> 6) When all complete, please close (do not resolve) this issue.
>
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
> See also: JBDS-4385
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months