December 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1849) Provide API to clean up MTOM attachments

by Magesh Kumar B (JIRA)

Provide API to clean up MTOM attachments ---------------------------------------- Key: JBWS-1849 URL: http://jira.jboss.com/jira/browse/JBWS-1849 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-jaxrpc, jbossws-jaxws Affects Versions: jbossws-1.2.0.SP1 Environment: Windows Reporter: Magesh Kumar B Priority: Optional When using MTOM with attachments, the temp files created using SwapableMemoryDataSource are not deleted in Windows environment. This is due to a problem in Windows and an outstanding bug in Java too contributes to it. http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4171239 It would be nice to have an API that can be explicity called to delete these temp files created as part of MTOM requests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

4
7
0 / 0

[JBoss JIRA] Created: (JBWS-1449) Generate extra XML schema file for SOAP message in document style web service

by qi liu (JIRA)

Generate extra XML schema file for SOAP message in document style web service ----------------------------------------------------------------------------- Key: JBWS-1449 URL: http://jira.jboss.com/jira/browse/JBWS-1449 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: qi liu The schema is currently inlined in the wsdl. An extra schema file is needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-1707) Resolved support patches should not appear as open issues

by Thomas Diesler (JIRA)

Resolved support patches should not appear as open issues --------------------------------------------------------- Key: JBWS-1707 URL: http://jira.jboss.com/jira/browse/JBWS-1707 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler JIRA project home contains a lot of noise from resolved support patches -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-1864) Extend MTOM test coverage to verify different data types

by Heiko Braun (JIRA)

Extend MTOM test coverage to verify different data types --------------------------------------------------------- Key: JBWS-1864 URL: http://jira.jboss.com/jira/browse/JBWS-1864 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: integration-metro, jbossws-jaxws Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-2.1.0 Currently the test coverage only uses simple types like Strings for instance. The MTOM test cases shoule be extended to verify that other possible attachment data types do work on both optimized and regular messages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-1918) Pass JavaEE5 CTS for jaxr, jaxrpc, jaxws, jws, saaj, webservice, webservices12

by Thomas Diesler (JIRA)

Pass JavaEE5 CTS for jaxr, jaxrpc, jaxws, jws, saaj, webservice, webservices12 ------------------------------------------------------------------------------ Key: JBWS-1918 URL: http://jira.jboss.com/jira/browse/JBWS-1918 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-jaxws Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-2.0.2 Run the JavaEE5 tests with jdk-1.5 against jboss-5.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-1917) Pass J2EE-1.4 CTS for jaxr, jaxrpc, saaj, webservice

by Thomas Diesler (JIRA)

Pass J2EE-1.4 CTS for jaxr, jaxrpc, saaj, webservice ---------------------------------------------------- Key: JBWS-1917 URL: http://jira.jboss.com/jira/browse/JBWS-1917 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-jaxws Reporter: Thomas Diesler Assigned To: Heiko Braun Fix For: jbossws-2.0.2 Run the J2EE-1.4 tests with jdk-1.5 against jboss-4.2.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1678) Redirect SunRI message logging to jboss log

by Thomas Diesler (JIRA)

Redirect SunRI message logging to jboss log ------------------------------------------- Key: JBWS-1678 URL: http://jira.jboss.com/jira/browse/JBWS-1678 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: integration-sunri Reporter: Thomas Diesler Fix For: jbossws-2.1.0 This cuurently uses the jdk logging -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-1888) Simple Ant build file for user WS-enabled projects

by Alessio Soldano (JIRA)

Simple Ant build file for user WS-enabled projects -------------------------------------------------- Key: JBWS-1888 URL: http://jira.jboss.com/jira/browse/JBWS-1888 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: productivity Reporter: Alessio Soldano -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBWS-1859) Concurrency issue in building the request handler chain when more than one handler is specified

by Bruce (JIRA)

Concurrency issue in building the request handler chain when more than one handler is specified ----------------------------------------------------------------------------------------------- Key: JBWS-1859 URL: http://jira.jboss.com/jira/browse/JBWS-1859 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxws Affects Versions: jbossws-2.0.1, jbossws-1.2.1 Reporter: Bruce >From what I can tell jbossws has concurrency issues in building the request handler chain when more than one handler is specified, and multiple requests are made to the server while it is starting. The problem is that too many copies of the handlers are inserted into the handler chain because more than one thread is building it. This only becomes apparent when one of the handlers is for WS Security. During request handling, the first WS Security handler removes the wsse header, so any subsequent handler throws an exception. The client receives the fault string "This service requires <wsse:Security>, which is missing". The server stack trace: javax.xml.ws.WebServiceException: org.jboss.ws.core.CommonSOAPFaultException: This service requires <wsse:Security>, which is missing. at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.processHandlerFailure(HandlerChainExecutor.java:276) at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:155) at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:87) at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:126) at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:170) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:408) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122) at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595) Steps to duplicate - Create web service that exposes a ping() method, and requires both WS Security and WS Addressing. A customized standard-jaxws-endpoint-config.xml file is required. - Create a client application that calls ping() every second in a loop - Start the server - Once the server initializes, start 2 instances of the client - Restart the server - Most of the time the error will start to occur for every request. You may have to restart the server a few time to get the error condition. Sometimes the server is able to initialize successfully. If it is successful, it will stay that way. Even having many clients pounding on the server for hours will not cause the error. - Once the error condition begins, the server is unable to properly process any more ping requests, even if both clients are stopped, and only one is restarted. standard-jaxws-endpoint-config.xml addition: <endpoint-config> <config-name>WSAddressing + WSSecurity Endpoint</config-name> <post-handler-chains> <javaee:handler-chain> <javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindings> <javaee:handler> <javaee:handler-name>WSAddressing Handler</javaee:handler-name> <javaee:handler-class>org.jboss.ws.extensions.addressing.jaxws.WSAddressingServerHandler</javaee:handler-class> </javaee:handler> <javaee:handler> <javaee:handler-name>WSSecurity Handler</javaee:handler-name> <javaee:handler-class>org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer</javaee:handler-class> </javaee:handler> </javaee:handler-chain> </post-handler-chains> </endpoint-config> I have sample server and client code that you can use, but could not see how to attach it to the bug report. I was able to prevent the error from occurring with a slight modification to callRequestHandlerChain() in org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS. I changed: if (isInitialized() == false) { resolver.initHandlerChain(sepMetaData, HandlerType.PRE, true); resolver.initHandlerChain(sepMetaData, HandlerType.ENDPOINT, true); resolver.initHandlerChain(sepMetaData, HandlerType.POST, true); setInitialized(true); } to if (isInitialized() == false) { synchronized(this) { if (isInitialized() == false) { resolver.initHandlerChain(sepMetaData, HandlerType.PRE, true); resolver.initHandlerChain(sepMetaData, HandlerType.ENDPOINT, true); resolver.initHandlerChain(sepMetaData, HandlerType.POST, true); setInitialized(true); } } } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-1938) Assign message name instead of IN and OUT for Inbound/Outbound Addressing Property

by Magesh Kumar B (JIRA)

Assign message name instead of IN and OUT for Inbound/Outbound Addressing Property ---------------------------------------------------------------------------------- Key: JBWS-1938 URL: http://jira.jboss.com/jira/browse/JBWS-1938 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxws, ws-addressing Affects Versions: jbossws-2.0.2, jbossws-1.2.1 Reporter: Magesh Kumar B Assigned To: Magesh Kumar B -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues December 2007