November 2014 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3857) Wrong content type (text/xml) in outgoing multipart SOAPMessage (expected multipart/related; ...)

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3857?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3857: ---------------------------------- Fix Version/s: jbossws-cxf-5.0 > Wrong content type (text/xml) in outgoing multipart SOAPMessage (expected multipart/related; ...) > ------------------------------------------------------------------------------------------------- > > Key: JBWS-3857 > URL: https://issues.jboss.org/browse/JBWS-3857 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Fix For: jbossws-cxf-5.0 > > > Clone of EAP6 issue https://bugzilla.redhat.com/show_bug.cgi?id=1167348 - WF is also susceptible. > Description of problem: > There is wrong content type (text/xml) in multipart SOAPMessage when sending it using javax.xml.soap API. So target system is unable to parse it. > How reproducible: > always > Additional info: > It's also wrong in EAP 6.2. > EAP 6.1 is OK. > There is a patch attached in BZ-1167348 for JBossWS CXF 4.3.3. The same fix should be also applied to JBossWS CXF 5.0.0 which is used by Wildfly. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3843) Username Token Digest Authentication failure with EJB3 endpoints

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3843?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3843: ----------------------------------------------- Jan Blizňák <jbliznak(a)redhat.com> changed the Status of [bug 1157482|https://bugzilla.redhat.com/show_bug.cgi?id=1157482] from ON_QA to VERIFIED > Username Token Digest Authentication failure with EJB3 endpoints > ---------------------------------------------------------------- > > Key: JBWS-3843 > URL: https://issues.jboss.org/browse/JBWS-3843 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf, jbossws-integration, ws-security > Affects Versions: jbossws-cxf-4.3.1 > Environment: JBoss EAP 6.3.1 > Reporter: Mustafa Musaji > Assignee: Jim Ma > Priority: Critical > Fix For: jbossws-cxf-4.3.2, jbossws-cxf-5.0.0.Beta2 > > Attachments: ClientSample.java, javaee-ws-with-security_1413372207000.zip > > > EJB3 Web Service using username token for digest authentication fails when you load test it with parallel invocations. See attached reproducer. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3843) Username Token Digest Authentication failure with EJB3 endpoints

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3843?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3843: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1157482|https://bugzilla.redhat.com/show_bug.cgi?id=1157482] from MODIFIED to ON_QA > Username Token Digest Authentication failure with EJB3 endpoints > ---------------------------------------------------------------- > > Key: JBWS-3843 > URL: https://issues.jboss.org/browse/JBWS-3843 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf, jbossws-integration, ws-security > Affects Versions: jbossws-cxf-4.3.1 > Environment: JBoss EAP 6.3.1 > Reporter: Mustafa Musaji > Assignee: Jim Ma > Priority: Critical > Fix For: jbossws-cxf-4.3.2, jbossws-cxf-5.0.0.Beta2 > > Attachments: ClientSample.java, javaee-ws-with-security_1413372207000.zip > > > EJB3 Web Service using username token for digest authentication fails when you load test it with parallel invocations. See attached reproducer. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3843) Username Token Digest Authentication failure with EJB3 endpoints

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3843?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3843: ----------------------------------------------- Peter Skopek <pskopek(a)redhat.com> changed the Status of [bug 1157482|https://bugzilla.redhat.com/show_bug.cgi?id=1157482] from POST to MODIFIED > Username Token Digest Authentication failure with EJB3 endpoints > ---------------------------------------------------------------- > > Key: JBWS-3843 > URL: https://issues.jboss.org/browse/JBWS-3843 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf, jbossws-integration, ws-security > Affects Versions: jbossws-cxf-4.3.1 > Environment: JBoss EAP 6.3.1 > Reporter: Mustafa Musaji > Assignee: Jim Ma > Priority: Critical > Fix For: jbossws-cxf-4.3.2, jbossws-cxf-5.0.0.Beta2 > > Attachments: ClientSample.java, javaee-ws-with-security_1413372207000.zip > > > EJB3 Web Service using username token for digest authentication fails when you load test it with parallel invocations. See attached reproducer. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 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 Blizňák <jbliznak(a)redhat.com> changed the Status of [bug 1155490|https://bugzilla.redhat.com/show_bug.cgi?id=1155490] from ON_QA to VERIFIED > 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 > 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 (v6.3.8#6338)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3856) jbossws.undefined.host in WS-MEX WSDL metadata

by Frank Cornelis (JIRA)

[ https://issues.jboss.org/browse/JBWS-3856?page=com.atlassian.jira.plugin.... ] Frank Cornelis edited comment on JBWS-3856 at 11/20/14 12:04 PM: ----------------------------------------------------------------- The weird thing is that the xs:import schemaLocations are correct. But the soap:address location is not. For WS-MEX there is also more to it than just the WSDL location replacements. For MetadataSections with Dialect http://www.w3.org/2001/XMLSchema and some Location element, the value of the Location element should also be adapted. was (Author: fcorneli): The weird thing is that the xs:import schemaLocations are correct. But the soap:address location is not. For WS-MEX there is also more to it than just the WSDL location replacements. For MetadataSections with Dialect http://www.w3.org/2001/XMLSchema and some Location element, the value of the Location element should also be adopted. > jbossws.undefined.host in WS-MEX WSDL metadata > ---------------------------------------------- > > Key: JBWS-3856 > URL: https://issues.jboss.org/browse/JBWS-3856 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.3 > Reporter: Frank Cornelis > > When defining <wsdl-host>jbossws.undefined.host</wsdl-host> the JBoss CXF indeed replaces the wsoap12:address location within the WSDL with the actual address. But the same substitution is not applied on the WSDL within WS-MEX metadata. Seems like the location is being replaced with an address containing jbossws.undefined.host, instead of the actual host. This causes STS implementations that also expose MEX to fail. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3856) jbossws.undefined.host in WS-MEX WSDL metadata

by Frank Cornelis (JIRA)

[ https://issues.jboss.org/browse/JBWS-3856?page=com.atlassian.jira.plugin.... ] Frank Cornelis commented on JBWS-3856: -------------------------------------- The weird thing is that the xs:import schemaLocations are correct. But the soap:address location is not. For WS-MEX there is also more to it than just the WSDL location replacements. For MetadataSections with Dialect http://www.w3.org/2001/XMLSchema and some Location element, the value of the Location element should also be adopted. > jbossws.undefined.host in WS-MEX WSDL metadata > ---------------------------------------------- > > Key: JBWS-3856 > URL: https://issues.jboss.org/browse/JBWS-3856 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.3 > Reporter: Frank Cornelis > > When defining <wsdl-host>jbossws.undefined.host</wsdl-host> the JBoss CXF indeed replaces the wsoap12:address location within the WSDL with the actual address. But the same substitution is not applied on the WSDL within WS-MEX metadata. Seems like the location is being replaced with an address containing jbossws.undefined.host, instead of the actual host. This causes STS implementations that also expose MEX to fail. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 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 Blizňák <jbliznak(a)redhat.com> changed the Status of [bug 1153960|https://bugzilla.redhat.com/show_bug.cgi?id=1153960] from ON_QA to VERIFIED > 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 > 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 (v6.3.8#6338)

10 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 Blizňák <jbliznak(a)redhat.com> changed the Status of [bug 1153954|https://bugzilla.redhat.com/show_bug.cgi?id=1153954] from ON_QA to VERIFIED > 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 > 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 (v6.3.8#6338)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3856) jbossws.undefined.host in WS-MEX WSDL metadata

by Frank Cornelis (JIRA)

Frank Cornelis created JBWS-3856: ------------------------------------ Summary: jbossws.undefined.host in WS-MEX WSDL metadata Key: JBWS-3856 URL: https://issues.jboss.org/browse/JBWS-3856 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf Affects Versions: jbossws-cxf-4.3 Reporter: Frank Cornelis When defining <wsdl-host>jbossws.undefined.host</wsdl-host> the JBoss CXF indeed replaces the wsoap12:address location within the WSDL with the actual address. But the same substitution is not applied on the WSDL within WS-MEX metadata. Seems like the location is being replaced with an address containing jbossws.undefined.host, instead of the actual host. This causes STS implementations that also expose MEX to fail. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues November 2014