gaol

Related Issues

• https://issues.redhat.com/browse/WFLY-18544
• https://issues.redhat.com/browse/WFLY-19635

Description

With WFLY-18544 addressed from WildFly 31.0.0.Final+, which tries to avoid deployment archives duplication to save disk usage, it has side effects on cases of VFS API usage in the application and/or layered projects.

gaol

11:56:09,312 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "vertx-demos-kafka-web-0.0.1.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"vertx-demos-kafka-web-0.0.1.war\".WeldStartService" => "Failed to start service
    Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
Exception 0 :
org.jboss.weld.resources.spi.ResourceLoadingException: Error while loading class io.vertx.mutiny.core.Vertx
	at [email protected]//org.jboss.weld.resources.ClassTransformer.getBackedAnnotatedType(ClassTransformer.java:193)
	at [email protected]//org.jboss.weld.resources.ClassTransformer.getBackedAnnotatedType(ClassTransformer.java:201)
	at [email protected]//org.jboss.weld.manager.BeanManagerImpl.createAnnotatedType(BeanManagerImpl.java:1176)
	at [email protected]//org.jboss.weld.util.Forwardi

gaol

but some elements were not expected:
  [Stream{groupId='org.codehaus.woodstox', artifactId='stax2-api', version='4.2.1', versionPattern=null, versionComparator=org.wildfly.channel.version.FixedVersionMatcher@6e4566f1},
    Stream{groupId='org.wildfly.core', artifactId='wildfly-core-model-test-framework', version='19.0.0.Beta11', versionPattern=null, versionComparator=org.wildfly.channel.version.FixedVersionMatcher@51acdf2e},
    Stream{groupId='org.wildfly.core', artifactId='wildfly-jar-boot', version='19.0.0.Beta11', versionPattern=null, versionComparator=org.wildfly.channel.version.FixedVersionMatcher@5143c662},
    Stream{groupId='org.wildfly.galleon-plugins', artifactId='wildfly-config-gen', version='6.0.0.Alpha6', versionPattern=null, versionComparator=org.wildfly.channel.version.FixedVersionMatcher@78383390}]

gaol

check_password = Module.cwrap("login", "number", ["string"]);
function check_nums_on(pass, idx, len) {
  for (var i = 0; i < 10; i ++) {
    pass[idx] = i;
    if (idx + 1 < len) {
      check_nums_on(pass, idx + 1, len);
    } else {
      var pass_to_verify = "RH_CTF{" + pass.join("") + "}";
      console.log("the last bit, checking the password: " + pass_to_verify);
      result = check_password(pass_to_verify);

gaol

When I ran wildfly testsuite on JDK 17 within a podman container, I got NPE for all tests, please refer to NPE.stacktrace.java below on the stack trace, all work fine if I run it on base metal.

It relates to JDK issue: https://bugs.openjdk.java.net/browse/JDK-8272124, but this demostrates another case when the cgroup path does not start with the mount root.

In this case /proc/self/cgroup has the following line:

9:memory:/user.slice/user-1000.slice/session-3.scope

gaol

  @Test
  public void testEventBusOptions() {
    VertxOptions vertxOptions1 = new VertxOptions();
    JsonObject json = vertxOptions1.toJson();
    VertxOptions vertxOptions2 = new VertxOptions(json);
    assertEquals(json, vertxOptions2.toJson());
  }
  
  
  // ========================

gaol

(base) [lgao@lgao vertx-eventbus-bridge-clients]$ git remote -v
fork	[email protected]:gaol/vertx-eventbus-bridge-clients.git (fetch)    ## <<  here is my fork
fork	[email protected]:gaol/vertx-eventbus-bridge-clients.git (push)
origin	https://github.com/vert-x3/vertx-eventbus-bridge-clients (fetch)   ## << here is the official vert-x3 repo
origin	https://github.com/vert-x3/vertx-eventbus-bridge-clients (push)

So maybe try this:

git checkout master
git pull

gaol

2020-11-09 19:11:10
Full thread dump OpenJDK 64-Bit Server VM (25.222-b10 mixed mode):

"Attach Listener" #410 daemon prio=9 os_prio=0 tid=0x00007f7a8c028000 nid=0x1b0e waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
	- None

"ServerService Thread Pool -- 81" #407 prio=5 os_prio=0 tid=0x00007f7a582d8800 nid=0x184b waiting on condition [0x00007f7a28bd1000]

gaol

JBoss Mojo page: https://developer.jboss.org/wiki/ProposedRequirementsForImprovingQueryOperationForNestedChildResourcesAndComplexAttributes

Steps to create data source valid checker:
===

> /subsystem=datasources/data-source=ExampleDS:write-attribute(name=valid-connection-checker-class-name,value=org.jboss.jca.adapters.jdbc.extensions.novendor.SQLExceptionValidConnectionChecker)
> :reload
> /subsystem=datasources/data-source=ExampleDS:write-attribute(name=valid-connection-checker-properties, value={reason=>NoReason})
> :reload

gaol

11:06:22,998 DEBUG [io.undertow.request] (default I/O-3) Matched prefix path /long-running-servlet for path /long-running-servlet/HeavyProcessing
11:06:23,007 DEBUG [io.undertow.request.security] (default task-1) Attempting to authenticate HttpServerExchange{ GET /long-running-servlet/HeavyProcessing request {Accept=[*/*], User-Agent=[curl/7.51.0], Host=[127.0.0.1:8080]} response {X-Powered-By=[Undertow/1], Server=[WildFly/10]}}, authentication required: false
11:06:23,008 DEBUG [io.undertow.request.security] (default task-1) Authentication outcome was NOT_ATTEMPTED with method io.undertow.security.impl.CachedAuthenticatedSessionMechanism@3e39fda2 for HttpServerExchange{ GET /long-running-servlet/HeavyProcessing request {Accept=[*/*], User-Agent=[curl/7.51.0], Host=[127.0.0.1:8080]} response {X-Powered-By=[Undertow/1], Server=[WildFly/10]}}
11:06:23,008 DEBUG [io.undertow.request.security] (default task-1) Authentication result was ATTEMPTED for HttpServerExchange{ GET /long-running-servlet/HeavyProcessing re