[JBoss JIRA] (JBIDE-26797) Invalid - 2 subsystems have been declared with the same unique id: deploymentPage.standard
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26797?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26797.
---------------------------------
Closing.
I have not seen this error.
Verified in:
AM1-v20190903-0418-B4927
> Invalid - 2 subsystems have been declared with the same unique id: deploymentPage.standard
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-26797
> URL: https://issues.jboss.org/browse/JBIDE-26797
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Reporter: Ondrej Dockal
> Assignee: André Dietisheim
> Priority: Major
> Fix For: 4.13.0.AM1
>
>
> Error after fresh start of studio or in a new workspace:
> {code}
> eclipse.buildId=12.13.0.AM1-v20190823-0757-B4854
> java.version=11.0.4
> 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 /home/odockal/workspace_12130AM1-0823_TEST -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.ide.eclipse.as.wtp.core
> Error
> Fri Aug 23 14:51:49 CEST 2019
> Errors validating Server Subsystem Model
> eclipse.buildId=12.13.0.AM1-v20190823-0757-B4854
> java.version=11.0.4
> 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 /home/odockal/workspace_12130AM1-0823_TEST -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.ide.eclipse.as.wtp.core
> Error
> Fri Aug 23 14:51:49 CEST 2019
> Invalid - 2 subsystems have been declared with the same unique id: deploymentPage.standard
> {code}
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 7 months
[JBoss JIRA] (JBIDE-26746) Deployment Page: changing location, deploys to new war but wont remove old one
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26746?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-26746:
------------------------------------------
[~jkopriva] thanks, very appreciated :)
> Deployment Page: changing location, deploys to new war 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
> Labels: deployment_page, server_adapter
> 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.13.5#713005)
6 years, 7 months
[JBoss JIRA] (JBIDE-26694) Server adapter: should be able to freely set a war name
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26694?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26694.
---------------------------------
Closing.
Verified in:
Red Hat CodeReady Studio
Version: 12.13.0.AM1
Build id: AM1-v20190901-2225-B4919
Build date: 20190901-2225
> 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.war* (webapp is accessible at *<host>/websocket-chat/*)
> !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.13.5#713005)
6 years, 7 months
[JBoss JIRA] (JBIDE-26754) Deployment Page: changing location, app not accessible
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26754?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26754.
---------------------------------
Closing.
Verified in:
Red Hat CodeReady Studio
Version: 12.13.0.AM1
Build id: AM1-v20190901-2225-B4919
Build date: 20190901-2225
> Deployment Page: changing location, app not accessible
> ------------------------------------------------------
>
> Key: JBIDE-26754
> URL: https://issues.jboss.org/browse/JBIDE-26754
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.12.0.AM1
> Reporter: Josef Kopriva
> Assignee: André Dietisheim
> Priority: Major
> Labels: server_adapter, server_adapter_editor
> Fix For: 4.13.0.AM1
>
>
> Server log:
> {code:java}
> 09:14:56,891 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.2.2.GA (WildFly Core 6.0.14.Final-redhat-00001) started in 27390ms - Started 577 of 821 services (482 services are lazy, passive or on-demand)
> 09:14:59,352 INFO [org.apache.activemq.artemis.core.server] (Thread-0 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@7ee063d)) AMQ221056: Reloading configuration: logging
> 09:14:59,352 WARN [org.apache.activemq.artemis.core.server] (Thread-0 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@7ee063d)) AMQ222276: Failed to process changes to the logging configuration file: file:/opt/eap/standalone/configuration/logging.properties
> 09:15:07,648 INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (default task-1) HHH000397: Using ASTQueryTranslatorFactory
> 09:15:31,871 WARN [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0003: Deployment of 'ROOT.war' requested, but the deployment is not present
> 09:15:31,872 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found kitchensink.war in deployment directory. To trigger deployment create a file called kitchensink.war.dodeploy
> 09:15:31,872 WARN [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0007: The deployment scanner found that the content for exploded deployment ROOT.war has been deleted, but auto-deploy/undeploy for exploded deployments is not enabled and the ROOT.war.deployed marker file for this deployment has not been removed. As a result, the deployment is not being undeployed, but resources needed by the deployment may have been deleted and application errors may occur. Deleting the ROOT.war.deployed marker file to trigger undeploy is recommended.
> 09:15:31,889 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "kitchensink.war" (runtime-name: "kitchensink.war")
> 09:15:32,012 INFO [org.jboss.as.jpa] (MSC service thread 1-1) WFLYJPA0002: Read persistence.xml for primary
> 09:15:32,013 WARN [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0091: -ds.xml file deployments are deprecated. Support may be removed in a future version.
> 09:15:32,098 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."kitchensink.war".FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit."kitchensink.war".FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "kitchensink.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:151)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> 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:155)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:144)
> ... 8 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:111)
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:245)
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:757)
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:260)
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2058)
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:260)
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2058)
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:189)
> at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.startDataSource(DsXmlDeploymentInstallProcessor.java:339)
> at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:152)
> ... 9 more
> 09:15:32,106 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "kitchensink.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"kitchensink.war\".FIRST_MODULE_USE" => "WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"kitchensink.war\"
> 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"}}
> 09:15:32,186 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "kitchensink.war" (runtime-name : "kitchensink.war")
> 09:15:32,188 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."kitchensink.war".FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "kitchensink.war"
> 09:15:35,295 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /javax.faces.resource/css/screen.css.jsf: java.lang.NullPointerException
> at com.sun.faces.application.resource.ResourceHelper$ELEvaluatingInputStream.close(ResourceHelper.java:847)
> at java.io.BufferedInputStream.close(BufferedInputStream.java:483)
> at java.nio.channels.Channels$ReadableByteChannelImpl.implCloseChannel(Channels.java:403)
> at java.nio.channels.spi.AbstractInterruptibleChannel.close(AbstractInterruptibleChannel.java:115)
> at com.sun.faces.application.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:371)
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:667)
> at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74)
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
> at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:68)
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132)
> at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
> at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
> at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
> at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1504)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1504)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1504)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1504)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1504)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:364)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> C
> {code}
> fails still on duplicated datasource:
> {code:java}
> {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"kitchensink.war\".FIRST_MODULE_USE" => "WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"kitchensink.war\"
> 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"}}
> {code}
> Deployments folder in POD contains:
> {code:java}
> README.txt ROOT.war.deployed ROOT.war.dodeploy activemq-rar.rar activemq-rar.rar.skipdeploy kitchensink.war kitchensink.war.failed
> {code}
> rsync output:
> {code:java}
> sent 1326 bytes received 20 bytes 897.33 bytes/sec
> total size is 12022119 speedup is 8931.74
> receiving file list ... done
> ROOT.war.dodeploy
> ROOT.war.isdeploying
> sent 80 bytes received 1427 bytes 1004.67 bytes/sec
> total size is 12022127 speedup is 7977.52
> receiving file list ... done
> ROOT.war.deployed
> sent 58 bytes received 1355 bytes 2826.00 bytes/sec
> total size is 12022127 speedup is 8508.23
> building file list ... done
> deleting ROOT.war/resources/gfx/wildfly_400x130.jpg
> deleting ROOT.war/resources/gfx/rhjb_eap_logo.png
> deleting ROOT.war/resources/gfx/headerbkg.png
> deleting ROOT.war/resources/gfx/bkg-blkheader.png
> deleting ROOT.war/resources/gfx/banner.png
> deleting ROOT.war/resources/gfx/asidebkg.png
> deleting ROOT.war/resources/gfx/
> deleting ROOT.war/resources/css/screen.css
> deleting ROOT.war/resources/css/
> deleting ROOT.war/resources/
> deleting ROOT.war/WEB-INF/templates/default.xhtml
> deleting ROOT.war/WEB-INF/templates/
> deleting ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/util/Resources.class
> deleting ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/util/
> deleting ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/service/MemberRegistration.class
> deleting ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/service/
> deleting ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/MemberResourceRESTService.class
> deleting ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/JaxRsActivator.class
> deleting ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/
> deleting ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/model/Member.class
> deleting ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/model/
> deleting ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberRepository.class
> deleting ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberListProducer.class
> deleting ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/
> deleting ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/controller/MemberController.class
> deleting ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/controller/
> deleting ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/
> deleting ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/
> deleting ROOT.war/WEB-INF/classes/org/jboss/as/
> deleting ROOT.war/WEB-INF/classes/org/jboss/
> deleting ROOT.war/WEB-INF/classes/org/
> deleting ROOT.war/WEB-INF/classes/META-INF/persistence.xml
> deleting ROOT.war/WEB-INF/classes/META-INF/
> deleting ROOT.war/WEB-INF/classes/import.sql
> deleting ROOT.war/WEB-INF/classes/
> deleting ROOT.war/WEB-INF/kitchensink-quickstart-ds.xml
> deleting ROOT.war/WEB-INF/faces-config.xml
> deleting ROOT.war/WEB-INF/beans.xml
> deleting ROOT.war/WEB-INF/
> deleting ROOT.war/META-INF/maven/org.jboss.eap.quickstarts/kitchensink/pom.xml
> deleting ROOT.war/META-INF/maven/org.jboss.eap.quickstarts/kitchensink/pom.properties
> deleting ROOT.war/META-INF/maven/org.jboss.eap.quickstarts/kitchensink/
> deleting ROOT.war/META-INF/maven/org.jboss.eap.quickstarts/
> deleting ROOT.war/META-INF/maven/
> deleting ROOT.war/META-INF/MANIFEST.MF
> deleting ROOT.war/META-INF/
> deleting ROOT.war/index.xhtml
> deleting ROOT.war/index.html
> deleting ROOT.war/
> ROOT.war.dodeploy
> ROOT.war.isdeploying
> kitchensink.war.dodeploy
> kitchensink.war/
> kitchensink.war/index.html
> kitchensink.war/index.xhtml
> kitchensink.war/META-INF/
> kitchensink.war/META-INF/MANIFEST.MF
> kitchensink.war/META-INF/maven/
> kitchensink.war/META-INF/maven/org.jboss.eap.quickstarts/
> kitchensink.war/META-INF/maven/org.jboss.eap.quickstarts/kitchensink/
> kitchensink.war/META-INF/maven/org.jboss.eap.quickstarts/kitchensink/pom.properties
> kitchensink.war/META-INF/maven/org.jboss.eap.quickstarts/kitchensink/pom.xml
> kitchensink.war/WEB-INF/
> kitchensink.war/WEB-INF/beans.xml
> kitchensink.war/WEB-INF/faces-config.xml
> kitchensink.war/WEB-INF/kitchensink-quickstart-ds.xml
> kitchensink.war/WEB-INF/classes/
> kitchensink.war/WEB-INF/classes/import.sql
> kitchensink.war/WEB-INF/classes/META-INF/
> kitchensink.war/WEB-INF/classes/META-INF/persistence.xml
> kitchensink.war/WEB-INF/classes/org/
> kitchensink.war/WEB-INF/classes/org/jboss/
> kitchensink.war/WEB-INF/classes/org/jboss/as/
> kitchensink.war/WEB-INF/classes/org/jboss/as/quickstarts/
> kitchensink.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/
> kitchensink.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/controller/
> kitchensink.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/controller/MemberController.class
> kitchensink.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/
> kitchensink.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberListProducer.class
> kitchensink.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberRepository.class
> kitchensink.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/model/
> kitchensink.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/model/Member.class
> kitchensink.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/
> kitchensink.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/JaxRsActivator.class
> kitchensink.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/MemberResourceRESTService.class
> kitchensink.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/service/
> kitchensink.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/service/MemberRegistration.class
> kitchensink.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/util/
> kitchensink.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/util/Resources.class
> kitchensink.war/WEB-INF/templates/
> kitchensink.war/WEB-INF/templates/default.xhtml
> kitchensink.war/resources/
> kitchensink.war/resources/css/
> kitchensink.war/resources/css/screen.css
> kitchensink.war/resources/gfx/
> kitchensink.war/resources/gfx/asidebkg.png
> kitchensink.war/resources/gfx/banner.png
> kitchensink.war/resources/gfx/bkg-blkheader.png
> kitchensink.war/resources/gfx/headerbkg.png
> kitchensink.war/resources/gfx/rhjb_eap_logo.png
> kitchensink.war/resources/gfx/wildfly_400x130.jpg
> sent 106775 bytes received 796 bytes 71714.00 bytes/sec
> total size is 12022135 speedup is 111.76
> {code}
> Suspicious part in rsync:
> {code:java}
> ROOT.war.dodeploy
> ROOT.war.isdeploying
> {code}
> after deleting ROOT.war
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 7 months
[JBoss JIRA] (JBIDE-26746) Deployment Page: changing location, deploys to new war but wont remove old one
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26746?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26746.
---------------------------------
Works as expected.
Good job [~adietish]!
Verified in:
Red Hat CodeReady Studio
Version: 12.13.0.AM1
Build id: AM1-v20190901-2225-B4919
Build date: 20190901-2225
> Deployment Page: changing location, deploys to new war 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
> Labels: deployment_page, server_adapter
> 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.13.5#713005)
6 years, 7 months
[JBoss JIRA] (JBIDE-26714) Change all occurences of OpenShift 3 by OpenShift
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26714?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26714.
---------------------------------
I have not found any occurrences of OpenShift 3.
Closing.
Verified in:
Red Hat CodeReady Studio
Version: 12.13.0.AM1
Build id: AM1-v20190901-2225-B4919
Build date: 20190901-2225
> Change all occurences of OpenShift 3 by OpenShift
> -------------------------------------------------
>
> Key: JBIDE-26714
> URL: https://issues.jboss.org/browse/JBIDE-26714
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.12.0.Final
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.13.0.AM1
>
>
> Now that JBoss Tools supports OCP4 in the same way that OCP3, we should replace all occurence of OpenShift 3 by OpenShift
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 7 months
[JBoss JIRA] (JBIDE-26744) Server adapter: "Clean" required after changing the war name
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26744?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26744.
---------------------------------
Works as expected.
Verified in:
Red Hat CodeReady Studio
Version: 12.13.0.AM1
Build id: AM1-v20190901-2225-B4919
Build date: 20190901-2225
> Server adapter: "Clean" required after changing the war name
> ------------------------------------------------------------
>
> Key: JBIDE-26744
> URL: https://issues.jboss.org/browse/JBIDE-26744
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Major
> Labels: server_adapter
> Fix For: 4.13.0.AM1
>
>
> *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
> # EXEC: open the server adapter editor and switch to "Deployment" Tag
> # EXEC: edit "Deployment Location"
> *Result*:
> Server adapter is syncing, but in the "Console" you dont see new files being transferred
> *Expected Result*:
> As soon as a new deployment location is set, the new destination should be synced to the pod.
> *Workaround*:
> "Clean" the server adapter.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 7 months
[JBoss JIRA] (JBIDE-24498) Deploy Docker Image wizard: results dialog is not very informative
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-24498?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-24498.
---------------------------------
Closing, dialog is improved.
Verified in:
Red Hat CodeReady Studio
Version: 12.13.0.AM1
Build id: AM1-v20190901-2225-B4919
Build date: 20190901-2225
> Deploy Docker Image wizard: results dialog is not very informative
> ------------------------------------------------------------------
>
> Key: JBIDE-24498
> URL: https://issues.jboss.org/browse/JBIDE-24498
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Major
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.13.0.AM1
>
> Attachments: image-2017-05-23-11-07-21-461.png, pod-deploy-failed.png, pod-deploy-failed.png, resource-summary-dialog.png
>
>
> steps to reproduce:
> # ASSERT: have a docker connection
> # ASSERT: have an OpenShift connection
> # EXEC: in "Docker Explorer": select an image and pick "Deploy to OpenShift..."
> # ASSERT: deploy docker image wizard pops up
> # EXEC: provide settings and finish the wizard
> Result:
> A dialog pops up informing you about the result of your deployment.
> !image-2017-05-23-11-07-21-461.png!
> But the dialog is not very informative, it's far from obvious what the different informations are all about:
> * If there's an error deploying (ex. you have chosen to "Push to the registry" but the registry is not reachable from the local docker daemon that holds the image that you want to deploy) the error is displayed in the title area. It's not visible at first sight that it's an error. Only by reading you're discovering it. (ex. add an error decorator)
> * There's a list of items. Nothing in the dialog tells the user what these items are.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 7 months