February 2016 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3987) Loosen BusTestCase::testReuse() checks

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3987?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3987: ---------------------------------- Description: The org.jboss.test.ws.jaxws.cxf.bus.BusTestCase::testReuse() test is too strict and basically assumes that GC is not performed during its run. As a consequence of CXF-6632 having been fixed, we need to loosen the test checks to only assert what we are interested in and is going to be always reproducible. > Loosen BusTestCase::testReuse() checks > -------------------------------------- > > Key: JBWS-3987 > URL: https://issues.jboss.org/browse/JBWS-3987 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1.4.Final > > > The org.jboss.test.ws.jaxws.cxf.bus.BusTestCase::testReuse() test is too strict and basically assumes that GC is not performed during its run. > As a consequence of CXF-6632 having been fixed, we need to loosen the test checks to only assert what we are interested in and is going to be always reproducible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3987) Loosen BusTestCase::testReuse() checks

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3987: ------------------------------------- Summary: Loosen BusTestCase::testReuse() checks Key: JBWS-3987 URL: https://issues.jboss.org/browse/JBWS-3987 Project: JBoss Web Services Issue Type: Task Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.1.4.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3986) Improve isolation between integration code and user code

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3986: ------------------------------------- Summary: Improve isolation between integration code and user code Key: JBWS-3986 URL: https://issues.jboss.org/browse/JBWS-3986 Project: JBoss Web Services Issue Type: Enhancement Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.1.4.Final It is currently possible for user code to "see" some JBossWS integration classes & dependencies during the execution of static blocks of user handlers declared through webservices.xml descriptors or management model. That happens because such code is executed at deployment time when the JBossWS integration classloader is set as thread context classloader. We should prevent this from happening. This is not a problem, of course, at runtime, when the deployment is completely isolated from the integration classloader. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3985) CXFHandlerResolverImpl not threadsafe

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3985?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3985: --------------------------------------- The fix will eventually reach WildFly next time we upgrade the JBossWS stack in it. > CXFHandlerResolverImpl not threadsafe > ------------------------------------- > > Key: JBWS-3985 > URL: https://issues.jboss.org/browse/JBWS-3985 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.0.0.Final > Reporter: Bjørn Hilstad > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1.4.Final > > > When the concurrency of handler-chain parsing increases , the following error shows up in the logs: > Caused by: org.xml.sax.SAXException: FWK005 parse may not be called while parsing. > at org.apache.xerces.parsers.DOMParser.parse(DOMParser.java:260) > at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:298) > at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121) > at org.jboss.wsf.stack.cxf.client.serviceref.CXFHandlerResolverImpl.createHandlerChain(CXFHandlerResolverImpl.java:161) > ... 132 more > One case where I have seen this is when an EJB/MDB uses @WebServiceRef and @HandlerChain to get a reference to a webservice. > When multiple instances of the EJB/MDB are created at the same time to handle a lot of messages this happens. > It is the @HandlerChain that triggers the xml parsing and gives the error. > The Xerces DocumentBuilder is not threadsafe and thus requires code to synchronize it correctly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3985) CXFHandlerResolverImpl not threadsafe

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3985?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3985: ---------------------------------- Fix Version/s: jbossws-cxf-5.1.4.Final > CXFHandlerResolverImpl not threadsafe > ------------------------------------- > > Key: JBWS-3985 > URL: https://issues.jboss.org/browse/JBWS-3985 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.0.0.Final > Reporter: Bjørn Hilstad > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1.4.Final > > > When the concurrency of handler-chain parsing increases , the following error shows up in the logs: > Caused by: org.xml.sax.SAXException: FWK005 parse may not be called while parsing. > at org.apache.xerces.parsers.DOMParser.parse(DOMParser.java:260) > at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:298) > at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121) > at org.jboss.wsf.stack.cxf.client.serviceref.CXFHandlerResolverImpl.createHandlerChain(CXFHandlerResolverImpl.java:161) > ... 132 more > One case where I have seen this is when an EJB/MDB uses @WebServiceRef and @HandlerChain to get a reference to a webservice. > When multiple instances of the EJB/MDB are created at the same time to handle a lot of messages this happens. > It is the @HandlerChain that triggers the xml parsing and gives the error. > The Xerces DocumentBuilder is not threadsafe and thus requires code to synchronize it correctly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3985) CXFHandlerResolverImpl not threadsafe

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3985?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3985: ---------------------------------- Project: JBoss Web Services (was: WildFly) Key: JBWS-3985 (was: WFLY-6287) Workflow: classic default workflow (was: GIT Pull Request workflow ) Component/s: jbossws-cxf (was: Web Services) Affects Version/s: jbossws-cxf-5.0.0.Final (was: 9.0.1.Final) > CXFHandlerResolverImpl not threadsafe > ------------------------------------- > > Key: JBWS-3985 > URL: https://issues.jboss.org/browse/JBWS-3985 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.0.0.Final > Reporter: Bjørn Hilstad > Assignee: Alessio Soldano > > When the concurrency of handler-chain parsing increases , the following error shows up in the logs: > Caused by: org.xml.sax.SAXException: FWK005 parse may not be called while parsing. > at org.apache.xerces.parsers.DOMParser.parse(DOMParser.java:260) > at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:298) > at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121) > at org.jboss.wsf.stack.cxf.client.serviceref.CXFHandlerResolverImpl.createHandlerChain(CXFHandlerResolverImpl.java:161) > ... 132 more > One case where I have seen this is when an EJB/MDB uses @WebServiceRef and @HandlerChain to get a reference to a webservice. > When multiple instances of the EJB/MDB are created at the same time to handle a lot of messages this happens. > It is the @HandlerChain that triggers the xml parsing and gives the error. > The Xerces DocumentBuilder is not threadsafe and thus requires code to synchronize it correctly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3984) Add support for cxf-rt-features-clustering in jbossws-cxf

by Viral Gohel (JIRA)

Viral Gohel created JBWS-3984: --------------------------------- Summary: Add support for cxf-rt-features-clustering in jbossws-cxf Key: JBWS-3984 URL: https://issues.jboss.org/browse/JBWS-3984 Project: JBoss Web Services Issue Type: Feature Request Components: jbossws-cxf Reporter: Viral Gohel We need to have the cxf failover feature, http://cxf.apache.org/docs/failoverfeature.html, be made available in jbossws-cxf. We don't ship with this feature yet and the feature actually allows us to how to implement auto fail over and fail back of CXF SOAP calls from a primary to a secondary URL. Here's is an example hosted for this, https://github.com/jaceko/cxf-circuit-switcher. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3983) Basic integration of JAX-RS functionalities from Apache CXF

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3983: ------------------------------------- Summary: Basic integration of JAX-RS functionalities from Apache CXF Key: JBWS-3983 URL: https://issues.jboss.org/browse/JBWS-3983 Project: JBoss Web Services Issue Type: Feature Request Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-6.0.0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3974) Incorreclty bypass the SecurityManager and call AccessControl.checkPermission() directly

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3974?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3974: ---------------------------------- Fix Version/s: (was: jbossws-cxf-5.2.0.Final) > Incorreclty bypass the SecurityManager and call AccessControl.checkPermission() directly > ---------------------------------------------------------------------------------------- > > Key: JBWS-3974 > URL: https://issues.jboss.org/browse/JBWS-3974 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-integration > Environment: EAP 7.0.0.Beta1, jbossws-spi 3.1.1 (Couldn't find in affected version list) > Reporter: Jason Shepherd > Assignee: Jim Ma > Priority: Minor > Fix For: jbossws-cxf-5.1.4.Final > > > Calls to AccessControl.checkPermission() should be done by the Security Manager so that policies can be centrally managed. See this guide as a reference: > bq. Note that the method AccessController.checkPermission is normally invoked indirectly through invocations of specific SecurityManager methods that begin with the word check such as checkConnect or through the method SecurityManager.checkPermission. Normally, these checks only occur if a SecurityManager has been installed; code checked by the AccessController.checkPermission method first checks if the method System.getSecurityManager returns null. > [https://docs.oracle.com/javase/8/docs/technotes/guides/security/doprivile...] > Also refer to fixed issue WFCORE-1266, as it is similar. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3974) Incorreclty bypass the SecurityManager and call AccessControl.checkPermission() directly

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3974?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3974: ---------------------------------- Fix Version/s: jbossws-cxf-5.1.4.Final > Incorreclty bypass the SecurityManager and call AccessControl.checkPermission() directly > ---------------------------------------------------------------------------------------- > > Key: JBWS-3974 > URL: https://issues.jboss.org/browse/JBWS-3974 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-integration > Environment: EAP 7.0.0.Beta1, jbossws-spi 3.1.1 (Couldn't find in affected version list) > Reporter: Jason Shepherd > Assignee: Jim Ma > Priority: Minor > Fix For: jbossws-cxf-5.1.4.Final > > > Calls to AccessControl.checkPermission() should be done by the Security Manager so that policies can be centrally managed. See this guide as a reference: > bq. Note that the method AccessController.checkPermission is normally invoked indirectly through invocations of specific SecurityManager methods that begin with the word check such as checkConnect or through the method SecurityManager.checkPermission. Normally, these checks only occur if a SecurityManager has been installed; code checked by the AccessController.checkPermission method first checks if the method System.getSecurityManager returns null. > [https://docs.oracle.com/javase/8/docs/technotes/guides/security/doprivile...] > Also refer to fixed issue WFCORE-1266, as it is similar. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 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 February 2016