[Red Hat JIRA] (WFLY-13538) Add Java 9+ version of ConcurrentDirectDeque
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13538?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFLY-13538:
-----------------------------------------
[~pferraro] I'm not sure if this should be resolved; i.e. did merging the PR into a built-with-JDK8 WildFly count?
> Add Java 9+ version of ConcurrentDirectDeque
> --------------------------------------------
>
> Key: WFLY-13538
> URL: https://issues.redhat.com/browse/WFLY-13538
> Project: WildFly
> Issue Type: Task
> Components: Clustering
> Affects Versions: 20.0.0.Beta1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Major
>
> The clustering code uses ConcurrentDirectDeque for its local scheduler implementation. While a portable implementation exists, a faster implementation that relies on sun.misc.Unsafe will be used when running with a compatible JVM.
> Now that jboss-parent includes profiles for multi-release jars, we can add a fast implementation (ported from Undertow) that uses VarHandle that will work on all Java9+ JVMs.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (WFLY-14134) Ignore OnOffOpenTracingTestCase
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-14134?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFLY-14134:
---------------------------------------
Fix Version/s: 22.0.0.Beta1
Assignee: Jeff Mesnil (was: Emmanuel Hugonnet)
Resolution: Done
> Ignore OnOffOpenTracingTestCase
> -------------------------------
>
> Key: WFLY-14134
> URL: https://issues.redhat.com/browse/WFLY-14134
> Project: WildFly
> Issue Type: Bug
> Components: MP OpenTracing
> Affects Versions: 22.0.0.Alpha1
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Priority: Major
> Fix For: 22.0.0.Beta1
>
>
> While doing unrelated development, I noticed that I had a failure in SimpleRestClientTestCase that seems to come from the OnOffOpenTracingTestCase.
> It seems that the test code in OnOffOpenTracingTestCase make Weld get lost and the failure happens in the next test running...
> The code in OnOffOpenTracingTestCase is a bit convoluted (it reload the server 4 times!) and does not take into account that once the open tracing subsystem is removed, the deployment used by the test can not be deployed (as the subsystem was responsible for exposing the opentracing API to the deployment code).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (WFLY-14235) com/sun/ts/tests/ejb30/sec/permsxml#ValidateCustomPerm fails due to appclient not having security manager enabled.
by Scott Marlow (Jira)
Scott Marlow created WFLY-14235:
-----------------------------------
Summary: com/sun/ts/tests/ejb30/sec/permsxml#ValidateCustomPerm fails due to appclient not having security manager enabled.
Key: WFLY-14235
URL: https://issues.redhat.com/browse/WFLY-14235
Project: WildFly
Issue Type: Sub-task
Components: Application Client
Reporter: Scott Marlow
Assignee: Scott Marlow
{quote}
#Test Results (version 2)
#Tue Dec 15 00:17:33 EST 2020
#-----testdescription-----
$file=/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/src/com/sun/ts/tests/ejb30/sec/permsxml/Client.java
$root=/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/src
assertion_ids=JavaEE\:SPEC\:290 See assertion html documents.\nJavaEE\:SPEC\:293 See assertion html documents.
classname=com.sun.ts.tests.ejb30.sec.permsxml.Client
direction=forward
finder=cts
id=ValidateCustomPerm
keywords=all javaee security_manager_enabled ValidateCustomPerm novehicle forward
service_eetest=no
testName=ValidateCustomPerm
testProps=\ user password authuser
test_directory=com/sun/ts/tests/ejb30/sec/permsxml
#-----environment-----
EJBServer1TxInteropEnabled=false
EJBServer2TxInteropEnabled=true
JAVA_HOME=/qa/tools/opt/x86_64/jdk1.8.0_191/jre
SYSTEMROOT=${env.SystemRoot}
TMP=${env.TMP}
authuser=javajoe
command.testExecuteAppClient=com.sun.ts.lib.harness.ExecTSTestCmd CLASSPATH\=${ts.run.classpath} DISPLAY\=${ts.display} HOME\="${user.home}" JAVA_HOME\=${JAVA_HOME} JAVAEE_HOME_RI\=${JAVAEE_HOME_RI} LD_LIBRARY_PATH\=${javaee.home}/lib TMP\=${TMP} windir\=${windir} SYSTEMROOT\=${SYSTEMROOT} APPCPATH\=${ts.run.classpath} TZ\=${tz} ${jboss.home}/bin/appclient.sh -Dee8.preview.mode\=true -DwebServerHost.2\=${webServerHost.2} -DwebServerPort.2\=${webServerPort.2} -Dcxf.tls-client.disableCNCheck\=true -Djava.protocol.handler.pkgs\=javax.net.ssl -Djavax.net.ssl.keyStore\=${ts.home}/bin/certificates/clientcert.jks -Djavax.net.ssl.keyStorePassword\=changeit -Djavax.net.ssl.trustStore\=${jboss.conf.dir}/keystores/tomcat.keystore -Djavax.net.ssl.trustStorePassword\=rmi+ssl -Dri.log.file.location\=${ri.log.file.location} $testExecuteArgs
deployment_host.1=${orb.host}
deployment_host.2=${orb.host.ri}
deployment_port.1=${impl.vi.port}
deployment_port.2=${impl.ri.port}
derby.classes=${jdbc.lib.class.path}/derbyclient.jar
derby.dbName=derbyDB
derby.driver=org.apache.derby.jdbc.ClientDriver
derby.passwd=cts1
derby.port=1527
derby.server=${orb.host}
derby.url=jdbc\:derby\://${derby.server}\:${derby.port}/${derby.dbName};create\=true
derby.user=cts1
harness.executeMode=0
harness.log.delayseconds=1
harness.log.port=2000
harness.log.traceflag=false
harness.socket.retry.count=10
harness.temp.directory=${ts.home}/tmp
http.server.supports.endpoint.publish=true
http.server.supports.endpoint.publish.2=false
impl.ri.port=${ri.admin.port}
impl.vi.port=${jboss.admin.port}
jakarta.persistence.jdbc.driver=${derby.driver}
jakarta.persistence.jdbc.password=${derby.passwd}
jakarta.persistence.jdbc.url=${derby.url}
jakarta.persistence.jdbc.user=${derby.user}
jakarta.persistence.provider=org.hibernate.jpa.HibernatePersistenceProvider
jaspic.classpath=\:${jboss.modules.dir}/system/layers/base/org/apache/cxf/main/cxf-rt-features-logging-3.3.7.jar\:${jboss.modules.dir}/system/layers/base/org/jboss/as/logging/main/wildfly-logging-14.0.0.Beta4.jar\:${jboss.modules.dir}/system/layers/base/org/jboss/logging/commons/logging/main/commons-logging-jboss-logging-1.0.0.Final.jar\:${jboss.modules.dir}/system/layers/base/org/jboss/logging/main/jboss-logging-3.4.1.Final.jar\:${jboss.modules.dir}/system/layers/base/org/wildfly/security/elytron-private/main/wildfly-elytron-jaspi-1.14.0.Final-ee9.jar
javaee.classes=${javaee.home}/bin/client/jboss-client.jar\:${jboss.javamail.classpath}\:${jboss.iiop.client.classpath}${pathsep}${jboss.modules.dir}/system/layers/base/javax/enterprise/api/main/jakarta.enterprise.cdi-api-2.0.2.jar${pathsep}${jboss.modules.dir}/system/layers/base/javax/enterprise/api/main/cdi-api-2.0.jar${pathsep}${jboss.io.undertow.classpath}${pathsep}${ts.home}/lib/tsharness.jar
javaee.home=/mnt/hudson_workspace/customWorkspaceName/wildfly
javaee.home.ri=/mnt/hudson_workspace/customWorkspaceName/glassfish6/glassfish
javaee.level=full jms connector jaxws jaxb javamail jacc jaspic wsmd
jboss.admin.port=9990
jboss.base.client.classpath=\:${jboss.modules.dir}/system/layers/base/jakarta/el/api/main/jboss-el-api_4.0_spec-3.0.0.jar\:${jboss.modules.dir}/system/layers/base/jakarta/websocket/api/main/jakarta.websocket-api-2.0.0.jar\:${jboss.modules.dir}/system/layers/base/jakarta/ws/rs/api/main/jboss-jaxrs-api_2.1_spec-2.0.1.Final-ee9.jar\:${jboss.modules.dir}/system/layers/base/javax/json/api/main/jakarta.json-api-1.1.6-ee9.jar\:${jboss.modules.dir}/system/layers/base/org/glassfish/jakarta/json/main/jakarta.json-1.1.6-ee9.jar
jboss.classpath=${ts.home}/jboss/classes
jboss.client.classpath=${jboss.base.client.classpath}\:${jaspic.classpath}
jboss.conf.dir=${jboss.server.home}/configuration
jboss.home=${javaee.home}
jboss.iiop.client.classpath=${jboss.modules.dir}/system/layers/base/org/jboss/iiop-client/main/jboss-iiop-client-1.0.1.Final-ee9.jar
jboss.io.undertow.classpath=\:${jboss.modules.dir}/system/layers/base/io/undertow/core/main/undertow-core-2.2.3.Final.jar\:${jboss.modules.dir}/system/layers/base/io/undertow/js/main/undertow-js-1.0.2.Final-ee9.jar\:${jboss.modules.dir}/system/layers/base/io/undertow/servlet/main/undertow-servlet-2.2.3.Final-ee9.jar\:${jboss.modules.dir}/system/layers/base/io/undertow/websocket/main/undertow-websockets-jsr-2.2.3.Final-ee9.jar\:${jboss.modules.dir}/system/layers/base/org/wildfly/security/elytron-web/undertow-server-servlet/main/undertow-server-servlet-1.8.0.Final-ee9.jar\:${jboss.modules.dir}/system/layers/base/org/wildfly/security/elytron-web/undertow-server/main/undertow-server-1.8.0.Final.jar
jboss.javamail.classpath=\:${jboss.modules.dir}/system/layers/base/jakarta/mail/api/main/jakarta.mail-2.0.0.jar
jboss.modules.dir=${jboss.home}/modules
jboss.server.home=${jboss.home}/standalone
jdbc.db.classes=${derby.classes}
jdbc.lib.class.path=${javaee.home.ri}/../javadb/lib
jpa.provider.implementation.specific.properties=hibernate.jpa.compliance.closed\=true\:hibernate.model.generator_name_as_sequence_name\=true\:hibernate.jpa.compliance.transaction\=true\:hibernate.jpa.compliance.query\=true\:hibernate.jpa.compliance.list\=true\:hibernate.jpa.compliance.caching\=true\:hibernate.enable_lazy_load_no_trans\=true
namingServiceHost1=${orb.host}
namingServiceHost2=${orb.host.ri}
namingServicePort1=${orb.port}
namingServicePort2=${orb.port.ri}
orb.host=localhost
orb.host.ri=localhost
orb.port=3528
orb.port.ri=3700
password=j2ee
password1=${derby.passwd}
password2=${derby.passwd}
pathsep=\:
persistence.second.level.caching.supported=true
persistence.unit.name=CTS-EM
persistence.unit.name.2=JPATCK2
platform.mode=jakartaEE
porting.ts.HttpsURLConnection.class.1=com.sun.ts.lib.implementation.sun.javaee.SunRIHttpsURLConnection
porting.ts.HttpsURLConnection.class.2=com.sun.ts.lib.implementation.sun.javaee.SunRIHttpsURLConnection
porting.ts.deploy.class.1=org.jboss.ts.lib.implementation.jboss.javaee.JBossAutoDeployment
porting.ts.deploy.class.2=com.sun.ts.lib.implementation.sun.javaee.glassfish.AutoDeployment
porting.ts.deploy2.class.1=org.jboss.ts.lib.implementation.jboss.javaee.JBossDeployment2
porting.ts.deploy2.class.2=com.sun.ts.lib.implementation.sun.javaee.SunRIDeployment2
porting.ts.jms.class.1=com.sun.ts.lib.implementation.sun.javaee.SunRIJMSAdmin
porting.ts.jms.class.2=com.sun.ts.lib.implementation.sun.javaee.SunRIJMSAdmin
porting.ts.login.class.1=org.jboss.ts.lib.implementation.jboss.javaee.JBossLoginContext
porting.ts.login.class.2=com.sun.ts.lib.implementation.sun.javaee.SunRILoginContext
porting.ts.url.class.1=com.sun.ts.lib.implementation.sun.common.SunRIURL
porting.ts.url.class.2=com.sun.ts.lib.implementation.sun.common.SunRIURL
ri.admin.port=4848
ri.domain=${ri.domain.dir}/${ri.domain.name}
ri.domain.dir=${javaee.home.ri}/domains
ri.domain.name=domain1
ri.log.file.location=${ri.domain}/logs
securedWebServicePort=8443
securedWebServicePort.2=1045
ts.display=\:0.0
ts.home=/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../..
ts.run.classpath=${jboss.classpath}${pathsep}${jboss.client.classpath}${pathsep}${ts.home}/lib/oasis-regrep.jar${pathsep}${ts.home}/lib/omar-common.jar${pathsep}${javaee.classes}${pathsep}${ts.home}/lib/tsharness.jar${pathsep}${ts.home}/lib/cts.jar${pathsep}${derby.classes}${pathsep}${ts.home}/jboss/lib/jboss-porting.jar${pathsep}${jdbc.db.classes}${pathsep}
tz=US/Eastern
user=j2ee
user.home=/home/hudson
user1=${derby.user}
user2=${derby.user}
variable.mapper=com.sun.el.lang.VariableMapperImpl
vi.admin.passwd=
vi.admin.user=admin
webServerHost=${orb.host}
webServerHost.2=${orb.host.ri}
webServerPort=8080
webServerPort.2=8002
windir=${env.windir}
wsdlRepository1=${jboss.server.home}/data/wsdl
wsdlRepository2=${harness.temp.directory}/wsdlRepository2
#-----testresult-----
description=file\:/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/src/com/sun/ts/tests/ejb30/sec/permsxml/Client.java\#ValidateCustomPerm
end=Tue Dec 15 00\:17\:33 EST 2020
environment=ts_unix
execStatus=Failed. test failed
harnessLoaderMode=Classpath Loader
harnessVariety=Full Bundle
javatestOS=Linux 3.10.0-693.21.1.el7.x86_64 (amd64)
javatestVersion=5.0
script=com.sun.ts.lib.harness.TSScript
sections=script_messages Deployment TestRun
start=Tue Dec 15 00\:17\:20 EST 2020
test=com/sun/ts/tests/ejb30/sec/permsxml/Client.java\#ValidateCustomPerm
timeoutSeconds=600
totalTime=12954
work=/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/JTwork/com/sun/ts/tests/ejb30/sec/permsxml
#section:script_messages
----------messages:(0/0)----------
#section:Deployment
----------messages:(0/0)----------
----------log:(17/1242)----------
Undeploying apps...
JBossAutoDeployment.isDeployed()
JBossAutoDeployment.undeploy()
Undeploying apps...
JBossAutoDeployment.isDeployed()
Search for s1as runtime files match:`ejb3_sec_permsxml.ear`
Valid runtime files after sweep:
/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/ejb30/sec/permsxml/ejb3_sec_permsxml.ear.sun-application.xml
/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/ejb30/sec/permsxml/ejb3_sec_permsxml_client.jar.sun-application-client.xml
/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/ejb30/sec/permsxml/ejb3_sec_permsxml_ejb.jar.sun-ejb-jar.xml
Deploying apps for forward rebuildable...
Search for s1as runtime files match:`ejb3_sec_permsxml.ear`
Valid runtime files after sweep:
/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../tmp/ejb3_sec_permsxml.ear.sun-application.xml
/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../tmp/ejb3_sec_permsxml_client.jar.sun-application-client.xml
/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../tmp/ejb3_sec_permsxml_ejb.jar.sun-ejb-jar.xml
getAppNameFromApplicationXML() returning "null"
result: Passed. Deployment phase completed. However, check the output above to see if actual deployment passed or failed.
#section:TestRun
----------messages:(1/8596)----------
command: com.sun.ts.lib.harness.ExecTSTestCmd CLASSPATH=:::::/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../jboss/classes::/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/jakarta/el/api/main/jboss-el-api_4.0_spec-3.0.0.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/jakarta/websocket/api/main/jakarta.websocket-api-2.0.0.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/jakarta/ws/rs/api/main/jboss-jaxrs-api_2.1_spec-2.0.1.Final-ee9.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/javax/json/api/main/jakarta.json-api-1.1.6-ee9.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/org/glassfish/jakarta/json/main/jakarta.json-1.1.6-ee9.jar::/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/org/apache/cxf/main/cxf-rt-features-logging-3.3.7.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/org/jboss/as/logging/main/wildfly-logging-14.0.0.Beta4.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/org/jboss/logging/commons/logging/main/commons-logging-jboss-logging-1.0.0.Final.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/org/jboss/logging/main/jboss-logging-3.4.1.Final.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/org/wildfly/security/elytron-private/main/wildfly-elytron-jaspi-1.14.0.Final-ee9.jar:/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../lib/oasis-regrep.jar:/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../lib/omar-common.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/bin/client/jboss-client.jar::/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/jakarta/mail/api/main/jakarta.mail-2.0.0.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/org/jboss/iiop-client/main/jboss-iiop-client-1.0.1.Final-ee9.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/javax/enterprise/api/main/jakarta.enterprise.cdi-api-2.0.2.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/javax/enterprise/api/main/cdi-api-2.0.jar::/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/io/undertow/core/main/undertow-core-2.2.3.Final.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/io/undertow/js/main/undertow-js-1.0.2.Final-ee9.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/io/undertow/servlet/main/undertow-servlet-2.2.3.Final-ee9.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/io/undertow/websocket/main/undertow-websockets-jsr-2.2.3.Final-ee9.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/org/wildfly/security/elytron-web/undertow-server-servlet/main/undertow-server-servlet-1.8.0.Final-ee9.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/org/wildfly/security/elytron-web/undertow-server/main/undertow-server-1.8.0.Final.jar:/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../lib/tsharness.jar:/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../lib/tsharness.jar:/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../lib/cts.jar:/mnt/hudson_workspace/customWorkspaceName/glassfish6/glassfish/../javadb/lib/derbyclient.jar:/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../jboss/lib/jboss-porting.jar:/mnt/hudson_workspace/customWorkspaceName/glassfish6/glassfish/../javadb/lib/derbyclient.jar: DISPLAY=:0.0 HOME=/home/hudson JAVA_HOME=/qa/tools/opt/x86_64/jdk1.8.0_191/jre JAVAEE_HOME_RI= LD_LIBRARY_PATH=/mnt/hudson_workspace/customWorkspaceName/wildfly/lib TMP= windir= SYSTEMROOT= APPCPATH=/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../jboss/classes::/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/jakarta/el/api/main/jboss-el-api_4.0_spec-3.0.0.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/jakarta/websocket/api/main/jakarta.websocket-api-2.0.0.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/jakarta/ws/rs/api/main/jboss-jaxrs-api_2.1_spec-2.0.1.Final-ee9.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/javax/json/api/main/jakarta.json-api-1.1.6-ee9.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/org/glassfish/jakarta/json/main/jakarta.json-1.1.6-ee9.jar::/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/org/apache/cxf/main/cxf-rt-features-logging-3.3.7.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/org/jboss/as/logging/main/wildfly-logging-14.0.0.Beta4.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/org/jboss/logging/commons/logging/main/commons-logging-jboss-logging-1.0.0.Final.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/org/jboss/logging/main/jboss-logging-3.4.1.Final.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/org/wildfly/security/elytron-private/main/wildfly-elytron-jaspi-1.14.0.Final-ee9.jar:/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../lib/oasis-regrep.jar:/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../lib/omar-common.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/bin/client/jboss-client.jar::/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/jakarta/mail/api/main/jakarta.mail-2.0.0.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/org/jboss/iiop-client/main/jboss-iiop-client-1.0.1.Final-ee9.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/javax/enterprise/api/main/jakarta.enterprise.cdi-api-2.0.2.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/javax/enterprise/api/main/cdi-api-2.0.jar::/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/io/undertow/core/main/undertow-core-2.2.3.Final.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/io/undertow/js/main/undertow-js-1.0.2.Final-ee9.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/io/undertow/servlet/main/undertow-servlet-2.2.3.Final-ee9.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/io/undertow/websocket/main/undertow-websockets-jsr-2.2.3.Final-ee9.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/org/wildfly/security/elytron-web/undertow-server-servlet/main/undertow-server-servlet-1.8.0.Final-ee9.jar:/mnt/hudson_workspace/customWorkspaceName/wildfly/modules/system/layers/base/org/wildfly/security/elytron-web/undertow-server/main/undertow-server-1.8.0.Final.jar:/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../lib/tsharness.jar:/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../lib/tsharness.jar:/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../lib/cts.jar:/mnt/hudson_workspace/customWorkspaceName/glassfish6/glassfish/../javadb/lib/derbyclient.jar:/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../jboss/lib/jboss-porting.jar:/mnt/hudson_workspace/customWorkspaceName/glassfish6/glassfish/../javadb/lib/derbyclient.jar: TZ=US/Eastern /mnt/hudson_workspace/customWorkspaceName/wildfly/bin/appclient.sh -Dee8.preview.mode=true -DwebServerHost.2=localhost -DwebServerPort.2=8002 -Dcxf.tls-client.disableCNCheck=true -Djava.protocol.handler.pkgs=javax.net.ssl -Djavax.net.ssl.keyStore=/mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../bin/certificates/clientcert.jks -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/mnt/hudson_workspace/customWorkspaceName/wildfly/standalone/configuration/keystores/tomcat.keystore -Djavax.net.ssl.trustStorePassword=rmi+ssl -Dri.log.file.location=/mnt/hudson_workspace/customWorkspaceName/glassfish6/glassfish/domains/domain1/logs /mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/ejb30/sec/permsxml/ejb3_sec_permsxml.ear#ejb3_sec_permsxml_client.jar -p /mnt/hudson_workspace/customWorkspaceName/jakartaeetck/bin/xml/../../tmp/tstest.jte -t ValidateCustomPerm
----------log:(128/23812)*----------
\u001b[0m00:17:21,985 INFO [org.jboss.modules] (main) JBoss Modules version 1.11.0.Final
\u001b[0m\u001b[0m00:17:22,473 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.12.Final
\u001b[0m\u001b[0m00:17:22,496 INFO [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final
\u001b[0m\u001b[0m00:17:22,768 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Preview 22.0.0.Beta1-SNAPSHOT (WildFly Core 14.0.0.Beta4) starting
\u001b[0m\u001b[0m00:17:25,100 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 10) WFLYCTL0028: Attribute 'security-domain' in the resource at address '/subsystem=messaging-activemq/server=default' 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.
\u001b[0m\u001b[0m00:17:25,326 INFO [org.jboss.as.security] (ServerService Thread Pool -- 29) WFLYSEC0002: Activating Security Subsystem
\u001b[0m\u001b[33m00:17:25,327 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 31) 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.
\u001b[0m\u001b[0m00:17:25,330 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 32) WFLYWS0002: Activating WebServices Extension
\u001b[0m\u001b[0m00:17:25,400 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 28) WFLYNAM0001: Activating Naming Subsystem
\u001b[0m\u001b[0m00:17:25,503 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 23) WFLYIIOP0001: Activating IIOP Subsystem
\u001b[0m\u001b[0m00:17:25,719 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=5.0.3.Final-redhat-00007
\u001b[0m\u001b[0m00:17:25,794 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 20) WFLYJCA0004: Deploying JDBC-compliant driver class org.apache.derby.jdbc.ClientDriver (version 10.14)
\u001b[0m\u001b[0m00:17:25,816 INFO [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar @VERSION@)
\u001b[0m\u001b[0m00:17:26,413 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = derby
\u001b[0m\u001b[0m00:17:26,416 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service
\u001b[0m\u001b[0m00:17:26,570 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.8.4.Final
\u001b[0m\u001b[0m00:17:26,575 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.8.4.Final
\u001b[0m\u001b[0m00:17:26,694 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 5.0.20.Final
\u001b[0m\u001b[0m00:17:26,767 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:/mail/Session]
\u001b[0m\u001b[0m00:17:27,001 INFO [org.jboss.as.patching] (MSC service thread 1-1) WFLYPAT0050: WildFly Preview cumulative patch ID is: base, one-off patches include: none
\u001b[0m\u001b[0m00:17:27,126 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.4.2.Final (Apache CXF 3.3.7)
\u001b[0m\u001b[0m00:17:27,267 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0098: Bound non-transactional data source: java:/jdbc/DB_no_tx
\u001b[0m\u001b[0m00:17:27,396 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0493: EJB subsystem suspension complete
\u001b[0m\u001b[33m00:17:27,459 WARN [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-1) IJ020016: Missing <recovery> element. XA recovery disabled for: java:/JavadbXA
\u001b[0m\u001b[0m00:17:27,462 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:/jdbc/DBTimer]
\u001b[0m\u001b[0m00:17:27,462 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:/jdbc/DB1]
\u001b[0m\u001b[0m00:17:27,462 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:/JavadbXA]
\u001b[0m\u001b[0m00:17:27,731 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-2) WFLYIIOP0009: CORBA ORB Service started
\u001b[0m\u001b[33m00:17:29,006 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 35) AMQ222205: OutOfMemoryError possible! There are currently 134 addresses with a total max-size-bytes of 1,405,091,840 bytes, but the maximum memory available is 518,979,584 bytes.
\u001b[0m\u001b[0m00:17:29,086 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 35) WFLYMSGAMQ0002: Bound messaging object to jndi name jms/DURABLE_CMT_CONNECTION_FACTORY
\u001b[0m\u001b[0m00:17:29,394 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 160) WFLYMSGAMQ0002: Bound messaging object to jndi name jms/QueueConnectionFactory
\u001b[0m\u001b[0m00:17:29,392 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0007: Registered connection factory java:/jms/QueueConnectionFactory2
\u001b[0m\u001b[0m00:17:29,423 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 144) WFLYMSGAMQ0002: Bound messaging object to jndi name jms/DURABLE_BMT_XCONNECTION_FACTORY
\u001b[0m\u001b[0m00:17:29,428 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 106) WFLYMSGAMQ0002: Bound messaging object to jndi name jms/DURABLE_CMT_XCONNECTION_FACTORY
\u001b[0m\u001b[0m00:17:29,429 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 102) WFLYMSGAMQ0002: Bound messaging object to jndi name jms/MDBTACCESSTEST_FACTORY
\u001b[0m\u001b[0m00:17:29,431 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 88) WFLYMSGAMQ0002: Bound messaging object to jndi name jms/DURABLE_BMT_CONNECTION_FACTORY
\u001b[0m\u001b[0m00:17:29,432 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 51) WFLYMSGAMQ0002: Bound messaging object to jndi name jms/DURABLE_SUB_CONNECTION_FACTORY
\u001b[0m\u001b[0m00:17:29,434 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 47) WFLYMSGAMQ0002: Bound messaging object to jndi name RemoteConnectionFactory
\u001b[0m\u001b[0m00:17:29,435 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 47) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
\u001b[0m\u001b[0m00:17:29,435 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 47) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
\u001b[0m\u001b[0m00:17:29,435 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 62) WFLYMSGAMQ0002: Bound messaging object to jndi name jms/DURABLE_CMT_TXNS_XCONNECTION_FACTORY
\u001b[0m\u001b[0m00:17:29,436 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 48) WFLYMSGAMQ0002: Bound messaging object to jndi name jms/TopicConnectionFactory
\u001b[0m\u001b[0m00:17:29,787 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-2) IJ020002: Deployed: file://RaActivatorjmsra
\u001b[0m\u001b[0m00:17:29,789 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0002: Bound JCA ConnectionFactory [java:/jms/QueueConnectionFactory2]
\u001b[0m\u001b[0m00:17:29,789 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0118: Binding connection factory named java:/jms/QueueConnectionFactory2 to alias jms/TopicConnectionFactory2
\u001b[0m\u001b[0m00:17:29,879 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "ejb3_sec_permsxml.ear" (runtime-name: "ejb3_sec_permsxml.ear")
\u001b[0m\u001b[0m00:17:29,967 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
\u001b[0m\u001b[0m00:17:30,088 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: "ejb3_sec_permsxml_ejb.jar")
\u001b[0m\u001b[0m00:17:30,102 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "ejb3_sec_permsxml_client.jar")
\u001b[0m\u001b[33m00:17:30,727 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=tsharness, specificationVersion=1.4, title=tsharness] referenced from ResourceRoot [root="/content/ejb3_sec_permsxml.ear"]
\u001b[0m\u001b[33m00:17:30,727 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=cts, specificationVersion=1.4, title=cts] referenced from ResourceRoot [root="/content/ejb3_sec_permsxml.ear"]
\u001b[0m\u001b[33m00:17:30,728 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=tsharness, specificationVersion=1.4, title=tsharness] referenced from ResourceRoot [root="/content/ejb3_sec_permsxml.ear/ejb3_sec_permsxml_client.jar"]
\u001b[0m\u001b[33m00:17:30,728 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=cts, specificationVersion=1.4, title=cts] referenced from ResourceRoot [root="/content/ejb3_sec_permsxml.ear/ejb3_sec_permsxml_client.jar"]
\u001b[0m\u001b[33m00:17:30,728 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=tsharness, specificationVersion=1.4, title=tsharness] referenced from ResourceRoot [root="/content/ejb3_sec_permsxml.ear/ejb3_sec_permsxml_client.jar"]
\u001b[0m\u001b[33m00:17:30,728 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=cts, specificationVersion=1.4, title=cts] referenced from ResourceRoot [root="/content/ejb3_sec_permsxml.ear/ejb3_sec_permsxml_client.jar"]
\u001b[0m\u001b[33m00:17:30,728 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=tsharness, specificationVersion=1.4, title=tsharness] referenced from ResourceRoot [root="/content/ejb3_sec_permsxml.ear/ejb3_sec_permsxml_ejb.jar"]
\u001b[0m\u001b[33m00:17:30,728 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=cts, specificationVersion=1.4, title=cts] referenced from ResourceRoot [root="/content/ejb3_sec_permsxml.ear/ejb3_sec_permsxml_ejb.jar"]
\u001b[0m\u001b[33m00:17:30,728 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=tsharness, specificationVersion=1.4, title=tsharness] referenced from ResourceRoot [root="/content/ejb3_sec_permsxml.ear/ejb3_sec_permsxml_ejb.jar"]
\u001b[0m\u001b[33m00:17:30,728 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=cts, specificationVersion=1.4, title=cts] referenced from ResourceRoot [root="/content/ejb3_sec_permsxml.ear/ejb3_sec_permsxml_ejb.jar"]
\u001b[0m\u001b[33m00:17:30,734 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=tsharness, specificationVersion=1.4, title=tsharness] referenced from ResourceRoot [root="/content/ejb3_sec_permsxml.ear/ejb3_sec_permsxml_ejb.jar"]
\u001b[0m\u001b[33m00:17:30,734 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=cts, specificationVersion=1.4, title=cts] referenced from ResourceRoot [root="/content/ejb3_sec_permsxml.ear/ejb3_sec_permsxml_ejb.jar"]
\u001b[0m\u001b[33m00:17:30,734 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=tsharness, specificationVersion=1.4, title=tsharness] referenced from ResourceRoot [root="/content/ejb3_sec_permsxml.ear/ejb3_sec_permsxml_ejb.jar"]
\u001b[0m\u001b[33m00:17:30,734 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=cts, specificationVersion=1.4, title=cts] referenced from ResourceRoot [root="/content/ejb3_sec_permsxml.ear/ejb3_sec_permsxml_ejb.jar"]
\u001b[0m\u001b[33m00:17:30,735 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=tsharness, specificationVersion=1.4, title=tsharness] referenced from ResourceRoot [root="/content/ejb3_sec_permsxml.ear/ejb3_sec_permsxml_client.jar"]
\u001b[0m\u001b[33m00:17:30,735 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=cts, specificationVersion=1.4, title=cts] referenced from ResourceRoot [root="/content/ejb3_sec_permsxml.ear/ejb3_sec_permsxml_client.jar"]
\u001b[0m\u001b[33m00:17:30,735 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=tsharness, specificationVersion=1.4, title=tsharness] referenced from ResourceRoot [root="/content/ejb3_sec_permsxml.ear/ejb3_sec_permsxml_client.jar"]
\u001b[0m\u001b[33m00:17:30,735 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=cts, specificationVersion=1.4, title=cts] referenced from ResourceRoot [root="/content/ejb3_sec_permsxml.ear/ejb3_sec_permsxml_client.jar"]
\u001b[0m\u001b[0m00:17:30,855 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'PermDDTestEJB' in deployment unit 'subdeployment "ejb3_sec_permsxml_ejb.jar" of deployment "ejb3_sec_permsxml.ear"' are as follows:
java:global/ejb3_sec_permsxml/ejb3_sec_permsxml_ejb/PermDDTestEJB!com.sun.ts.tests.ejb30.sec.permsxml.PermDDTestIF
java:app/ejb3_sec_permsxml_ejb/PermDDTestEJB!com.sun.ts.tests.ejb30.sec.permsxml.PermDDTestIF
java:module/PermDDTestEJB!com.sun.ts.tests.ejb30.sec.permsxml.PermDDTestIF
java:jboss/exported/ejb3_sec_permsxml/ejb3_sec_permsxml_ejb/PermDDTestEJB!com.sun.ts.tests.ejb30.sec.permsxml.PermDDTestIF
ejb:ejb3_sec_permsxml/ejb3_sec_permsxml_ejb/PermDDTestEJB!com.sun.ts.tests.ejb30.sec.permsxml.PermDDTestIF?stateful
java:global/ejb3_sec_permsxml/ejb3_sec_permsxml_ejb/PermDDTestEJB
java:app/ejb3_sec_permsxml_ejb/PermDDTestEJB
java:module/PermDDTestEJB
\u001b[0m\u001b[0m00:17:30,876 INFO [org.wildfly.security] (MSC service thread 1-1) ELY00001: WildFly Elytron version 1.14.0.Final
\u001b[0m\u001b[0m00:17:31,003 INFO [org.jboss.as.server] (Thread-40) WFLYSRV0010: Deployed "ejb3_sec_permsxml.ear" (runtime-name : "ejb3_sec_permsxml.ear")
\u001b[0m\u001b[0m00:17:31,005 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Preview 22.0.0.Beta1-SNAPSHOT (WildFly Core 14.0.0.Beta4) started in 8584ms - Started 583 of 595 services (312 services are lazy, passive or on-demand)
\u001b[0m\u001b[0m00:17:31,018 INFO [org.jboss.ejb.client] (Thread-190) JBoss EJB Client version 4.0.37.Final
\u001b[0m\u001b[0m00:17:31,540 INFO [stdout] (Thread-190) ************************************************************
\u001b[0m\u001b[0m00:17:31,540 INFO [stdout] (Thread-190) * props file set to "/tmp/hudson-cts-props.txt"
\u001b[0m\u001b[0m00:17:31,540 INFO [stdout] (Thread-190) ************************************************************
\u001b[0m\u001b[0m00:17:31,560 INFO [org.jboss.ts.lib.implementation.jboss.javaee.JBossLoginContext] (Thread-190) login ok: j2ee/j2ee
\u001b[0m\u001b[0m00:17:31,560 INFO [stdout] (Thread-190) 12-15-2020 00:17:31: ERROR: Security Manager is NOT enabled and must be for these tests. If you have passed these tests while running with Security Manager enabled, you can use keywords to bypass the running of these tests when Security Manager is disabled.
\u001b[0m\u001b[0m00:17:31,560 INFO [stdout] (Thread-190) 12-15-2020 00:17:31: ERROR: ERROR: Security Manager is NOT enabled and must be for these tests. If you have passed these tests while running with Security Manager enabled, you can use keywords to bypass the running of these tests when Security Manager is disabled.
\u001b[0m\u001b[0m00:17:31,561 INFO [stdout] (Thread-190) 12-15-2020 00:17:31: ERROR: Test case throws exception: ValidateCustomPerm test failed:
\u001b[0m\u001b[0m00:17:31,561 INFO [stdout] (Thread-190) 12-15-2020 00:17:31: ERROR: Exception at:
\u001b[0m\u001b[0m00:17:31,561 INFO [stdout] (Thread-190) 12-15-2020 00:17:31: ERROR: com.sun.ts.lib.harness.EETest$Fault: ERROR: Security Manager is NOT enabled and must be for these tests. If you have passed these tests while running with Security Manager enabled, you can use keywords to bypass the running of these tests when Security Manager is disabled.
\u001b[0m\u001b[0m00:17:31,561 INFO [stdout] (Thread-190) at com.sun.ts.tests.ejb30.sec.permsxml.Client.ValidateCustomPerm(Client.java:117)
\u001b[0m\u001b[0m00:17:31,562 INFO [stdout] (Thread-190) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
\u001b[0m\u001b[0m00:17:31,562 INFO [stdout] (Thread-190) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
\u001b[0m\u001b[0m00:17:31,562 INFO [stdout] (Thread-190) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
\u001b[0m\u001b[0m00:17:31,562 INFO [stdout] (Thread-190) at java.lang.reflect.Method.invoke(Method.java:498)
\u001b[0m\u001b[0m00:17:31,562 INFO [stdout] (Thread-190) at com.sun.ts.lib.harness.EETest.run(EETest.java:596)
\u001b[0m\u001b[0m00:17:31,562 INFO [stdout] (Thread-190) at com.sun.ts.lib.harness.EETest.getPropsReady(EETest.java:486)
\u001b[0m\u001b[0m00:17:31,562 INFO [stdout] (Thread-190) at com.sun.ts.lib.harness.EETest.run(EETest.java:337)
\u001b[0m\u001b[0m00:17:31,562 INFO [stdout] (Thread-190) at com.sun.ts.lib.harness.EETest.run(EETest.java:285)
\u001b[0m\u001b[0m00:17:31,562 INFO [stdout] (Thread-190) at com.sun.ts.tests.ejb30.sec.permsxml.Client.main(Client.java:66)
\u001b[0m\u001b[0m00:17:31,562 INFO [stdout] (Thread-190) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
\u001b[0m\u001b[0m00:17:31,562 INFO [stdout] (Thread-190) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
\u001b[0m\u001b[0m00:17:31,562 INFO [stdout] (Thread-190) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
\u001b[0m\u001b[0m00:17:31,562 INFO [stdout] (Thread-190) at java.lang.reflect.Method.invoke(Method.java:498)
\u001b[0m\u001b[0m00:17:31,562 INFO [stdout] (Thread-190) at org.jboss.as.appclient.service.ApplicationClientStartService$1.run(ApplicationClientStartService.java:99)
\u001b[0m\u001b[0m00:17:31,563 INFO [stdout] (Thread-190) at java.lang.Thread.run(Thread.java:748)
\u001b[0m\u001b[0m00:17:31,563 INFO [stdout] (Thread-190)
\u001b[0m\u001b[0m00:17:31,563 INFO [stdout] (Thread-190) 12-15-2020 00:17:31: cleanup ok
\u001b[0m\u001b[31m00:17:32,563 ERROR [stderr] (Thread-190) STATUS:Failed.Test case throws exception: ValidateCustomPerm test failed:
\u001b[0m\u001b[0m00:17:32,565 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0272: Suspending server
\u001b[0m\u001b[0m00:17:32,568 INFO [org.jboss.as.ejb3] (Thread-2) WFLYEJB0493: EJB subsystem suspension complete
\u001b[0m\u001b[0m00:17:32,569 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested via an OS signal
\u001b[0m\u001b[0m00:17:32,608 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0119: Unbinding connection factory named java:/jms/QueueConnectionFactory2 to alias jms/TopicConnectionFactory2
\u001b[0m\u001b[0m00:17:32,608 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0099: Unbound non-transactional data source: java:/jdbc/DB_no_tx
\u001b[0m\u001b[0m00:17:32,610 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:/jdbc/DBTimer]
\u001b[0m\u001b[0m00:17:32,611 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0002: Unbound mail session [java:/mail/Session]
\u001b[0m\u001b[0m00:17:32,612 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:/JavadbXA]
\u001b[0m\u001b[0m00:17:32,616 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/jms/QueueConnectionFactory2]
\u001b[0m\u001b[0m00:17:32,617 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/jms/TopicConnectionFactory
\u001b[0m\u001b[0m00:17:32,626 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:/jdbc/DB1]
\u001b[0m\u001b[0m00:17:32,649 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
\u001b[0m\u001b[0m00:17:32,655 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0019: Stopped Driver service with driver-name = derby
\u001b[0m\u001b[0m00:17:32,672 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0208: Stopped subdeployment (runtime-name: ejb3_sec_permsxml_client.jar) in 100ms
\u001b[0m\u001b[0m00:17:32,677 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: ejb3_sec_permsxml_ejb.jar) in 105ms
\u001b[0m\u001b[0m00:17:32,709 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment ejb3_sec_permsxml.ear (runtime-name: ejb3_sec_permsxml.ear) in 138ms
\u001b[0m\u001b[0m00:17:32,814 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Preview 22.0.0.Beta1-SNAPSHOT (WildFly Core 14.0.0.Beta4) stopped in 242ms
\u001b[0m
result: Failed. test failed
test result: Failed. test failed
{quote}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (DROOLS-5902) DMN Editor wrong typeRef for DT column
by Matteo Mortari (Jira)
Matteo Mortari created DROOLS-5902:
--------------------------------------
Summary: DMN Editor wrong typeRef for DT column
Key: DROOLS-5902
URL: https://issues.redhat.com/browse/DROOLS-5902
Project: Drools
Issue Type: Bug
Components: DMN Editor
Reporter: Matteo Mortari
Assignee: Guilherme Gomes
Attachments: DMNEditorIssueTypeRefOfDT.mp4
The itemRef for the Decision Table column is not respecting the ItemDefinition
As per attached reproducer video:
[^DMNEditorIssueTypeRefOfDT.mp4]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (WFLY-14234) EJB bean method direct memory buffer leaking
by Mike Zhary (Jira)
[ https://issues.redhat.com/browse/WFLY-14234?page=com.atlassian.jira.plugi... ]
Mike Zhary updated WFLY-14234:
------------------------------
Description:
Wildfly.19.0.1.Final standalone
We're using haproxy to balance ejb calls between wildfly servers.
That's very useful model, but there are problems with it.
All connections are declared as remote-outbound-connection and it works.
{code}
<remote-outbound-connection name="{{ c.name }}" outbound-socket-binding-ref="{{ c.socket_binding }}" protocol="http-remoting" security-realm="{{ c.security_realm }}" username="{{ c.user }}">
<properties>
<property name="SASL_POLICY_NOANONYMOUS" value="false"/>
<property name="SSL_ENABLED" value="false"/>
</properties>
</remote-outbound-connection>
{code}
But there is the problem when some from servers is offline. haproxy send response by http and send RST by tcp, but WF can't make sense of this response it.
Problem can be reprouced when servers listening port, but there is no repsonse for ejb call(in our case it means haproxy doesn't have suitable backend online)
But everything is clear, when port closed or server don't response for a calls.
Haproxy doesn't have feature to don't listen port if backed is offline.
At OS problems shows as huge count(equal to thread count) of connections in state CLOSE_WAIT. That means server had send packet TCP_FIN and client accepted it, but there were no respond on it. In other words WF and it's subsystems didn't agree with closing connection and it becomes to CLOSE_WAIT. At OS side closing connection in sometime and took it as dead(it's normal case)
At WF memory it appears as growing count of objects org.xnio.ByteBufferSlicePool$PooledByteBuffer, that have attribute buffer that holds about 2mb each.
Take a look:
!2020-11-10-112753_563x276_scrot.png|thumbnail!
Problem allocated in XNIO library. There were found a mistake and looks very similar to our problem. XNIO-254
The same time we'd found XNIO-380 and we tried it with last version of this library(snapshot 3.9), no results were there.
We tried get undrestanding ow DMB clean, but did nothing due to too complicated code design.
As per investigations DMB used for an SSL connection, but we don't it.
So we were to patch jboss-remoting class RemoteConnectionProvider.
after that we'd solved issue with leaking of DMB.
Our patched library: [^src_main_java_org_jboss_remoting3_remote_RemoteConnectionProvider.java]
Please take look how this bug can be fixed.
was:
Wildfly.19.0.1.Final standalone
We're using haproxy to balance ejb calls between wildfly servers.
That's very useful model, but there are problems with it.
All connections are declared as remote-outbound-connection and it works.
{code}
<remote-outbound-connection name="{{ c.name }}" outbound-socket-binding-ref="{{ c.socket_binding }}" protocol="http-remoting" security-realm="{{ c.security_realm }}" username="{{ c.user }}">
<properties>
<property name="SASL_POLICY_NOANONYMOUS" value="false"/>
<property name="SSL_ENABLED" value="false"/>
</properties>
</remote-outbound-connection>
{code}
But there is the problem when some from servers is offline. haproxy can't provide data about unavailability and direct memory buffer grows.
Problem can be reprouced when servers listening port, but there is no repsonse for ejb call(in our case it means haproxy doesn't have suitable backend online)
But everything is clear, when port closed or server don't response for a calls.
Haproxy doesn't have feature to don't listen port if backed is offline.
At OS problems shows as huge count(equal to thread count) of connections in state CLOSE_WAIT. That means server had send packet TCP_FIN and client accepted it, but there were no respond on it. In other words WF and it's subsystems didn't agree with closing connection and it becomes to CLOSE_WAIT. At OS side closing connection in sometime and took it as dead(it's normal case)
At WF memory it appears as growing count of objects org.xnio.ByteBufferSlicePool$PooledByteBuffer, that have attribute buffer that holds about 2mb each.
Take a look:
!2020-11-10-112753_563x276_scrot.png|thumbnail!
Problem allocated in XNIO library. There were found a mistake and looks very similar to our problem. XNIO-254
The same time we'd found XNIO-380 and we tried it with last version of this library(snapshot 3.9), no results were there.
We tried get undrestanding ow DMB clean, but did nothing due to too complicated code design.
As per investigations DMB used for an SSL connection, but we don't it.
So we were to patch jboss-remoting class RemoteConnectionProvider.
after that we'd solved issue with leaking of DMB.
Our patched library: [^src_main_java_org_jboss_remoting3_remote_RemoteConnectionProvider.java]
Please take look how this bug can be fixed.
> EJB bean method direct memory buffer leaking
> --------------------------------------------
>
> Key: WFLY-14234
> URL: https://issues.redhat.com/browse/WFLY-14234
> Project: WildFly
> Issue Type: Bug
> Components: EJB, IO
> Affects Versions: 19.0.0.Final
> Reporter: Mike Zhary
> Assignee: Cheng Fang
> Priority: Major
> Attachments: 2020-11-10-112753_563x276_scrot.png, src_main_java_org_jboss_remoting3_remote_RemoteConnectionProvider.java
>
>
> Wildfly.19.0.1.Final standalone
> We're using haproxy to balance ejb calls between wildfly servers.
> That's very useful model, but there are problems with it.
> All connections are declared as remote-outbound-connection and it works.
> {code}
> <remote-outbound-connection name="{{ c.name }}" outbound-socket-binding-ref="{{ c.socket_binding }}" protocol="http-remoting" security-realm="{{ c.security_realm }}" username="{{ c.user }}">
> <properties>
> <property name="SASL_POLICY_NOANONYMOUS" value="false"/>
> <property name="SSL_ENABLED" value="false"/>
> </properties>
> </remote-outbound-connection>
> {code}
> But there is the problem when some from servers is offline. haproxy send response by http and send RST by tcp, but WF can't make sense of this response it.
> Problem can be reprouced when servers listening port, but there is no repsonse for ejb call(in our case it means haproxy doesn't have suitable backend online)
> But everything is clear, when port closed or server don't response for a calls.
> Haproxy doesn't have feature to don't listen port if backed is offline.
> At OS problems shows as huge count(equal to thread count) of connections in state CLOSE_WAIT. That means server had send packet TCP_FIN and client accepted it, but there were no respond on it. In other words WF and it's subsystems didn't agree with closing connection and it becomes to CLOSE_WAIT. At OS side closing connection in sometime and took it as dead(it's normal case)
> At WF memory it appears as growing count of objects org.xnio.ByteBufferSlicePool$PooledByteBuffer, that have attribute buffer that holds about 2mb each.
> Take a look:
> !2020-11-10-112753_563x276_scrot.png|thumbnail!
> Problem allocated in XNIO library. There were found a mistake and looks very similar to our problem. XNIO-254
> The same time we'd found XNIO-380 and we tried it with last version of this library(snapshot 3.9), no results were there.
> We tried get undrestanding ow DMB clean, but did nothing due to too complicated code design.
> As per investigations DMB used for an SSL connection, but we don't it.
> So we were to patch jboss-remoting class RemoteConnectionProvider.
> after that we'd solved issue with leaking of DMB.
> Our patched library: [^src_main_java_org_jboss_remoting3_remote_RemoteConnectionProvider.java]
> Please take look how this bug can be fixed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (WFLY-14234) EJB bean method direct memory buffer leaking
by Mike Zhary (Jira)
[ https://issues.redhat.com/browse/WFLY-14234?page=com.atlassian.jira.plugi... ]
Mike Zhary updated WFLY-14234:
------------------------------
Description:
Wildfly.19.0.1.Final standalone
We're using haproxy to balance ejb calls between wildfly servers.
That's very useful model, but there are problems with it.
All connections are declared as remote-outbound-connection and it works.
{code}
<remote-outbound-connection name="{{ c.name }}" outbound-socket-binding-ref="{{ c.socket_binding }}" protocol="http-remoting" security-realm="{{ c.security_realm }}" username="{{ c.user }}">
<properties>
<property name="SASL_POLICY_NOANONYMOUS" value="false"/>
<property name="SSL_ENABLED" value="false"/>
</properties>
</remote-outbound-connection>
{code}
But there is the problem when some from servers is offline. haproxy send response by http and sends RST by tcp, but WF can't make sense of this response.
Problem can be reprouced when servers listening port, but there is no repsonse for ejb call(in our case it means haproxy doesn't have suitable backend online)
But everything is clear, when port closed or server don't response for a calls.
Haproxy doesn't have feature to don't listen port if backed is offline.
At OS problems shows as huge count(equal to thread count) of connections in state CLOSE_WAIT. That means server had send packet TCP_FIN and client accepted it, but there were no respond on it. In other words WF and it's subsystems didn't agree with closing connection and it becomes to CLOSE_WAIT. At OS side closing connection in sometime and took it as dead(it's normal case)
At WF memory it appears as growing count of objects org.xnio.ByteBufferSlicePool$PooledByteBuffer, that have attribute buffer that holds about 2mb each.
Take a look:
!2020-11-10-112753_563x276_scrot.png|thumbnail!
Problem allocated in XNIO library. There were found a mistake and looks very similar to our problem. XNIO-254
The same time we'd found XNIO-380 and we tried it with last version of this library(snapshot 3.9), no results were there.
We tried get undrestanding ow DMB clean, but did nothing due to too complicated code design.
As per investigations DMB used for an SSL connection, but we don't it.
So we were to patch jboss-remoting class RemoteConnectionProvider.
after that we'd solved issue with leaking of DMB.
Our patched library: [^src_main_java_org_jboss_remoting3_remote_RemoteConnectionProvider.java]
Please take look how this bug can be fixed.
was:
Wildfly.19.0.1.Final standalone
We're using haproxy to balance ejb calls between wildfly servers.
That's very useful model, but there are problems with it.
All connections are declared as remote-outbound-connection and it works.
{code}
<remote-outbound-connection name="{{ c.name }}" outbound-socket-binding-ref="{{ c.socket_binding }}" protocol="http-remoting" security-realm="{{ c.security_realm }}" username="{{ c.user }}">
<properties>
<property name="SASL_POLICY_NOANONYMOUS" value="false"/>
<property name="SSL_ENABLED" value="false"/>
</properties>
</remote-outbound-connection>
{code}
But there is the problem when some from servers is offline. haproxy send response by http and send RST by tcp, but WF can't make sense of this response.
Problem can be reprouced when servers listening port, but there is no repsonse for ejb call(in our case it means haproxy doesn't have suitable backend online)
But everything is clear, when port closed or server don't response for a calls.
Haproxy doesn't have feature to don't listen port if backed is offline.
At OS problems shows as huge count(equal to thread count) of connections in state CLOSE_WAIT. That means server had send packet TCP_FIN and client accepted it, but there were no respond on it. In other words WF and it's subsystems didn't agree with closing connection and it becomes to CLOSE_WAIT. At OS side closing connection in sometime and took it as dead(it's normal case)
At WF memory it appears as growing count of objects org.xnio.ByteBufferSlicePool$PooledByteBuffer, that have attribute buffer that holds about 2mb each.
Take a look:
!2020-11-10-112753_563x276_scrot.png|thumbnail!
Problem allocated in XNIO library. There were found a mistake and looks very similar to our problem. XNIO-254
The same time we'd found XNIO-380 and we tried it with last version of this library(snapshot 3.9), no results were there.
We tried get undrestanding ow DMB clean, but did nothing due to too complicated code design.
As per investigations DMB used for an SSL connection, but we don't it.
So we were to patch jboss-remoting class RemoteConnectionProvider.
after that we'd solved issue with leaking of DMB.
Our patched library: [^src_main_java_org_jboss_remoting3_remote_RemoteConnectionProvider.java]
Please take look how this bug can be fixed.
> EJB bean method direct memory buffer leaking
> --------------------------------------------
>
> Key: WFLY-14234
> URL: https://issues.redhat.com/browse/WFLY-14234
> Project: WildFly
> Issue Type: Bug
> Components: EJB, IO
> Affects Versions: 19.0.0.Final
> Reporter: Mike Zhary
> Assignee: Cheng Fang
> Priority: Major
> Attachments: 2020-11-10-112753_563x276_scrot.png, src_main_java_org_jboss_remoting3_remote_RemoteConnectionProvider.java
>
>
> Wildfly.19.0.1.Final standalone
> We're using haproxy to balance ejb calls between wildfly servers.
> That's very useful model, but there are problems with it.
> All connections are declared as remote-outbound-connection and it works.
> {code}
> <remote-outbound-connection name="{{ c.name }}" outbound-socket-binding-ref="{{ c.socket_binding }}" protocol="http-remoting" security-realm="{{ c.security_realm }}" username="{{ c.user }}">
> <properties>
> <property name="SASL_POLICY_NOANONYMOUS" value="false"/>
> <property name="SSL_ENABLED" value="false"/>
> </properties>
> </remote-outbound-connection>
> {code}
> But there is the problem when some from servers is offline. haproxy send response by http and sends RST by tcp, but WF can't make sense of this response.
> Problem can be reprouced when servers listening port, but there is no repsonse for ejb call(in our case it means haproxy doesn't have suitable backend online)
> But everything is clear, when port closed or server don't response for a calls.
> Haproxy doesn't have feature to don't listen port if backed is offline.
> At OS problems shows as huge count(equal to thread count) of connections in state CLOSE_WAIT. That means server had send packet TCP_FIN and client accepted it, but there were no respond on it. In other words WF and it's subsystems didn't agree with closing connection and it becomes to CLOSE_WAIT. At OS side closing connection in sometime and took it as dead(it's normal case)
> At WF memory it appears as growing count of objects org.xnio.ByteBufferSlicePool$PooledByteBuffer, that have attribute buffer that holds about 2mb each.
> Take a look:
> !2020-11-10-112753_563x276_scrot.png|thumbnail!
> Problem allocated in XNIO library. There were found a mistake and looks very similar to our problem. XNIO-254
> The same time we'd found XNIO-380 and we tried it with last version of this library(snapshot 3.9), no results were there.
> We tried get undrestanding ow DMB clean, but did nothing due to too complicated code design.
> As per investigations DMB used for an SSL connection, but we don't it.
> So we were to patch jboss-remoting class RemoteConnectionProvider.
> after that we'd solved issue with leaking of DMB.
> Our patched library: [^src_main_java_org_jboss_remoting3_remote_RemoteConnectionProvider.java]
> Please take look how this bug can be fixed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months