August 2019 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-4181) Remove TS workarounds not needed anymore

by Jan Blizňák (Jira)

Jan Blizňák created JBWS-4181: --------------------------------- Summary: Remove TS workarounds not needed anymore Key: JBWS-4181 URL: https://issues.jboss.org/browse/JBWS-4181 Project: JBoss Web Services Issue Type: Task Reporter: Jan Blizňák Assignee: Jan Blizňák Remove leftover workarounds for tests. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4180) UsernameAuthorizationTestCase & UsernameAuthorizationDigestTestCase fail with elytron profile after upgrade to CXF 3.3.x

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4180?page=com.atlassian.jira.plugin.... ] Jan Blizňák commented on JBWS-4180: ----------------------------------- Looking at PR https://github.com/jbossws/jbossws-cxf/commit/149c0fc8d19e566541d919e73b6... I can see that method is removed https://github.com/jbossws/jbossws-cxf/commit/149c0fc8d19e566541d919e73b6... but this makes the CustomValidator class unused, this might not be the cause of the issue reported here but if it is a dead code, it should be removed too. > UsernameAuthorizationTestCase & UsernameAuthorizationDigestTestCase fail with elytron profile after upgrade to CXF 3.3.x > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBWS-4180 > URL: https://issues.jboss.org/browse/JBWS-4180 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.3.0.Final > Reporter: Jan Blizňák > Assignee: Jim Ma > Priority: Critical > > The WS-Security Policy tests org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationTestCase and org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationDigestTestCase fail when running testsuite with elytron profile (server security configured via elytron subsystem). > The breaking commit is https://github.com/jbossws/jbossws-cxf/commit/149c0fc8d19e566541d919e73b6... > To reproduce: > {code:java} > # last commit that passes > git checkout fbdbe55e6ff686cad85be6552e1139efb87645f8 > mvn clean verify -Pwildfly1600 -pl :jbossws-cxf-specific-tests -am -Dtest=UsernameAuthorizationTestCaseUsernameAuthorizationDigestTestCase, -DadditionalGroovyScriptSuffix=-elytron > # fails > git checkout 149c0fc8d19e566541d919e73b608ae53ca3fefb > mvn clean verify -Pwildfly1600 -pl :jbossws-cxf-specific-tests -am -Dtest=UsernameAuthorizationTestCase,UsernameAuthorizationDigestTestCase -DadditionalGroovyScriptSuffix=-elytron > # passes without elytron configuration > mvn clean verify -Pwildfly1600 -pl :jbossws-cxf-specific-tests -am -Dtest=UsernameAuthorizationTestCase,UsernameAuthorizationDigestTestCase > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4180) UsernameAuthorizationTestCase & UsernameAuthorizationDigestTestCase fail with elytron profile after upgrade to CXF 3.3.x

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4180?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4180: ------------------------------ Assignee: Jim Ma > UsernameAuthorizationTestCase & UsernameAuthorizationDigestTestCase fail with elytron profile after upgrade to CXF 3.3.x > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBWS-4180 > URL: https://issues.jboss.org/browse/JBWS-4180 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.3.0.Final > Reporter: Jan Blizňák > Assignee: Jim Ma > Priority: Critical > > The WS-Security Policy tests org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationTestCase and org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationDigestTestCase fail when running testsuite with elytron profile (server security configured via elytron subsystem). > The breaking commit is https://github.com/jbossws/jbossws-cxf/commit/149c0fc8d19e566541d919e73b6... > To reproduce: > {code:java} > # last commit that passes > git checkout fbdbe55e6ff686cad85be6552e1139efb87645f8 > mvn clean verify -Pwildfly1600 -pl :jbossws-cxf-specific-tests -am -Dtest=UsernameAuthorizationTestCaseUsernameAuthorizationDigestTestCase, -DadditionalGroovyScriptSuffix=-elytron > # fails > git checkout 149c0fc8d19e566541d919e73b608ae53ca3fefb > mvn clean verify -Pwildfly1600 -pl :jbossws-cxf-specific-tests -am -Dtest=UsernameAuthorizationTestCase,UsernameAuthorizationDigestTestCase -DadditionalGroovyScriptSuffix=-elytron > # passes without elytron configuration > mvn clean verify -Pwildfly1600 -pl :jbossws-cxf-specific-tests -am -Dtest=UsernameAuthorizationTestCase,UsernameAuthorizationDigestTestCase > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4180) UsernameAuthorizationTestCase & UsernameAuthorizationDigestTestCase fail with elytron profile after upgrade to CXF 3.3.x

by Jan Blizňák (Jira)

Jan Blizňák created JBWS-4180: --------------------------------- Summary: UsernameAuthorizationTestCase & UsernameAuthorizationDigestTestCase fail with elytron profile after upgrade to CXF 3.3.x Key: JBWS-4180 URL: https://issues.jboss.org/browse/JBWS-4180 Project: JBoss Web Services Issue Type: Bug Affects Versions: jbossws-cxf-5.3.0.Final Reporter: Jan Blizňák The WS-Security Policy tests org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationTestCase and org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationDigestTestCase fail when running testsuite with elytron profile (server security configured via elytron subsystem). The breaking commit is https://github.com/jbossws/jbossws-cxf/commit/149c0fc8d19e566541d919e73b6... To reproduce: {code:java} # last commit that passes git checkout fbdbe55e6ff686cad85be6552e1139efb87645f8 mvn clean verify -Pwildfly1600 -pl :jbossws-cxf-specific-tests -am -Dtest=UsernameAuthorizationTestCaseUsernameAuthorizationDigestTestCase, -DadditionalGroovyScriptSuffix=-elytron # fails git checkout 149c0fc8d19e566541d919e73b608ae53ca3fefb mvn clean verify -Pwildfly1600 -pl :jbossws-cxf-specific-tests -am -Dtest=UsernameAuthorizationTestCase,UsernameAuthorizationDigestTestCase -DadditionalGroovyScriptSuffix=-elytron # passes without elytron configuration mvn clean verify -Pwildfly1600 -pl :jbossws-cxf-specific-tests -am -Dtest=UsernameAuthorizationTestCase,UsernameAuthorizationDigestTestCase {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4179) WS integration with WildFly Elytron - AuthenticationClient for Authentication / SSL

by Diana Vilkolakova (Jira)

[ https://issues.jboss.org/browse/JBWS-4179?page=com.atlassian.jira.plugin.... ] Diana Vilkolakova updated JBWS-4179: ------------------------------------ Git Pull Request: https://github.com/jbossws/jbossws-spi/pull/5, https://github.com/jbossws/jbossws-common/pull/18, https://github.com/jbossws/jbossws-cxf/pull/108 > WS integration with WildFly Elytron - AuthenticationClient for Authentication / SSL > ----------------------------------------------------------------------------------- > > Key: JBWS-4179 > URL: https://issues.jboss.org/browse/JBWS-4179 > Project: JBoss Web Services > Issue Type: Feature Request > Reporter: Diana Vilkolakova > Assignee: Diana Vilkolakova > Priority: Major > > This feature request is about making use of authentication configuration for Elytron on the client side of the Web Services deployment. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3802) Empty response returned when SOAP Fault is thrown from an endpoint having WS-Security Policy Signature profile

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/JBWS-3802?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3802: ----------------------------------------------- Jan Kurik <jkurik(a)redhat.com> changed the Status of [bug 1110631|https://bugzilla.redhat.com/show_bug.cgi?id=1110631] from VERIFIED to CLOSED > Empty response returned when SOAP Fault is thrown from an endpoint having WS-Security Policy Signature profile > -------------------------------------------------------------------------------------------------------------- > > Key: JBWS-3802 > URL: https://issues.jboss.org/browse/JBWS-3802 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.4, jbossws-cxf-4.3 > Reporter: Tadayoshi Sato > Assignee: Jim Ma > Priority: Major > Fix For: jbossws-cxf-5.0.0.Beta1 > > > Please port [CXF-5810|https://issues.apache.org/jira/browse/CXF-5810], which is the root cause of the issue, to JBoss WS. > When a web service has a WS-Security Signature policy in its WSDL and throws a SOAP Fault, it returns an empty HTTP response that has zero-length of content to client instead of the SOAP Fault. > This happens only with Signature policy and doesn't happen with any other WS-Security policies like UsernameToken, or without WS-Security. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3858) Misconfigured TCCL during endpoint method invocations when Spring integration is enabled

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/JBWS-3858?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3858: ----------------------------------------------- Jan Kurik <jkurik(a)redhat.com> changed the Status of [bug 1174922|https://bugzilla.redhat.com/show_bug.cgi?id=1174922] from VERIFIED to CLOSED > Misconfigured TCCL during endpoint method invocations when Spring integration is enabled > ---------------------------------------------------------------------------------------- > > Key: JBWS-3858 > URL: https://issues.jboss.org/browse/JBWS-3858 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Major > Fix For: jbossws-cxf-5.0.0.Beta3 > > > When the Spring integration is enabled, the TCCL that's set at the time the user endpoint methods are executed is an instance of DelegateClassLoader whose parent actually grants user visibility over classes he should only be given access if he declared a proper module dependency. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3847) Memory leak in JBoss WS CXF Client's HandlerChainSortInterceptor

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/JBWS-3847?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3847: ----------------------------------------------- Jan Kurik <jkurik(a)redhat.com> changed the Status of [bug 1155490|https://bugzilla.redhat.com/show_bug.cgi?id=1155490] from VERIFIED to CLOSED > Memory leak in JBoss WS CXF Client's HandlerChainSortInterceptor > ---------------------------------------------------------------- > > Key: JBWS-3847 > URL: https://issues.jboss.org/browse/JBWS-3847 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.3 > Reporter: Tadayoshi Sato > Assignee: Alessio Soldano > Priority: Major > Fix For: jbossws-cxf-4.3.2, jbossws-cxf-5.0.0.Beta2 > > > {{HandlerChainSortInterceptor.handleMessage(Message)}} sorts and sets JAX-WS handlers every time it handles a SOAP message: > {code:java} > public void handleMessage(Message message) throws Fault > { > if (binding != null) { > @SuppressWarnings("rawtypes") > List<Handler> list = binding.getHandlerChain(); > if (list != null && !list.isEmpty()) { > Collections.sort(list, comparator); > binding.setHandlerChain(list); > } > } > } > {code} > However, inside the {{org.apache.cxf.jaxws.binding.AbstractBindingImpl}} and {{org.apache.cxf.jaxws.support.JaxWsEndpointImpl}} implementations the handler chain is not reset every time but piled up with interceptors, which leads to subtle but indefinite memory leak in JBoss WS CXF client. > Furthermore, {{org.apache.cxf.jaxws.support.JaxWsEndpointImpl}} holds the interceptors as a kind of {{java.util.concurrent.CopyOnWriteArrayList}}. So modifying the growing list of interceptors per each message should cause a growing performance drawback, which is also not a good implementation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3842) Cannot boot server with 2+ handlers in the same predefined configuration handler chain

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/JBWS-3842?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3842: ----------------------------------------------- Jan Kurik <jkurik(a)redhat.com> changed the Status of [bug 1153954|https://bugzilla.redhat.com/show_bug.cgi?id=1153954] from VERIFIED to CLOSED > Cannot boot server with 2+ handlers in the same predefined configuration handler chain > -------------------------------------------------------------------------------------- > > Key: JBWS-3842 > URL: https://issues.jboss.org/browse/JBWS-3842 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf, jbossws-integration > Affects Versions: jbossws-cxf-4.3 > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Major > Fix For: jbossws-cxf-4.3.2, jbossws-cxf-5.0.0.Beta2 > > > Commit https://github.com/wildfly/wildfly/commit/e32f27d433ad3da41ef042f1ad9b950... introduced a regressions when having multiple handlers in the same handler-chain within one of the pre-defined configuration in the webservices subsystem: > {noformat} > 5:49:24,653 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.ws.endpoint-config.Recording-Endpoint-Config.pre-handler-chain.recording-handlers: org.jboss.msc.service.StartException in service jboss.ws.endpoint-config.Recording-Endpoint-Config.pre-handler-chain.recording-handlers: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_60] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_60] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_60] > Caused by: org.jboss.msc.inject.InjectionException: Value already set for this injector > at org.jboss.msc.inject.RetainingInjector.inject(RetainingInjector.java:50) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.as.webservices.dmr.ListInjector.inject(ListInjector.java:23) > at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:55) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl.doInject(ServiceControllerImpl.java:1672) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl.access$2000(ServiceControllerImpl.java:51) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.performInjections(ServiceControllerImpl.java:1917) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1876) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > ... 3 more > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3838) Predefined configuration handlers executing in different order when server is restarted

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/JBWS-3838?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3838: ----------------------------------------------- Jan Kurik <jkurik(a)redhat.com> changed the Status of [bug 1153960|https://bugzilla.redhat.com/show_bug.cgi?id=1153960] from VERIFIED to CLOSED > Predefined configuration handlers executing in different order when server is restarted > --------------------------------------------------------------------------------------- > > Key: JBWS-3838 > URL: https://issues.jboss.org/browse/JBWS-3838 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.3 > Reporter: David Boeren > Assignee: Alessio Soldano > Priority: Major > Fix For: jbossws-cxf-4.3.2, jbossws-cxf-5.0.0.Beta2 > > > Handler order can change after a reboot, which causes problems when one handler depends on the action of another. > * Description of the problem > The flow is basically the following: > 1) the container model is parsed; it can include jaxws configs, which are composed > of jaxws handler chains, which in turn has one or multiple jaxws handlers > 2) we have add operations for each jaxws handler and jaxws handler > chain. Each of them starts a service, which builds up the corresponding > metadata to be later used by jbossws; proper dependencies are set > between those services, so that for instance the service for a handler > chain waits for all its handlers' services. > 3) when the service for the handler chain runs, it gets the info from > the handler services and them in the chain metadata. This is where I get > unpredictable ordering, as the handler services are run in parallel > * Solution > The idea is that we need to derive the handlers' order from the add operation steps, which are executed in the same order they're created in the parser. > Brian also suggests to use the OperationContext.attach(...) API to pass data between handler invocations within an overall operation execution. All ws subsystem ops during boot are executed as steps within an overall operation. The API works like the attachment stuff that's used a lot in DeploymentUnitProcessors. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues August 2019