August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8449) EJB contextData not sent back to client in response

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-8449?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-8449: ------------------------------- Fix Version/s: 11.0.0.CR1 (was: 11.0.0.Beta1) > EJB contextData not sent back to client in response > --------------------------------------------------- > > Key: WFLY-8449 > URL: https://issues.jboss.org/browse/WFLY-8449 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Fedor Gavrilov > Assignee: Fedor Gavrilov > Labels: downstream_dependency, ejb > Fix For: 11.0.0.CR1 > > > With former JBoss versions it was possible to pass context beside the method invocation from the client to the server and back. This was done via (AOP) interceptors. > Since AS7 and WildFly the only possibility is to pass such context from the client to the server. > It should also possible to pass serializeable objects from the server side to the client if the invocation returns and have a client side interceptor to read that informations. > This was used to return i.e. tracking or additional usefull informations. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8390) Correct RemotingLoginModule test failures.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-8390?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-8390: ------------------------------- Fix Version/s: 11.0.0.CR1 (was: 11.0.0.Beta1) > Correct RemotingLoginModule test failures. > ------------------------------------------ > > Key: WFLY-8390 > URL: https://issues.jboss.org/browse/WFLY-8390 > Project: WildFly > Issue Type: Bug > Components: Security, Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 11.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8250) Ensure all Elytron subsystem resources that depend on the core services also record a capability dependency.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-8250?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-8250: ------------------------------- Fix Version/s: 11.0.0.CR1 (was: 11.0.0.Beta1) > Ensure all Elytron subsystem resources that depend on the core services also record a capability dependency. > ------------------------------------------------------------------------------------------------------------ > > Key: WFLY-8250 > URL: https://issues.jboss.org/browse/WFLY-8250 > Project: WildFly > Issue Type: Enhancement > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 11.0.0.CR1 > > > This builds on https://issues.jboss.org/browse/WFCORE-1106 so we can skip runtime steps when the dependent services are not available. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9009) Upgrade Jackson to 2.8.9

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9009?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9009: ------------------------------- Fix Version/s: 11.0.0.CR1 (was: 11.0.0.Beta1) > Upgrade Jackson to 2.8.9 > ------------------------ > > Key: WFLY-9009 > URL: https://issues.jboss.org/browse/WFLY-9009 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Jason Greene > Assignee: Jason Greene > Fix For: 11.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9111) Some tests from manualmode is unable to start with node0 and node1 properties

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9111?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9111: ------------------------------- Fix Version/s: 11.0.0.CR1 (was: 11.0.0.Beta1) > Some tests from manualmode is unable to start with node0 and node1 properties > ----------------------------------------------------------------------------- > > Key: WFLY-9111 > URL: https://issues.jboss.org/browse/WFLY-9111 > Project: WildFly > Issue Type: Bug > Components: JCA, Test Suite > Reporter: Richard Janík > Assignee: Richard Janík > Fix For: 11.0.0.CR1 > > > *Description of problem:* > Some tests from manualmode is unable to start with node0 and node1 properties. > It's caused by [these new containers in arquillian.xml|https://github.com/jbossas/jboss-eap7/pull/1935/files#diff...] > These tests are affected by this issue: > {noformat} > org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteOutboundConnectionReconnectTestCase > org.jboss.as.test.manualmode.ejb.client.outbound.connection.security.ElytronRemoteOutboundConnectionTestCase > org.jboss.as.test.manualmode.ejb.client.reconnect.EJBClientReconnectionTestCase > org.jboss.as.test.manualmode.jca.connectionlistener.ConnectionListenerTestCase > org.jboss.as.test.manualmode.jca.workmanager.distributed.DwmAlwaysTestCase > org.jboss.as.test.manualmode.jca.workmanager.distributed.DwmNeverTestCase > org.jboss.as.test.manualmode.jca.workmanager.distributed.DwmWatermarkTestCase > org.jboss.as.test.manualmode.layered.LayeredDistributionTestCase > org.jboss.as.test.manualmode.messaging.ha.ReplicatedFailoverTestCase > org.jboss.as.test.manualmode.messaging.ha.SharedStoreFailoverTestCase > org.jboss.as.test.manualmode.security.OutboundLdapConnectionClientCertTestCase > org.jboss.as.test.manualmode.security.OutboundLdapConnectionTestCase > org.jboss.as.test.manualmode.security.SecuredDataSourceTestCase > org.jboss.as.test.manualmode.security.VaultSystemPropertyOnServerStartTestCase > org.jboss.as.test.manualmode.transaction.ObjectStoreTypeTestCase > org.jboss.as.test.manualmode.web.ssl.CertificateRolesLoginModuleTestCase > org.jboss.as.test.manualmode.web.ssl.DatabaseCertLoginModuleTestCase > org.jboss.as.test.manualmode.web.ssl.HTTPSWebConnectorTestCase > org.jboss.as.test.manualmode.weld.extension.BeforeShutdownJNDILookupTestCase > org.jboss.as.test.manualmode.ws.ReloadRequiringChangesTestCase > org.jboss.as.test.manualmode.ws.ReloadWSDLPublisherTestCase > {noformat} > *How reproducible:* > Always > *Steps to Reproduce:* > # ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 -Djboss.dist=/home/mkopecky/playground/eap/7.1.0.ER2.2/jboss-eap-7.1 -DtestLogToFile=false -Dts.noSmoke -Dts.manualmode -Dtest=RemoteOutboundConnectionReconnectTestCase > *StackTrace:* > {noformat} > Caused by: java.util.concurrent.TimeoutException: Managed server was not started within [60] s > at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:161) > ... 73 more > {noformat} > *Expected results:* > No errors -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9005) Ensure tests use unique names for principal-transformers and principal-decoders

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9005?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9005: ------------------------------- Fix Version/s: 11.0.0.CR1 (was: 11.0.0.Beta1) > Ensure tests use unique names for principal-transformers and principal-decoders > ------------------------------------------------------------------------------- > > Key: WFLY-9005 > URL: https://issues.jboss.org/browse/WFLY-9005 > Project: WildFly > Issue Type: Task > Components: Security, Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 11.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8905) Remove wildfly-config.xml from app client test in basic testsuite.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-8905?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-8905: ------------------------------- Fix Version/s: 11.0.0.CR1 (was: 11.0.0.Beta1) > Remove wildfly-config.xml from app client test in basic testsuite. > ------------------------------------------------------------------ > > Key: WFLY-8905 > URL: https://issues.jboss.org/browse/WFLY-8905 > Project: WildFly > Issue Type: Bug > Components: Security, Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 11.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3146) Prevent default loading of legacy ManagementXml and AuditLogXml impls

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3146?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3146: ------------------------------------- Description: The legacy variants of ManagementXml and AuditLogXml are getting loaded but aren't used, which is a waste of boot time and of metaspace. It turns out that the idiom of having the impls extend an abstract base class and then having a static factory method in the abstract class results in all the different impl classes being loaded into memory. Simply changing the abstract base class to an interface eliminates the problem. While I'm at it, the legacy impls still have code for the writeXXX methods, which should never be called. So I'll clean that out and replace with a default impl that throws UnsupportedOperationException. I'll do some other code cleanup on these too, removing unused params, etc. This should save 118K of metaspace. was: The legacy variants of ManagementXml and AuditLogXml are getting loaded but aren't used, which is a waste of boot time and of metaspace. It turns out that the idiom of having the impls extend an abstract base class and then having a static factory method in the abstract class results in all the different impl classes being loaded into memory. Simply changing the abstract base class to an interface eliminates the problem. While I'm at it, the legacy impls still have code for the writeXXX methods, which should never be called. So I'll clean that out and replace with a default impl that throws UnsupportedOperationException. I'll do some other code cleanup on these too, removing unused params, etc. > Prevent default loading of legacy ManagementXml and AuditLogXml impls > --------------------------------------------------------------------- > > Key: WFCORE-3146 > URL: https://issues.jboss.org/browse/WFCORE-3146 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 3.0.0.CR1 > > > The legacy variants of ManagementXml and AuditLogXml are getting loaded but aren't used, which is a waste of boot time and of metaspace. > It turns out that the idiom of having the impls extend an abstract base class and then having a static factory method in the abstract class results in all the different impl classes being loaded into memory. Simply changing the abstract base class to an interface eliminates the problem. > While I'm at it, the legacy impls still have code for the writeXXX methods, which should never be called. So I'll clean that out and replace with a default impl that throws UnsupportedOperationException. > I'll do some other code cleanup on these too, removing unused params, etc. > This should save 118K of metaspace. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3145) Comment out unused Logger methods

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3145?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3145: ------------------------------------- Fix Version/s: 3.0.0.CR1 > Comment out unused Logger methods > --------------------------------- > > Key: WFCORE-3145 > URL: https://issues.jboss.org/browse/WFCORE-3145 > Project: WildFly Core > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 3.0.0.CR1 > > > The various XXXLogger/XXXMessages interfaces over the years have accumulated a lot of no-longer-used methods. Comment these out to save the memory space used by the interface itself and by the implementation that's generated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3146) Prevent default loading of legacy ManagementXml and AuditLogXml impls

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3146?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3146: ------------------------------------- Fix Version/s: 3.0.0.CR1 > Prevent default loading of legacy ManagementXml and AuditLogXml impls > --------------------------------------------------------------------- > > Key: WFCORE-3146 > URL: https://issues.jboss.org/browse/WFCORE-3146 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 3.0.0.CR1 > > > The legacy variants of ManagementXml and AuditLogXml are getting loaded but aren't used, which is a waste of boot time and of metaspace. > It turns out that the idiom of having the impls extend an abstract base class and then having a static factory method in the abstract class results in all the different impl classes being loaded into memory. Simply changing the abstract base class to an interface eliminates the problem. > While I'm at it, the legacy impls still have code for the writeXXX methods, which should never be called. So I'll clean that out and replace with a default impl that throws UnsupportedOperationException. > I'll do some other code cleanup on these too, removing unused params, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2017