[JBoss JIRA] (WFLY-12464) Remove the legacy security subsystem from the config used by testsuite/integration/elytron
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-12464?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-12464:
---------------------------------
Fix Version/s: 18.0.0.Final
(was: 18.0.0.Beta1)
> Remove the legacy security subsystem from the config used by testsuite/integration/elytron
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-12464
> URL: https://issues.jboss.org/browse/WFLY-12464
> Project: WildFly
> Issue Type: Task
> Components: Security, Test Suite
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
> Fix For: 18.0.0.Final
>
>
> The CLI script that sets up the config used in testsuite/integration/elytron leaves an empty shell legacy security subsystem around, saying:
> {code}
> # datasources and ejb3 still has dependency on legacy security subsystem, so we can't remove it completely now
> {code}
> But actually removing it, the tests all pass but two. And one of those fails simply because it includes a setup task management up to disable JACC in the legacy subsystem, which would not be necessary if it were not present.
> The other failure I believe is due to a flaw in the Elytron subsystem that will be fixed by WFCORE-4640. Basically in the absence of the legacy subsystem no DUP adds JASPI or JACC dependencies to the deployment module.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (WFLY-12458) WebServices tests failing in IBM JDK8
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-12458?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-12458:
---------------------------------
Fix Version/s: 18.0.0.Final
(was: 18.0.0.Beta1)
> WebServices tests failing in IBM JDK8
> -------------------------------------
>
> Key: WFLY-12458
> URL: https://issues.jboss.org/browse/WFLY-12458
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Environment: java version "1.8.0_211"
> Java(TM) SE Runtime Environment (build 8.0.5.36 - pxa6480sr5fp36-20190510_01(SR5 FP36))
> IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20190502_415899 (JIT enabled, AOT enabled)
> OpenJ9 - 46e57f9
> OMR - 06a046a
> IBM - 0b909bf)
> JCL - 20190409_01 based on Oracle jdk8u211-b25
> Reporter: Richard Opalka
> Assignee: Jim Ma
> Priority: Major
> Fix For: 18.0.0.Final
>
>
> [ERROR] EJBSignTestCase.signedRequest:86 » SOAPFault MustUnderstand headers: [{http://...
> [ERROR] SignTestCase.signedRequest:88 » SOAPFault MustUnderstand headers: [{http://doc...
> [ERROR] EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromAlice:90 » SOAPFault
> [ERROR] EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromJohn:102 » SOAPFault
> [ERROR] EJBSignEncryptTestCase.encryptedAndSignedRequest:88 » SOAPFault MustUnderstand...
> [ERROR] SignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromAlice:91 » SOAPFault
> [ERROR] SignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromJohn:103 » SOAPFault
> [ERROR] SignEncryptTestCase.encryptedAndSignedRequest:90 » SOAPFault MustUnderstand he...
> [ERROR] WSBearerElytronSecurityPropagationTestCase.testBearer:133 » SOAPFault MustUnde...
> [ERROR] WSBearerSecurityPropagationTestCase.testBearer:133 » SOAPFault MustUnderstand ...
> [ERROR] WSTrustTestCase.test:319 » SOAPFault MustUnderstand headers: [{http://docs.oas...
> [ERROR] WSTrustTestCase.testActAs:442 » SOAPFault MustUnderstand headers: [{http://doc...
> [ERROR] WSTrustTestCase.testBearer:553 » SOAPFault MustUnderstand headers: [{http://do...
> [ERROR] WSTrustTestCase.testHolderOfKey:494 » SOAPFault MustUnderstand headers: [{http...
> [ERROR] WSTrustTestCase.testNoClientCallback:384 » SOAPFault MustUnderstand headers: [...
> [ERROR] WSTrustTestCase.testNoSignatureUsername:415 » SOAPFault MustUnderstand headers...
> [ERROR] WSTrustTestCase.testOnBehalfOf:469 » SOAPFault MustUnderstand headers: [{http:...
> [ERROR] WSTrustTestCase.testPicketLink:526 » SOAPFault MustUnderstand headers: [{http:...
> [ERROR] WSTrustTestCase.testUsingEPR:351 » SOAPFault MustUnderstand headers: [{http://...
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (WFLY-11293) Add attribute to model which will indicate that backup is synchronized with live server
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11293?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-11293:
---------------------------------
Fix Version/s: 18.0.0.Beta1
> Add attribute to model which will indicate that backup is synchronized with live server
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-11293
> URL: https://issues.jboss.org/browse/WFLY-11293
> Project: WildFly
> Issue Type: Feature Request
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: Emmanuel Hugonnet
> Priority: Critical
> Fix For: 18.0.0.Beta1
>
>
> If HA is configured with replicated journal then it takes some time to backup to synchronize with live server. Once backup is in sync with live then following information appears in server.log:
> {code}
> 13:20:00,739 INFO [org.apache.activemq.artemis.core.server] (Thread-3 (ActiveMQ-client-netty-threads-457000966)) AMQ221024: Backup server ActiveMQServerImpl::serverUUID=bc015b34-fd73-11e5-80ca-1b35f669abb8 is synchronized with live-server.
> 13:20:01,500 INFO [org.apache.activemq.artemis.core.server] (Thread-2 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@41f992ab-83559664)) AMQ221031: backup announced
> {code}
> Reading server logs to see whether backup is in sync is not convinient and user friendly way. Could we add this information to model so it can be detected through CLI command?
> New attribute with name {{synchronized-with-live}} should be added to {{/subsystem=messaging-activemq/server=default/ha-policy=replication-slave}}
> This information can be gathered by calling: {{SharedNothingBackupActivation.isRemoteBackupUpToDate()}}
> Additionally we should provide this attribute also in replicated live server in: {{/subsystem=messaging-activemq/server=default/ha-policy=replication-master}} as Administrator might want to know whether live can be shutdown.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (WFLY-12304) Upgrade Apache Artemis from 2.9.0 to 2.10.0
by Clebert Suconic (Jira)
[ https://issues.jboss.org/browse/WFLY-12304?page=com.atlassian.jira.plugin... ]
Clebert Suconic edited comment on WFLY-12304 at 9/4/19 7:24 PM:
----------------------------------------------------------------
It's definitely the netty-xnio-transport not being able to handle DefaultFileRegion
I tried debugging netty-xnio-transport, around AbstractXnioSocketChannel, and it's not possible to handle FileRegion
It seems to me that AbstractXnioSocketChannel is missing some calls on he chain as the write is never called for any FileRegion:
https://github.com/xnio/netty-xnio-transport/blob/b301ada03be308ea2751ae6...
Debugging this more carefully, I realized the object sent is actually an implementation of FileRegion, and the write is not being completed.
was (Author: clebert.suconic):
It's definitely the netty-xnio-transport not being able to handle DefaultFileRegion
I tried debugging netty-xnio-transport, around AbstractXnioSocketChannel, and it's not possible to handle FileRegion
It seems to me that AbstractXnioSocketChannel is missing some calls on he chain as the write is never called for any FileRegion:
https://github.com/xnio/netty-xnio-transport/blob/0.1/src/main/java/org/x...
Debugging this more carefully, I realized the object sent is actually an implementation of FileRegion, and the write is not being completed.
> Upgrade Apache Artemis from 2.9.0 to 2.10.0
> -------------------------------------------
>
> Key: WFLY-12304
> URL: https://issues.jboss.org/browse/WFLY-12304
> Project: WildFly
> Issue Type: Component Upgrade
> Components: JMS
> Reporter: Martin Stefanko
> Assignee: Emmanuel Hugonnet
> Priority: Blocker
> Labels: blocker-WF18, downstream_dependency
>
> Upgrade Apache Artemis from 2.9.0.Final to 2.10.0.Final.
> Due to HA issue with Apache Artemis 2.10.0 this may not be the final version upgrade
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months