[JBoss JIRA] (WFLY-9802) Minimize WildFly-specific stuff in welcome-content
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-9802?page=com.atlassian.jira.plugin.... ]
James Perkins updated WFLY-9802:
--------------------------------
Fix Version/s: 15.0.0.Final
> Minimize WildFly-specific stuff in welcome-content
> --------------------------------------------------
>
> Key: WFLY-9802
> URL: https://issues.jboss.org/browse/WFLY-9802
> Project: WildFly
> Issue Type: Task
> Components: Web (Undertow)
> Reporter: Brian Stansberry
> Priority: Major
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
>
> There are a number of welcome-content things that result in the need for overly complicated changes to convert the welcome-content for other branches (e.g. EAP).
> 1) Get rid of copyright headers.
> 2) Use HTML 5 DOCTYPE tag instead of 4.
> 3) -Rename files like wildfly.css to something generic so the same file name can be used elsewhere, just with different content.- (This is probably a bad idea as looking at the css the files are so different that they aren't really different variations of the same thing. Using the same file name will just lead to spurious merge conflicts.)
> 4) Add this:
> {code}
> <!-- proper charset -->
> <meta http-equiv="content-type" content="text/html;charset=utf-8" />
> <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" />
> {code}
> 5) Clean up various whitespace etc stuff.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11045) Jaeger remote sampler fails to deserialize response
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11045?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-11045:
---------------------------------
Fix Version/s: 15.0.0.Final
> Jaeger remote sampler fails to deserialize response
> ---------------------------------------------------
>
> Key: WFLY-11045
> URL: https://issues.jboss.org/browse/WFLY-11045
> Project: WildFly
> Issue Type: Bug
> Components: MP OpenTracing
> Affects Versions: 14.0.0.Final
> Reporter: Pavol Loffay
> Assignee: Juraci Paixão Kröhling
> Priority: Major
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
>
> JAEGER_REPORTER_LOG_SPANS=true JAEGER_SAMPLER_TYPE=remote $WILDFLY_HOME/bin/standalone.sh 1:39
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/ploffay/projects/javaee-traced-store/wildfly-14.0.1.Final
> JAVA: java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 13:39:30,432 INFO [org.jboss.modules] (main) JBoss Modules version 1.8.6.Final
> 13:39:30,861 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.3.Final
> 13:39:30,868 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.2.Final
> 13:39:30,992 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 14.0.1.Final (WildFly Core 6.0.2.Final) starting
> 13:39:31,697 INFO [org.wildfly.security] (ServerService Thread Pool -- 24) ELY00001: WildFly Elytron version 1.6.0.Final
> 13:39:32,155 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.
> 13:39:32,188 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 26) 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.
> 13:39:32,221 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 34) WFLYDR0001: Content added at location /home/ploffay/projects/javaee-traced-store/wildfly-14.0.1.Final/standalone/data/content/91/04caab3329ba82bafd92755e900187a74e536c/content
> 13:39:32,259 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
> 13:39:32,278 INFO [org.xnio] (MSC service thread 1-4) XNIO version 3.6.5.Final
> 13:39:32,290 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.6.5.Final
> 13:39:32,371 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 41) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
> 13:39:32,396 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 48) WFLYCLINF0001: Activating Infinispan subsystem.
> 13:39:32,400 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 49) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors
> 13:39:32,402 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 5.0.8.Final
> 13:39:32,435 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
> 13:39:32,444 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 50) WFLYRS0016: RESTEasy version 3.6.1.Final
> 13:39:32,478 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.11.Final)
> 13:39:32,493 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 55) WFLYJSF0007: Activated the following JSF Implementations: [main]
> 13:39:32,494 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
> 13:39:32,495 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2
> 13:39:32,506 INFO [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 57) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
> 13:39:32,508 INFO [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 59) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
> 13:39:32,531 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 60) WFLYNAM0001: Activating Naming Subsystem
> 13:39:32,545 INFO [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool -- 58) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
> 13:39:32,559 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 68) 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.
> 13:39:32,575 INFO [org.jboss.as.security] (ServerService Thread Pool -- 66) WFLYSEC0002: Activating Security Subsystem
> 13:39:32,581 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 70) WFLYWS0002: Activating WebServices Extension
> 13:39:32,589 INFO [org.jboss.as.naming] (MSC service thread 1-4) WFLYNAM0003: Starting Naming Service
> 13:39:32,592 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
> 13:39:32,617 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=5.0.3.Final
> 13:39:32,662 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 2.0.13.Final starting
> 13:39:32,670 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 128 (per class), which is derived from thread worker pool sizing.
> 13:39:32,673 INFO [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 32 (per class), which is derived from the number of CPUs on this host.
> 13:39:32,901 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 69) WFLYUT0014: Creating file handler for path '/home/ploffay/projects/javaee-traced-store/wildfly-14.0.1.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
> 13:39:32,915 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: Started server default-server.
> 13:39:32,918 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
> 13:39:32,985 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
> 13:39:33,103 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0493: EJB subsystem suspension complete
> 13:39:33,176 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
> 13:39:33,224 INFO [org.jboss.as.patching] (MSC service thread 1-1) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
> 13:39:33,252 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore /home/ploffay/projects/javaee-traced-store/wildfly-14.0.1.Final/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
> 13:39:33,258 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) WFLYDS0013: Started FileSystemDeploymentService for directory /home/ploffay/projects/javaee-traced-store/wildfly-14.0.1.Final/standalone/deployments
> 13:39:33,274 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "javaee-traced-store-1.0-SNAPSHOT.war" (runtime-name: "javaee-traced-store-1.0-SNAPSHOT.war")
> 13:39:33,337 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
> 13:39:33,417 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBossWS 5.2.3.Final (Apache CXF 3.2.5.jbossorg-1)
> 13:39:33,807 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment javaee-traced-store-1.0-SNAPSHOT.war
> 13:39:33,921 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-8) HV000001: Hibernate Validator 6.0.13.Final
> 13:39:34,075 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'OrderEndpoint' in deployment unit 'deployment "javaee-traced-store-1.0-SNAPSHOT.war"' are as follows:
> java:global/javaee-traced-store-1.0-SNAPSHOT/OrderEndpoint!io.jaegertracing.examples.wildfly.OrderEndpoint
> java:app/javaee-traced-store-1.0-SNAPSHOT/OrderEndpoint!io.jaegertracing.examples.wildfly.OrderEndpoint
> java:module/OrderEndpoint!io.jaegertracing.examples.wildfly.OrderEndpoint
> ejb:javaee-traced-store-1.0-SNAPSHOT/OrderEndpoint!io.jaegertracing.examples.wildfly.OrderEndpoint
> java:global/javaee-traced-store-1.0-SNAPSHOT/OrderEndpoint
> java:app/javaee-traced-store-1.0-SNAPSHOT/OrderEndpoint
> java:module/OrderEndpoint
> 13:39:34,248 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 3.0.5 (Final)
> 13:39:34,439 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-5) ISPN000128: Infinispan version: Infinispan 'Estrella Galicia' 9.3.1.Final
> 13:39:34,634 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 72) WFLYCLINF0002: Started client-mappings cache from ejb container
> 13:39:35,007 WARN [io.jaegertracing.internal.senders.SenderResolver] (ServerService Thread Pool -- 72) No suitable sender found. Using NoopSender, meaning that data will not be sent anywhere!
> 13:39:35,061 ERROR [stderr] (Timer-2) Exception in thread "Timer-2" java.lang.RuntimeException: Unable to invoke no-args constructor for class io.jaegertracing.internal.samplers.http.SamplingStrategyResponse. Registering an InstanceCreator with Gson for this type may fix this problem.
> 13:39:35,062 ERROR [stderr] (Timer-2) at com.google.gson.internal.ConstructorConstructor$14.construct(ConstructorConstructor.java:226)
> 13:39:35,062 ERROR [stderr] (Timer-2) at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:210)
> 13:39:35,062 ERROR [stderr] (Timer-2) at com.google.gson.Gson.fromJson(Gson.java:888)
> 13:39:35,062 ERROR [stderr] (Timer-2) at com.google.gson.Gson.fromJson(Gson.java:853)
> 13:39:35,062 ERROR [stderr] (Timer-2) at com.google.gson.Gson.fromJson(Gson.java:802)
> 13:39:35,062 ERROR [stderr] (Timer-2) at com.google.gson.Gson.fromJson(Gson.java:774)
> 13:39:35,062 ERROR [stderr] (Timer-2) at io.jaegertracing.internal.samplers.HttpSamplingManager.parseJson(HttpSamplingManager.java:49)
> 13:39:35,062 ERROR [stderr] (Timer-2) at io.jaegertracing.internal.samplers.HttpSamplingManager.getSamplingStrategy(HttpSamplingManager.java:68)
> 13:39:35,063 ERROR [stderr] (Timer-2) at io.jaegertracing.internal.samplers.RemoteControlledSampler.updateSampler(RemoteControlledSampler.java:88)
> 13:39:35,063 ERROR [stderr] (Timer-2) at io.jaegertracing.internal.samplers.RemoteControlledSampler$1.run(RemoteControlledSampler.java:70)
> 13:39:35,063 ERROR [stderr] (Timer-2) at java.util.TimerThread.mainLoop(Timer.java:555)
> 13:39:35,063 ERROR [stderr] (Timer-2) at java.util.TimerThread.run(Timer.java:505)
> 13:39:35,063 ERROR [stderr] (Timer-2) Caused by: java.lang.UnsupportedOperationException: Cannot allocate class io.jaegertracing.internal.samplers.http.SamplingStrategyResponse
> 13:39:35,063 ERROR [stderr] (Timer-2) at com.google.gson.internal.UnsafeAllocator$4.newInstance(UnsafeAllocator.java:104)
> 13:39:35,064 ERROR [stderr] (Timer-2) at com.google.gson.internal.ConstructorConstructor$14.construct(ConstructorConstructor.java:223)
> 13:39:35,064 ERROR [stderr] (Timer-2) ... 11 more
> 13:39:35,210 INFO [io.jaegertracing.Configuration] (ServerService Thread Pool -- 72) Initialized tracer=JaegerTracer(version=Java-0.30.6, serviceName=javaee-traced-store-1.0-SNAPSHOT.war, reporter=CompositeReporter(reporters=[RemoteReporter(sender=NoopSender(), closeEnqueueTimeout=1000), LoggingReporter(logger=org.slf4j.impl.Slf4jLogger(io.jaegertracing.internal.reporters.LoggingReporter))]), sampler=RemoteControlledSampler(maxOperations=2000, manager=HttpSamplingManager(hostPort=localhost:5778), sampler=ProbabilisticSampler(tags={sampler.type=probabilistic, sampler.param=0.001})), tags={hostname=dhcp-144-223.gva.redhat.com, jaeger.version=Java-0.30.6, ip=10.33.144.223}, zipkinSharedRpcSpan=false, expandExceptionLogs=false)
> 13:39:35,557 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 72) RESTEASY002225: Deploying javax.ws.rs.core.Application: class io.jaegertracing.examples.wildfly.TracedStoreApplication
> 13:39:35,589 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0021: Registered web context: '/javaee-traced-store-1.0-SNAPSHOT' for server 'default-server'
> 13:39:35,605 INFO [org.jboss.as.server] (ServerService Thread Pool -- 42) WFLYSRV0010: Deployed "javaee-traced-store-1.0-SNAPSHOT.war" (runtime-name : "javaee-traced-store-1.0-SNAPSHOT.war")
> 13:39:35,683 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
> 13:39:35,685 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
> 13:39:35,686 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
> 13:39:35,686 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 14.0.1.Final (WildFly Core 6.0.2.Final) started in 5525ms - Started 445 of 628 services (326 services are lazy, passive or on-demand)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-10438) Create a domain testsuite test for a missing host-exclude
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-10438?page=com.atlassian.jira.plugin... ]
James Perkins reopened WFLY-10438:
----------------------------------
> Create a domain testsuite test for a missing host-exclude
> ---------------------------------------------------------
>
> Key: WFLY-10438
> URL: https://issues.jboss.org/browse/WFLY-10438
> Project: WildFly
> Issue Type: Task
> Components: Management, Test Suite
> Reporter: Brian Stansberry
> Assignee: Yeray Borges
> Priority: Major
> Labels: domain-mode
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
>
> We need a simple domain mode smoke test that will fail if a new extension is added without corresponding adjustments to the domain.xml host-exclude resources.
> I had a complicated slow approach in mind that I wrote here before; it's stricken out below.
> Much simpler approach:
> Add a test to testsuite domain that uses a DC running the standard domain.xml. Read from the DC all the extensions. Work through the host-exclude resources. For each host-exclude, take a copy of the set of extensions, remove those listed in the host-exclude and compare the result to a known correct set of extensions for that version.
> If we add a new extension and don't host-exclude it, this will fail. This really is all that's needed to avoid completely skipping the host-excludes.
> If we add a new host-exclude and don't add the correct set of extensions to the test, the test will fail. This will help ensure the test isn't completely unmaintained.
> It doesn't cover people forgetting to add a new legacy version host-exclude when adding the first extension in a new version, but that can be tracked via code review or just being reasonably careful.
> Original complicated approach:
> -We need a simple test that a slave running the version before the current one can boot and run a minimal server. Basically to catch the need for a fix like WFLY-10396 whenever we add a new extension.
> Something like:
> Base domain config must be the standard one we ship. It will include all extensions.
> Test adds a minimal profile -- bare bones logging subsystem or perhaps no subsystem at all, can only have config that has been legal from the beginning -- and a server group using that profile. The server-group is added to the 'active-server-groups' attribute in the host-exclude resource for the slave's version.
> Slave host.xml has 1 server only, and in that server group.
> Launch the DC using the current release and the slave using the legacy release. Prove the slave server can start.-
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-10438) Create a domain testsuite test for a missing host-exclude
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-10438?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-10438:
---------------------------------
Fix Version/s: 15.0.0.Final
> Create a domain testsuite test for a missing host-exclude
> ---------------------------------------------------------
>
> Key: WFLY-10438
> URL: https://issues.jboss.org/browse/WFLY-10438
> Project: WildFly
> Issue Type: Task
> Components: Management, Test Suite
> Reporter: Brian Stansberry
> Assignee: Yeray Borges
> Priority: Major
> Labels: domain-mode
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
>
> We need a simple domain mode smoke test that will fail if a new extension is added without corresponding adjustments to the domain.xml host-exclude resources.
> I had a complicated slow approach in mind that I wrote here before; it's stricken out below.
> Much simpler approach:
> Add a test to testsuite domain that uses a DC running the standard domain.xml. Read from the DC all the extensions. Work through the host-exclude resources. For each host-exclude, take a copy of the set of extensions, remove those listed in the host-exclude and compare the result to a known correct set of extensions for that version.
> If we add a new extension and don't host-exclude it, this will fail. This really is all that's needed to avoid completely skipping the host-excludes.
> If we add a new host-exclude and don't add the correct set of extensions to the test, the test will fail. This will help ensure the test isn't completely unmaintained.
> It doesn't cover people forgetting to add a new legacy version host-exclude when adding the first extension in a new version, but that can be tracked via code review or just being reasonably careful.
> Original complicated approach:
> -We need a simple test that a slave running the version before the current one can boot and run a minimal server. Basically to catch the need for a fix like WFLY-10396 whenever we add a new extension.
> Something like:
> Base domain config must be the standard one we ship. It will include all extensions.
> Test adds a minimal profile -- bare bones logging subsystem or perhaps no subsystem at all, can only have config that has been legal from the beginning -- and a server group using that profile. The server-group is added to the 'active-server-groups' attribute in the host-exclude resource for the slave's version.
> Slave host.xml has 1 server only, and in that server group.
> Launch the DC using the current release and the slave using the legacy release. Prove the slave server can start.-
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months