[JBoss JIRA] (JBIDE-26745) Content.xml not found trying to install from Eclipse marketplace
by Ariel Barboza (Jira)
[ https://issues.jboss.org/browse/JBIDE-26745?page=com.atlassian.jira.plugi... ]
Ariel Barboza commented on JBIDE-26745:
---------------------------------------
[~jeffmaury] thank you for the prompt response, using Java 8, the odd thing is that 3 new employees did the exact same set up 1 month ago and it worked, and the new one is doing the same exact steps and that error message is failing, I manually went to that repository and I cannot find any content.xml either, it that irrelevant?. Do you think this this is only be a java issue or could it also be a proxy issue?
> Content.xml not found trying to install from Eclipse marketplace
> ----------------------------------------------------------------
>
> Key: JBIDE-26745
> URL: https://issues.jboss.org/browse/JBIDE-26745
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: marketplace
> Environment: Eclipse IDE for Enterprise Java Developers.
> Version: 2019-06 (4.12.0)
> Build id: 20190614-1200
> JBoss AS, WildFly & EAP Server Tools / Remote Systems Integration
>
> Version: 3.6.2.v20190304-1841
>
> (c) Copyright (c) Red Hat, Inc., contributors and others 2004 - 2012. All rights reserved.
> Visit http://jboss.org/tools
> Reporter: Ariel Barboza
> Priority: Major
> Attachments: ErrorLog.PNG, ErrorLog1.PNG
>
>
> When installing Eclipse, when trying to add JBoss tools plug in to add Wildfly server, it gives an installation error, saying a file "Content.xml" does not exist. Verified it was not a proxy issue, went to the directory error mentions and it is not found
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (JBIDE-26694) Server adapter: should be able to freely set a war name
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26694?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-26694:
------------------------------------------
Filed the 2nd issue where the old deployment is not removed to JBIDE-26746
> Server adapter: should be able to freely set a war name
> -------------------------------------------------------
>
> Key: JBIDE-26694
> URL: https://issues.jboss.org/browse/JBIDE-26694
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.12.0.AM1
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Major
> Labels: server_adapter
> Fix For: 4.13.0.AM1
>
> Attachments: console-output-1.png, console-output-2.png, deployment-page-edit-war-name.png, server-adapter-configuration.png, switch-location.png
>
>
> For the server adapters in tools/as we have UI that allows a user to set the name of the deployment archive. We're missing this feature for the OpenShift server adapters currently. We're asked to add it.
> Steps:
> # EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image
> # ASSERT: *websocket-chat* application is imported into your workspace
> # ASSERT: server adapter *jboss-webserver31-tomcat* is created
> # ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running)
> # EXEC: start the server adapter
> # ASSERT: RSync is executed and the output is visible in the "Console"
> Result:
> If you look closely at the output you see that the project is synced to the pod in a folder called *websocket-chat.jar*
> !console-output-1.png!
> Expected result:
> I should be able to set the output folder to anything I want. Ex. we have a customer that wants the application war to be synced up into a folder *ROOT* (without the extension *.war*).
> Currently, to achieve this I have to do the following:
> # EXEC: create the following xml snippet (notice the *outputName* property for the module)
> and make sure it reads as follows:
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <deployment>
> <local>
> <module id="org.eclipse.jst.jee.server:websocket-chat">
> <property key="tempLocation" value="" />
> <property key="location" value="" />
> <property key="outputName" value="ROOT" />
> </module>
> </local>
> </deployment>
> {code}
> # EXEC: html-encode, join it into a single line and copy it (into the clipboard)
> # EXEC: open the properties for the server adapter and hit "Switch Location"
> !switch-location.png!
> # ASSERT: in my workspace, a new project *Servers* is created. It contains the configuration for my server adapter.
> !server-adapter-configuration.png!
> # EXEC: open the file with the *XML Editor*
> # EXEC: in your *XML Editor*: go to the end of the line *<server auto-publish-setting="2"* and insert your html-encoded xml as a value to the attribute *org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="*
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <server auto-publish-setting="2" auto-publish-time="2" hostname="jboss-webserver31-tomcat-test.192.168.64.76.nip.io" id="test@jboss-webserver31-tomcat" id-set="true" name="jboss-webserver31-tomcat (Service) at OpenShift 3 (192.168.64.76)" org.jboss.ide.eclipse.as.core.server.IGNORE_LAUNCH_COMMANDS="true" org.jboss.ide.eclipse.as.core.server.deployDirectoryType="custom" org.jboss.ide.eclipse.as.core.server.serverMode="openshift3" org.jboss.ide.eclipse.as.core.server.webPort="80" org.jboss.ide.eclipse.as.core.server.webPortAutoDetect="false" org.jboss.ide.eclipse.as.core.server.zipDeploymentsPreference="true" org.jboss.tools.openshift.Connection="https://developer@192.168.64.76:8443" org.jboss.tools.openshift.DeployProject="websocket-chat" org.jboss.tools.openshift.PodPath="/opt/webserver/webapps" org.jboss.tools.openshift.SERVER_START_ON_CREATION="false" org.jboss.tools.openshift.Service="test@jboss-webserver31-tomcat" org.jboss.tools.openshift.SourcePath="${workspace_loc:/websocket-chat}" port="80" runtime-id="test@jboss-webserver31-tomcat" server-type="org.jboss.tools.openshift.server.type" server-type-id="org.jboss.tools.openshift.server.type" start-timeout="450" stop-timeout="450" timestamp="2" org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="<?xml version="1.0" encoding="UTF-8"?> <deployment> <local> <module id="org.eclipse.jst.jee.server:websocket-chat"> <property key="tempLocation" value="" /> <property key="location" value="" /> <property key="outputName" value="ROOT" /> </module> </local> </deployment>">
> <list key="modules" value0="websocket-chat::org.eclipse.jst.jee.server:websocket-chat::jst.web::3.0"/>
> </server>
> {code}
> # EXEC: Save the editor and restart the server
> Result:
> Syncing now happens into a folder *ROOT*
> !console-output-2.png!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (JBIDE-26746) Deployment Page: changing location, deploys to new jar but wont remove old one
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26746?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26746:
-------------------------------------
Fix Version/s: 4.13.0.AM1
> Deployment Page: changing location, deploys to new jar but wont remove old one
> ------------------------------------------------------------------------------
>
> Key: JBIDE-26746
> URL: https://issues.jboss.org/browse/JBIDE-26746
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Major
> Fix For: 4.13.0.AM1
>
>
> steps:
> # EXEC: Create application based on "eap72-basic-s2i" template & import source & create server adapter
> # ASSERT: application is running, server adapter created.
> # EXEC: open server editor, switch to "Deployment" tag and change the value in "Deployment Location" to "ROOT" & save editor
> # EXEC: start the server adapter
> # ASSERT: Console: adapter rsyncs local project into a folder "ROOT" on the pod.
> # EXEC: open the application log for the pod
> Result:
> the new deployment was picked up but failed with an error:
> ```
> [0m[31m15:42:29,955 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "ROOT"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS
> at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:154)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
> ... 5 more
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source."jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS".statistics is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768)
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555)
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555)
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
> at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.startDataSource(DsXmlDeploymentInstallProcessor.java:338)
> at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:151)
> ... 6 more
> [0m[31m15:42:29,958 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "ROOT")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.ROOT.FIRST_MODULE_USE" => "WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"ROOT\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.\"jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS\".statistics is already registered"}}
> [0m[0m15:42:30,001 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "ROOT" (runtime-name : "ROOT")
> [0m[0m15:42:30,001 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "ROOT"
> ```
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (JBIDE-26746) Deployment Page: changing location, deploys to new jar but wont remove old one
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26746?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26746:
-------------------------------------
Description:
steps:
# EXEC: Create application based on "eap72-basic-s2i" template & import source & create server adapter
# ASSERT: application is running, server adapter created.
# EXEC: open server editor, switch to "Deployment" tag and change the value in "Deployment Location" to "ROOT" & save editor
# EXEC: start the server adapter
# ASSERT: Console: adapter rsyncs local project into a folder "ROOT" on the pod.
# EXEC: open the application log for the pod
Result:
the new deployment was picked up but failed with an error:
{code}
[0m[31m15:42:29,955 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "ROOT"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS
at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:154)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
... 5 more
Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source."jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS".statistics is already registered
at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768)
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555)
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555)
at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.startDataSource(DsXmlDeploymentInstallProcessor.java:338)
at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:151)
... 6 more
[0m[31m15:42:29,958 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "ROOT")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.ROOT.FIRST_MODULE_USE" => "WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"ROOT\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS
Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.\"jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS\".statistics is already registered"}}
[0m[0m15:42:30,001 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "ROOT" (runtime-name : "ROOT")
[0m[0m15:42:30,001 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "ROOT"
{code}
was:
steps:
# EXEC: Create application based on "eap72-basic-s2i" template & import source & create server adapter
# ASSERT: application is running, server adapter created.
# EXEC: open server editor, switch to "Deployment" tag and change the value in "Deployment Location" to "ROOT" & save editor
# EXEC: start the server adapter
# ASSERT: Console: adapter rsyncs local project into a folder "ROOT" on the pod.
# EXEC: open the application log for the pod
Result:
the new deployment was picked up but failed with an error:
```
[0m[31m15:42:29,955 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "ROOT"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS
at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:154)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
... 5 more
Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source."jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS".statistics is already registered
at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768)
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555)
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555)
at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.startDataSource(DsXmlDeploymentInstallProcessor.java:338)
at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:151)
... 6 more
[0m[31m15:42:29,958 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "ROOT")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.ROOT.FIRST_MODULE_USE" => "WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"ROOT\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS
Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.\"jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS\".statistics is already registered"}}
[0m[0m15:42:30,001 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "ROOT" (runtime-name : "ROOT")
[0m[0m15:42:30,001 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "ROOT"
```
> Deployment Page: changing location, deploys to new jar but wont remove old one
> ------------------------------------------------------------------------------
>
> Key: JBIDE-26746
> URL: https://issues.jboss.org/browse/JBIDE-26746
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Major
> Fix For: 4.13.0.AM1
>
>
> steps:
> # EXEC: Create application based on "eap72-basic-s2i" template & import source & create server adapter
> # ASSERT: application is running, server adapter created.
> # EXEC: open server editor, switch to "Deployment" tag and change the value in "Deployment Location" to "ROOT" & save editor
> # EXEC: start the server adapter
> # ASSERT: Console: adapter rsyncs local project into a folder "ROOT" on the pod.
> # EXEC: open the application log for the pod
> Result:
> the new deployment was picked up but failed with an error:
> {code}
> [0m[31m15:42:29,955 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "ROOT"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS
> at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:154)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
> ... 5 more
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source."jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS".statistics is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768)
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555)
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555)
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
> at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.startDataSource(DsXmlDeploymentInstallProcessor.java:338)
> at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:151)
> ... 6 more
> [0m[31m15:42:29,958 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "ROOT")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.ROOT.FIRST_MODULE_USE" => "WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"ROOT\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.\"jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS\".statistics is already registered"}}
> [0m[0m15:42:30,001 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "ROOT" (runtime-name : "ROOT")
> [0m[0m15:42:30,001 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "ROOT"
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (JBIDE-26746) Deployment Page: changing location, deploys to new jar but wont remove old one
by André Dietisheim (Jira)
André Dietisheim created JBIDE-26746:
----------------------------------------
Summary: Deployment Page: changing location, deploys to new jar but wont remove old one
Key: JBIDE-26746
URL: https://issues.jboss.org/browse/JBIDE-26746
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.13.0.AM1
Reporter: André Dietisheim
steps:
# EXEC: Create application based on "eap72-basic-s2i" template & import source & create server adapter
# ASSERT: application is running, server adapter created.
# EXEC: open server editor, switch to "Deployment" tag and change the value in "Deployment Location" to "ROOT" & save editor
# EXEC: start the server adapter
# ASSERT: Console: adapter rsyncs local project into a folder "ROOT" on the pod.
# EXEC: open the application log for the pod
Result:
the new deployment was picked up but failed with an error:
```
[0m[31m15:42:29,955 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "ROOT"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS
at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:154)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
... 5 more
Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source."jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS".statistics is already registered
at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768)
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555)
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555)
at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.startDataSource(DsXmlDeploymentInstallProcessor.java:338)
at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:151)
... 6 more
[0m[31m15:42:29,958 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "ROOT")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.ROOT.FIRST_MODULE_USE" => "WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"ROOT\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS
Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.\"jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS\".statistics is already registered"}}
[0m[0m15:42:30,001 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "ROOT" (runtime-name : "ROOT")
[0m[0m15:42:30,001 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "ROOT"
```
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (JBIDE-26746) Deployment Page: changing location, deploys to new jar but wont remove old one
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26746?page=com.atlassian.jira.plugi... ]
André Dietisheim reassigned JBIDE-26746:
----------------------------------------
Assignee: André Dietisheim
> Deployment Page: changing location, deploys to new jar but wont remove old one
> ------------------------------------------------------------------------------
>
> Key: JBIDE-26746
> URL: https://issues.jboss.org/browse/JBIDE-26746
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Major
>
> steps:
> # EXEC: Create application based on "eap72-basic-s2i" template & import source & create server adapter
> # ASSERT: application is running, server adapter created.
> # EXEC: open server editor, switch to "Deployment" tag and change the value in "Deployment Location" to "ROOT" & save editor
> # EXEC: start the server adapter
> # ASSERT: Console: adapter rsyncs local project into a folder "ROOT" on the pod.
> # EXEC: open the application log for the pod
> Result:
> the new deployment was picked up but failed with an error:
> ```
> [0m[31m15:42:29,955 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "ROOT"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS
> at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:154)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
> ... 5 more
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source."jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS".statistics is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768)
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555)
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555)
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
> at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.startDataSource(DsXmlDeploymentInstallProcessor.java:338)
> at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:151)
> ... 6 more
> [0m[31m15:42:29,958 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "ROOT")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.ROOT.FIRST_MODULE_USE" => "WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"ROOT\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.\"jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS\".statistics is already registered"}}
> [0m[0m15:42:30,001 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "ROOT" (runtime-name : "ROOT")
> [0m[0m15:42:30,001 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "ROOT"
> ```
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (JBIDE-26745) Content.xml not found trying to install from Eclipse marketplace
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26745?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-26745:
------------------------------------
Which version of Java are you using. The real error is about the HTTPS connection which has been rejected. Pre Java11 (9 and 10) has some issues with HTTPS. I was able to install JBoss Tools on 2019-96 on my laptop
> Content.xml not found trying to install from Eclipse marketplace
> ----------------------------------------------------------------
>
> Key: JBIDE-26745
> URL: https://issues.jboss.org/browse/JBIDE-26745
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: marketplace
> Environment: Eclipse IDE for Enterprise Java Developers.
> Version: 2019-06 (4.12.0)
> Build id: 20190614-1200
> JBoss AS, WildFly & EAP Server Tools / Remote Systems Integration
>
> Version: 3.6.2.v20190304-1841
>
> (c) Copyright (c) Red Hat, Inc., contributors and others 2004 - 2012. All rights reserved.
> Visit http://jboss.org/tools
> Reporter: Ariel Barboza
> Priority: Major
> Attachments: ErrorLog.PNG, ErrorLog1.PNG
>
>
> When installing Eclipse, when trying to add JBoss tools plug in to add Wildfly server, it gives an installation error, saying a file "Content.xml" does not exist. Verified it was not a proxy issue, went to the directory error mentions and it is not found
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (JBIDE-26745) Content.xml not found trying to install from Eclipse marketplace
by Ariel Barboza (Jira)
Ariel Barboza created JBIDE-26745:
-------------------------------------
Summary: Content.xml not found trying to install from Eclipse marketplace
Key: JBIDE-26745
URL: https://issues.jboss.org/browse/JBIDE-26745
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: marketplace
Environment: Eclipse IDE for Enterprise Java Developers.
Version: 2019-06 (4.12.0)
Build id: 20190614-1200
JBoss AS, WildFly & EAP Server Tools / Remote Systems Integration
Version: 3.6.2.v20190304-1841
(c) Copyright (c) Red Hat, Inc., contributors and others 2004 - 2012. All rights reserved.
Visit http://jboss.org/tools
Reporter: Ariel Barboza
Attachments: ErrorLog.PNG, ErrorLog1.PNG
When installing Eclipse, when trying to add JBoss tools plug in to add Wildfly server, it gives an installation error, saying a file "Content.xml" does not exist. Verified it was not a proxy issue, went to the directory error mentions and it is not found
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (JBDS-4782) Prepare Doc/Tests for Level 2 Interop testing with RHEL
by Josef Kopriva (Jira)
Josef Kopriva created JBDS-4782:
-----------------------------------
Summary: Prepare Doc/Tests for Level 2 Interop testing with RHEL
Key: JBDS-4782
URL: https://issues.jboss.org/browse/JBDS-4782
Project: Red Hat CodeReady Studio (devstudio)
Issue Type: Epic
Components: integration-tests
Affects Versions: 12.13.0.AM1
Reporter: Josef Kopriva
Assignee: Josef Kopriva
We need to prepare doc and review tests for Interop Level 2 testing with RHEL.
Testing of CRS should be documented for PIT QE.
Doc deadline: TBD
Timeframe: 10/8-11/4
Selected test suites:
1) CR Studio installer tests
2) EAP compatibility test suite
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months