December 2013 - jbossws-issues - Jboss List Archives

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3746: ------------------------------------- Summary: Hudson cleanup Key: JBWS-3746 URL: https://issues.jboss.org/browse/JBWS-3746 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: productization Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.3 We need to remove some jobs, cleanup stale stuff, remove references to Sun in the job names, etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3743) Block HTTP GET requests with no query string

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3743: ------------------------------------- Summary: Block HTTP GET requests with no query string Key: JBWS-3743 URL: https://issues.jboss.org/browse/JBWS-3743 Project: JBoss Web Services Issue Type: Enhancement Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.3 Similarly to what we used to do with JBossWS-Native stack, we'd better block HTTP GET requests with no query string and return a nice response message instead of letting underlying Apache CXF fail (usually with a NPE because the soap message ends up not being created). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3742) EndpointMetricsImpl is not thread-safe

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3742: ------------------------------------- Summary: EndpointMetricsImpl is not thread-safe Key: JBWS-3742 URL: https://issues.jboss.org/browse/JBWS-3742 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.3 The EndpointMetricsImpl is not thread-safe; it has non-final / non-volatile long fields that do not ensure atomic reads nor proper visibility among different threads. The average processing time computation is also not atomic. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3733) Allow enabling/disabling endpoint metrics

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3733?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3733: --------------------------------------- The simplest approach would be to save the value of the new attribute in the ServerConfig; the EndpointMetricsDeploymentAspect will check that and decide whether to set a new EndpointMetrics instance in each Endpoint. In the future we could evaluate making this tuning more fine grain, perhaps by having an operation in the resource for each endpoint to enabled/disable metrics. > Allow enabling/disabling endpoint metrics > ----------------------------------------- > > Key: JBWS-3733 > URL: https://issues.jboss.org/browse/JBWS-3733 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > We need to offer a mechanism for enabling/disabling endpoint metrics. > We should probably have an element/attribute in the container DMR for enabling/disabling the metrics. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3691) Prevent race condition in default webservice port retrieval mechanism

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3691?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3691: ---------------------------------- Summary: Prevent race condition in default webservice port retrieval mechanism (was: Refactor default webservice port retrieval mechanism) > Prevent race condition in default webservice port retrieval mechanism > --------------------------------------------------------------------- > > Key: JBWS-3691 > URL: https://issues.jboss.org/browse/JBWS-3691 > Project: JBoss Web Services > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > The AbstractServerConfig has a getConnectorPort method for finding the default port to be used for endpoint addresses; that looks for the proper configured http connector. > The retrieval goes through a MSC service lookup (ServiceName.JBOSS.append("web", "common", "server")) in org.jboss.as.webservices.config.WebServerInfoFactoryImpl / WebServerInfoImpl. This creates a possible race condition at boot, given the web common server service might possibly start after a ws deployment process hit the EndpointAddressDeploymentAspect (actually to be verified). To be honest, the AbstractServerConfig has sensible defaults that would mitigate the problem if happening, but still this should be fixed. > A proposal would be to modify the WebServerInfoFactoryImpl / WebServerInfoImpl to wait for the availability of WS service having dependency on the web common server service. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3689) Ensure consistent state of server config is always used

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3689?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3689: --------------------------------------- The "basic" attributes in AbstractServerConfig are all related to / used for WS endpoints deployment: https://issues.jboss.org/browse/WFLY-2451 covers proper state management. The rest of the attributes in the ServerConfig is for management of client/endpoint pre-defined configs, which is addressed in https://svn.jboss.org/repos/jbossws/spi/branches/JBWS-3739 / https://svn.jboss.org/repos/jbossws/common/branches/JBWS-3739 / https://svn.jboss.org/repos/jbossws/stack/cxf/branches/JBWS-3739 branches (as part of the JBWS-3708 changes). > Ensure consistent state of server config is always used > ------------------------------------------------------- > > Key: JBWS-3689 > URL: https://issues.jboss.org/browse/JBWS-3689 > Project: JBoss Web Services > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > The ServerConfig can be modified, through management API, JMX, etc. We should ensure that each time we use data from the server config, a consistent state is actually used. This is tightly related to the work / efforts under WFLY-1759, as we might for instance keep a reference to a copy of the config with pending updates to its values still to be applied. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3708) Enforce client/endpoint config immutability at runtime

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3708?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3708: --------------------------------------- Solved in https://svn.jboss.org/repos/jbossws/spi/branches/JBWS-3739 / https://svn.jboss.org/repos/jbossws/common/branches/JBWS-3739 / https://svn.jboss.org/repos/jbossws/stack/cxf/branches/JBWS-3739 branches, to be merged later. > Enforce client/endpoint config immutability at runtime > ------------------------------------------------------ > > Key: JBWS-3708 > URL: https://issues.jboss.org/browse/JBWS-3708 > Project: JBoss Web Services > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > The client and endpoint predefined configs should be considered immutable after the server has booted. Unless we decide to explicitly support on-the-fly user modification of configs (e.g. for adding handlers, changing props, etc.) we need to return immutable versions / deep copy of them from the ServerConfig (AbstractServerConfig). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3739) Enforce jbossws-spi metadata immutability

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3739?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3739: --------------------------------------- Solved in https://svn.jboss.org/repos/jbossws/spi/branches/JBWS-3739 branch, to be merged later. > Enforce jbossws-spi metadata immutability > ----------------------------------------- > > Key: JBWS-3739 > URL: https://issues.jboss.org/browse/JBWS-3739 > Project: JBoss Web Services > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > All jbossws-spi metadata classes should be immutable, to automatically ensure thread safety and allow for achieving JBWS-3708. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3707) AbstractCommonConfig is not thread safe

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3707?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3707: --------------------------------------- Solved in https://svn.jboss.org/repos/jbossws/spi/branches/JBWS-3739 branch, to be merged later. > AbstractCommonConfig is not thread safe > --------------------------------------- > > Key: JBWS-3707 > URL: https://issues.jboss.org/browse/JBWS-3707 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > The org.jboss.wsf.spi.metadata.config.AbstractCommonConfig is not thread safe and is possibly accessed / modified concurrently (at least during boot on WFLY as a consequence of WFLY-1759). The members should likely be final (and the collection ones should be initialized to concurrent collections). > Same applies to org.jboss.wsf.spi.metadata.j2ee.serviceref.UnifiedHandlerChainMetaData and org.jboss.wsf.spi.metadata.j2ee.serviceref.UnifiedHandlerMetaData. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3741) WebService doesn't support "//"

by Thomas Szadel (JIRA)

Thomas Szadel created JBWS-3741: ----------------------------------- Summary: WebService doesn't support "//" Key: JBWS-3741 URL: https://issues.jboss.org/browse/JBWS-3741 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-4.1.3 Reporter: Thomas Szadel Priority: Minor The WebService part of Jboss eap 6 doesn't support double slash ('//') in URI (although JBoss 5 supports it and the Web connector also supports it). That's to say, those 3 urls should represent the same one : * http://localhost:8080/ws/myWs?wsdl * http://localhost:8080/ws//myWs?wsdl * http://localhost:8080//ws/myWs?wsdl BUT only the first one is accepted by JBoss. The others raise that stack trace: javax.servlet.ServletException: JBWS024029: Cannot obtain destination for /ws//myWs org.jboss.wsf.stack.cxf.RequestHandlerImpl.findDestination(RequestHandlerImpl.java:170) org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:87) org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:156) org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87) org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:225) org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:150) javax.servlet.http.HttpServlet.service(HttpServlet.java:734) org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135) org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) javax.servlet.http.HttpServlet.service(HttpServlet.java:847) AND if I call the following URL, it works : http://localhost:8080/./ws/myWs?wsdl IMHO, the method org.jboss.wsf.stack.cxf.RequestHandlerImpl.findDestination should use a "canonical path" before testing the equality. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

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 December 2013