[JBoss JIRA] (JBIDE-27188) Cannot create Web Service Client using CXF 3.3.5 and wildfly 18 on Java 11
by Ondrej Dockal (Jira)
Ondrej Dockal created JBIDE-27188:
-------------------------------------
Summary: Cannot create Web Service Client using CXF 3.3.5 and wildfly 18 on Java 11
Key: JBIDE-27188
URL: https://issues.redhat.com/browse/JBIDE-27188
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.15.0.AM1
Reporter: Ondrej Dockal
When trying to create Web Service client I get:
{code}
-Djava.endorsed.dirs=/home/odockal/git/jbosstools-integration-tests/tests/org.jboss.tools.ws.ui.bot.test/target/requirements/apache-cxf-2.x/apache-cxf-3.3.5 is not supported. Endorsed standards and standalone APIs
in modular form will be supported via the concept of upgradeable modules.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (JBIDE-27187) Update JOB DSL jobs to run periodically on weekend only smoke suites on restricted matrixes
by Zbyněk Červinka (Jira)
Zbyněk Červinka created JBIDE-27187:
---------------------------------------
Summary: Update JOB DSL jobs to run periodically on weekend only smoke suites on restricted matrixes
Key: JBIDE-27187
URL: https://issues.redhat.com/browse/JBIDE-27187
Project: Tools (JBoss Tools)
Issue Type: Task
Components: integration-tests, qa
Affects Versions: 4.15.0.Final
Reporter: Zbyněk Červinka
Assignee: Zbyněk Červinka
Fix For: 4.15.x
All the following JOB DSL Jenkins jobs specification needs to be updated to run periodically on weekend only smoke suites on restricted matrixes:
* maven itests
* central itests
* all example itests
* all cdi itests (CDI 1.2 and CDI 2.0)
* deltaspike itests
* mylyn itests
* jsf itests
* batch itests
* live reload itests
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (JBIDE-27144) WildFly 19 refuses to start when added to the CodeReady Studio
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-27144?page=com.atlassian.jira.plug... ]
Josef Kopriva commented on JBIDE-27144:
---------------------------------------
PR is merged, marking this as resolved.
> WildFly 19 refuses to start when added to the CodeReady Studio
> --------------------------------------------------------------
>
> Key: JBIDE-27144
> URL: https://issues.redhat.com/browse/JBIDE-27144
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.15.0.AM1
> Reporter: Zbyněk Červinka
> Assignee: Rob Stryker
> Priority: Major
> Fix For: 4.15.0.Final
>
> Attachments: adding_wildfly.png, after_attept_to_start_wildfly.png, wf19.png
>
>
> - WildFly 19.0.0.Final acts weird during adding to the CodeReady Studio - it shows warning message
> !adding_wildfly.png|thumbnail!
> - After an attempt to start the server, the server will end in [Stopped, Synchronized] state and Console produces several errors
> !after_attept_to_start_wildfly.png|thumbnail!
> h2. Red Hat CodeReady Studio version:
> Version: 12.14.0.GA
> Build id: GA-v20200323-0744-B6101
> Build date: 20200323-0744
> h2. Console output when trying to start the WildFly 19:
> {code:java}
> 20:15:24,805 INFO [org.jboss.modules] (main) JBoss Modules version 1.10.0.Final
> 20:15:25,418 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
> 20:15:25,428 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
> 20:15:25,590 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 19.0.0.Final (WildFly Core 11.0.0.Final) starting
> 20:15:26,219 INFO [org.wildfly.security] (ServerService Thread Pool -- 28) ELY00001: WildFly Elytron version 1.11.2.Final
> 20:15:26,709 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 20:15:26,731 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 11) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 20:15:26,784 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
> 20:15:26,803 INFO [org.xnio] (MSC service thread 1-5) XNIO version 3.7.7.Final
> 20:15:26,812 INFO [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.7.7.Final
> 20:15:26,836 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 52) WFLYCLINF0001: Activating Infinispan subsystem.
> 20:15:26,841 INFO [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 61) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
> 20:15:26,852 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 66) WFLYNAM0001: Activating Naming Subsystem
> 20:15:26,858 INFO [org.jboss.as.security] (ServerService Thread Pool -- 72) WFLYSEC0002: Activating Security Subsystem
> 20:15:26,852 INFO [org.jboss.as.connector] (MSC service thread 1-3) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.20.Final)
> 20:15:26,853 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 74) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
> 20:15:26,863 INFO [org.jboss.as.security] (MSC service thread 1-5) WFLYSEC0001: Current PicketBox version=5.0.3.Final
> 20:15:26,869 INFO [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool -- 62) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
> 20:15:26,868 INFO [org.wildfly.extension.microprofile.jwt.smallrye._private] (ServerService Thread Pool -- 63) WFLYJWT0001: Activating WildFly MicroProfile JWT Subsystem
> 20:15:26,867 INFO [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 65) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
> 20:15:26,882 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 54) WFLYRS0016: RESTEasy version 3.11.0.Final
> 20:15:26,884 INFO [org.wildfly.extension.microprofile.metrics.smallrye] (ServerService Thread Pool -- 64) WFLYMETRICS0001: Activating Eclipse MicroProfile Metrics Subsystem
> 20:15:26,905 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 53) WFLYIO001: Worker 'default' has auto-configured to 24 IO threads with 192 max task threads based on your 12 available processors
> 20:15:26,909 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 76) WFLYWS0002: Activating WebServices Extension
> 20:15:26,926 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 44) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
> 20:15:26,929 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 5.0.17.Final
> 20:15:26,932 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 59) WFLYJSF0007: Activated the following JSF Implementations: [main]
> 20:15:26,938 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = h2
> 20:15:26,964 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0003: Undertow 2.0.30.Final starting
> 20:15:26,969 INFO [org.jboss.as.naming] (MSC service thread 1-6) WFLYNAM0003: Starting Naming Service
> 20:15:26,970 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
> 20:15:27,028 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 75) WFLYUT0014: Creating file handler for path '/Users/zcervink/wildfly-19.0.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
> 20:15:27,039 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server.
> 20:15:27,042 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0018: Host default-host starting
> 20:15:27,054 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 48 (per class), which is derived from the number of CPUs on this host.
> 20:15:27,054 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 192 (per class), which is derived from thread worker pool sizing.
> 20:15:27,122 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service org.wildfly.undertow.listener.default: org.jboss.msc.service.StartException in service org.wildfly.undertow.listener.default: Address already in use localhost/127.0.0.1:8080
> at org.wildfly.extension.undertow@19.0.0.Final//org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:209)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> 20:15:27,234 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0493: EJB subsystem suspension complete
> 20:15:27,284 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
> 20:15:27,451 INFO [org.jboss.as.patching] (MSC service thread 1-4) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
> 20:15:27,464 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-5) WFLYDM0111: Keystore /Users/zcervink/wildfly-19.0.0.Final/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
> 20:15:27,471 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) WFLYDS0013: Started FileSystemDeploymentService for directory /Users/zcervink/wildfly-19.0.0.Final/standalone/deployments
> 20:15:27,532 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service org.wildfly.undertow.listener.https: org.jboss.msc.service.StartException in service org.wildfly.undertow.listener.https: Address already in use localhost/127.0.0.1:8443
> at org.wildfly.extension.undertow@19.0.0.Final//org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:209)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> 20:15:27,536 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service org.wildfly.management.http.extensible: org.jboss.msc.service.StartException in service org.wildfly.management.http.extensible: java.net.BindException: Address already in use localhost/127.0.0.1:9990
> at org.jboss.as.server@11.0.0.Final//org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:391)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> 20:15:27,538 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("management-interface" => "http-interface")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.management.http.extensible" => "java.net.BindException: Address already in use localhost/127.0.0.1:9990"}}
> 20:15:27,592 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("http-listener" => "default")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.undertow.listener.default" => "Address already in use localhost/127.0.0.1:8080"}}
> 20:15:27,593 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("https-listener" => "https")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.undertow.listener.https" => "Address already in use localhost/127.0.0.1:8443"}}
> 20:15:27,594 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0459: Triggering roll back due to missing management services.
> 20:15:27,594 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("management-interface" => "http-interface")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.management.http.extensible" => "java.net.BindException: Address already in use localhost/127.0.0.1:9990"}}
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (JBIDE-27144) WildFly 19 refuses to start when added to the CodeReady Studio
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-27144?page=com.atlassian.jira.plug... ]
Josef Kopriva updated JBIDE-27144:
----------------------------------
Fix Version/s: 4.15.0.Final
(was: 4.15.x)
> WildFly 19 refuses to start when added to the CodeReady Studio
> --------------------------------------------------------------
>
> Key: JBIDE-27144
> URL: https://issues.redhat.com/browse/JBIDE-27144
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.15.0.AM1
> Reporter: Zbyněk Červinka
> Assignee: Rob Stryker
> Priority: Major
> Fix For: 4.15.0.Final
>
> Attachments: adding_wildfly.png, after_attept_to_start_wildfly.png, wf19.png
>
>
> - WildFly 19.0.0.Final acts weird during adding to the CodeReady Studio - it shows warning message
> !adding_wildfly.png|thumbnail!
> - After an attempt to start the server, the server will end in [Stopped, Synchronized] state and Console produces several errors
> !after_attept_to_start_wildfly.png|thumbnail!
> h2. Red Hat CodeReady Studio version:
> Version: 12.14.0.GA
> Build id: GA-v20200323-0744-B6101
> Build date: 20200323-0744
> h2. Console output when trying to start the WildFly 19:
> {code:java}
> 20:15:24,805 INFO [org.jboss.modules] (main) JBoss Modules version 1.10.0.Final
> 20:15:25,418 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
> 20:15:25,428 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
> 20:15:25,590 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 19.0.0.Final (WildFly Core 11.0.0.Final) starting
> 20:15:26,219 INFO [org.wildfly.security] (ServerService Thread Pool -- 28) ELY00001: WildFly Elytron version 1.11.2.Final
> 20:15:26,709 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 20:15:26,731 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 11) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 20:15:26,784 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
> 20:15:26,803 INFO [org.xnio] (MSC service thread 1-5) XNIO version 3.7.7.Final
> 20:15:26,812 INFO [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.7.7.Final
> 20:15:26,836 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 52) WFLYCLINF0001: Activating Infinispan subsystem.
> 20:15:26,841 INFO [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 61) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
> 20:15:26,852 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 66) WFLYNAM0001: Activating Naming Subsystem
> 20:15:26,858 INFO [org.jboss.as.security] (ServerService Thread Pool -- 72) WFLYSEC0002: Activating Security Subsystem
> 20:15:26,852 INFO [org.jboss.as.connector] (MSC service thread 1-3) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.20.Final)
> 20:15:26,853 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 74) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
> 20:15:26,863 INFO [org.jboss.as.security] (MSC service thread 1-5) WFLYSEC0001: Current PicketBox version=5.0.3.Final
> 20:15:26,869 INFO [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool -- 62) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
> 20:15:26,868 INFO [org.wildfly.extension.microprofile.jwt.smallrye._private] (ServerService Thread Pool -- 63) WFLYJWT0001: Activating WildFly MicroProfile JWT Subsystem
> 20:15:26,867 INFO [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 65) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
> 20:15:26,882 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 54) WFLYRS0016: RESTEasy version 3.11.0.Final
> 20:15:26,884 INFO [org.wildfly.extension.microprofile.metrics.smallrye] (ServerService Thread Pool -- 64) WFLYMETRICS0001: Activating Eclipse MicroProfile Metrics Subsystem
> 20:15:26,905 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 53) WFLYIO001: Worker 'default' has auto-configured to 24 IO threads with 192 max task threads based on your 12 available processors
> 20:15:26,909 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 76) WFLYWS0002: Activating WebServices Extension
> 20:15:26,926 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 44) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
> 20:15:26,929 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 5.0.17.Final
> 20:15:26,932 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 59) WFLYJSF0007: Activated the following JSF Implementations: [main]
> 20:15:26,938 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = h2
> 20:15:26,964 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0003: Undertow 2.0.30.Final starting
> 20:15:26,969 INFO [org.jboss.as.naming] (MSC service thread 1-6) WFLYNAM0003: Starting Naming Service
> 20:15:26,970 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
> 20:15:27,028 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 75) WFLYUT0014: Creating file handler for path '/Users/zcervink/wildfly-19.0.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
> 20:15:27,039 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server.
> 20:15:27,042 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0018: Host default-host starting
> 20:15:27,054 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 48 (per class), which is derived from the number of CPUs on this host.
> 20:15:27,054 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 192 (per class), which is derived from thread worker pool sizing.
> 20:15:27,122 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service org.wildfly.undertow.listener.default: org.jboss.msc.service.StartException in service org.wildfly.undertow.listener.default: Address already in use localhost/127.0.0.1:8080
> at org.wildfly.extension.undertow@19.0.0.Final//org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:209)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> 20:15:27,234 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0493: EJB subsystem suspension complete
> 20:15:27,284 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
> 20:15:27,451 INFO [org.jboss.as.patching] (MSC service thread 1-4) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
> 20:15:27,464 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-5) WFLYDM0111: Keystore /Users/zcervink/wildfly-19.0.0.Final/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
> 20:15:27,471 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) WFLYDS0013: Started FileSystemDeploymentService for directory /Users/zcervink/wildfly-19.0.0.Final/standalone/deployments
> 20:15:27,532 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service org.wildfly.undertow.listener.https: org.jboss.msc.service.StartException in service org.wildfly.undertow.listener.https: Address already in use localhost/127.0.0.1:8443
> at org.wildfly.extension.undertow@19.0.0.Final//org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:209)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> 20:15:27,536 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service org.wildfly.management.http.extensible: org.jboss.msc.service.StartException in service org.wildfly.management.http.extensible: java.net.BindException: Address already in use localhost/127.0.0.1:9990
> at org.jboss.as.server@11.0.0.Final//org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:391)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> 20:15:27,538 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("management-interface" => "http-interface")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.management.http.extensible" => "java.net.BindException: Address already in use localhost/127.0.0.1:9990"}}
> 20:15:27,592 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("http-listener" => "default")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.undertow.listener.default" => "Address already in use localhost/127.0.0.1:8080"}}
> 20:15:27,593 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("https-listener" => "https")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.undertow.listener.https" => "Address already in use localhost/127.0.0.1:8443"}}
> 20:15:27,594 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0459: Triggering roll back due to missing management services.
> 20:15:27,594 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("management-interface" => "http-interface")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.management.http.extensible" => "java.net.BindException: Address already in use localhost/127.0.0.1:9990"}}
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (JBIDE-27185) The "template" quickstart from Red Hat Central shows errors after import
by Jeff MAURY (Jira)
[ https://issues.redhat.com/browse/JBIDE-27185?page=com.atlassian.jira.plug... ]
Jeff MAURY commented on JBIDE-27185:
------------------------------------
This is a template quickstart, I don't think it should be presented to the user.
> The "template" quickstart from Red Hat Central shows errors after import
> ------------------------------------------------------------------------
>
> Key: JBIDE-27185
> URL: https://issues.redhat.com/browse/JBIDE-27185
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.15.0.Final
> Reporter: Zbyněk Červinka
> Priority: Major
> Fix For: 4.15.x
>
> Attachments: errors_after_import.png, quick_fix.png, show_the_quick_fix_dialog.png
>
>
> *Here are the printscreen:*
> !errors_after_import.png|thumbnail!
> *Red Hat CodeReady Studio version:*
> Version: 12.15.0.AM1
> Build id: AM1-v20200326-1404-B6119
> Build date: 20200326-1404
> Additional details - _Show the Quick Fix Dialog_ checkbox is enabled:
> !quick_fix.png|thumbnail! !show_the_quick_fix_dialog.png|thumbnail!
> *Errors in the Problems view:*
> {code:java}
> Could not read maven project jboss-QUICKSTART_NAME line 1 Maven Build Problem
> Project build error: 'dependencies.dependency.version' for javax.enterprise:cdi-api:jar is missing. pom.xml /jboss-QUICKSTART_NAME line 80 Maven pom Loading Problem
> Project build error: 'dependencies.dependency.version' for org.hibernate.javax.persistence:hibernate-jpa-2.1-api:jar is missing. pom.xml /jboss-QUICKSTART_NAME line 102 Maven pom Loading Problem
> Project build error: 'dependencies.dependency.version' for org.jboss.spec.javax.annotation:jboss-annotations-api_1.2_spec:jar is missing. pom.xml /jboss-QUICKSTART_NAME line 88 Maven pom Loading Problem
> Project build error: 'dependencies.dependency.version' for org.jboss.spec.javax.ejb:jboss-ejb-api_3.2_spec:jar is missing. pom.xml /jboss-QUICKSTART_NAME line 116 Maven pom Loading Problem
> Project build error: 'dependencies.dependency.version' for org.jboss.spec.javax.faces:jboss-jsf-api_2.2_spec:jar is missing. pom.xml /jboss-QUICKSTART_NAME line 95 Maven pom Loading Problem
> Project build error: 'dependencies.dependency.version' for org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar is missing. pom.xml /jboss-QUICKSTART_NAME line 109 Maven pom Loading Problem
> Project build error: Non-resolvable import POM: Failure to find org.jboss.spec:jboss-javaee-7.0:pom:1.0.3.Final-redhat-2 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced pom.xml /jboss-QUICKSTART_NAME line 67 Maven pom Loading Problem
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (JBIDE-27185) The "template" quickstart from Red Hat Central shows errors after import
by Jeff MAURY (Jira)
[ https://issues.redhat.com/browse/JBIDE-27185?page=com.atlassian.jira.plug... ]
Jeff MAURY reassigned JBIDE-27185:
----------------------------------
Assignee: Jeff MAURY
> The "template" quickstart from Red Hat Central shows errors after import
> ------------------------------------------------------------------------
>
> Key: JBIDE-27185
> URL: https://issues.redhat.com/browse/JBIDE-27185
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.15.0.Final
> Reporter: Zbyněk Červinka
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.15.x
>
> Attachments: errors_after_import.png, quick_fix.png, show_the_quick_fix_dialog.png
>
>
> *Here are the printscreen:*
> !errors_after_import.png|thumbnail!
> *Red Hat CodeReady Studio version:*
> Version: 12.15.0.AM1
> Build id: AM1-v20200326-1404-B6119
> Build date: 20200326-1404
> Additional details - _Show the Quick Fix Dialog_ checkbox is enabled:
> !quick_fix.png|thumbnail! !show_the_quick_fix_dialog.png|thumbnail!
> *Errors in the Problems view:*
> {code:java}
> Could not read maven project jboss-QUICKSTART_NAME line 1 Maven Build Problem
> Project build error: 'dependencies.dependency.version' for javax.enterprise:cdi-api:jar is missing. pom.xml /jboss-QUICKSTART_NAME line 80 Maven pom Loading Problem
> Project build error: 'dependencies.dependency.version' for org.hibernate.javax.persistence:hibernate-jpa-2.1-api:jar is missing. pom.xml /jboss-QUICKSTART_NAME line 102 Maven pom Loading Problem
> Project build error: 'dependencies.dependency.version' for org.jboss.spec.javax.annotation:jboss-annotations-api_1.2_spec:jar is missing. pom.xml /jboss-QUICKSTART_NAME line 88 Maven pom Loading Problem
> Project build error: 'dependencies.dependency.version' for org.jboss.spec.javax.ejb:jboss-ejb-api_3.2_spec:jar is missing. pom.xml /jboss-QUICKSTART_NAME line 116 Maven pom Loading Problem
> Project build error: 'dependencies.dependency.version' for org.jboss.spec.javax.faces:jboss-jsf-api_2.2_spec:jar is missing. pom.xml /jboss-QUICKSTART_NAME line 95 Maven pom Loading Problem
> Project build error: 'dependencies.dependency.version' for org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar is missing. pom.xml /jboss-QUICKSTART_NAME line 109 Maven pom Loading Problem
> Project build error: Non-resolvable import POM: Failure to find org.jboss.spec:jboss-javaee-7.0:pom:1.0.3.Final-redhat-2 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced pom.xml /jboss-QUICKSTART_NAME line 67 Maven pom Loading Problem
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months