Re: I have the TRaX, can you help?
JBoss 4.2 Benson Margulies-4 wrote: I think this has to do with the XML jars in your path. What container are you in? -- View this message in context: http://www.nabble.com/I-have-the-TRaX%2C-can-you-help--tp16455965p16597149.html Sent from the cxf-user mailing list archive at Nabble.com.
Re: I have the TRaX, can you help?
We have found a way to reproduce it. We are using JBoss 4.2 and CXF 2.0.3.
When JBoss is starting, if a client {java or .net} attempts to connect to
the webservice before the JBoss server is completely up and servicing the
webservice, the exception will be thrown after JBoss displays it's started
successfully message. Now it's looking more like a JBoss problem than a CXF
problem. Any thoughts?
Thanks,
Jason
dkulp wrote:
On Friday 04 April 2008, Daniel Kulp wrote:
On Thursday 03 April 2008, jm1468 wrote:
...
WARNING: org.apache.cxf.transport.http.WSDLQueryHandler Exception
caught writing response: Failed to configure TRaX
...
org.apache.cxf.interceptor.Fault: No such operation
Ick.. there are several things wrong that I need to dig into quite a
bit more:
1) The WSDLQueryHandler is throwing the above exception. However, we
only log the basic getMessage() thing and not the full stack trace
that would indicate any internal cause exceptions and stuff that
would actually help to diagnose it.
2) If an exception is thrown, wrather than returning an error to the
client like error generating wsdl, we try to dispatch the request
into the interceptor chains like its a service invokation. Since it
doesn't look like a normal request, it doesn't find an operaion.
I'm going to fix both of those. It most likely won't fix your problem
as it's having problems creating a transformer, but it MAY at least
provide a better indication of WHY it's not working.
Actually, I'm going to go one furthur and change from using a transformer
to write the wsdl out to using our Stax based writers. Since Stax HAS
to work for pretty much anything in CXF to work, that should be a bit
more reliable. :-) It may be a bit quicker as well.
--
J. Daniel Kulp
Principal Engineer, IONA
[EMAIL PROTECTED]
http://www.dankulp.com/blog
--
View this message in context:
http://www.nabble.com/I-have-the-TRaX%2C-can-you-help--tp16455965p16597540.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: I have the TRaX, can you help?
Honestly, my first thought is to hope that Thomas from JBoss, who has been
posting a lot of traffic on the dev list, might be able to help you.
On Wed, Apr 9, 2008 at 5:42 PM, jm1468 [EMAIL PROTECTED] wrote:
We have found a way to reproduce it. We are using JBoss 4.2 and CXF
2.0.3.
When JBoss is starting, if a client {java or .net} attempts to connect to
the webservice before the JBoss server is completely up and servicing the
webservice, the exception will be thrown after JBoss displays it's started
successfully message. Now it's looking more like a JBoss problem than a
CXF
problem. Any thoughts?
Thanks,
Jason
dkulp wrote:
On Friday 04 April 2008, Daniel Kulp wrote:
On Thursday 03 April 2008, jm1468 wrote:
...
WARNING: org.apache.cxf.transport.http.WSDLQueryHandler Exception
caught writing response: Failed to configure TRaX
...
org.apache.cxf.interceptor.Fault: No such operation
Ick.. there are several things wrong that I need to dig into quite a
bit more:
1) The WSDLQueryHandler is throwing the above exception. However, we
only log the basic getMessage() thing and not the full stack trace
that would indicate any internal cause exceptions and stuff that
would actually help to diagnose it.
2) If an exception is thrown, wrather than returning an error to the
client like error generating wsdl, we try to dispatch the request
into the interceptor chains like its a service invokation. Since it
doesn't look like a normal request, it doesn't find an operaion.
I'm going to fix both of those. It most likely won't fix your problem
as it's having problems creating a transformer, but it MAY at least
provide a better indication of WHY it's not working.
Actually, I'm going to go one furthur and change from using a
transformer
to write the wsdl out to using our Stax based writers. Since Stax HAS
to work for pretty much anything in CXF to work, that should be a bit
more reliable. :-) It may be a bit quicker as well.
--
J. Daniel Kulp
Principal Engineer, IONA
[EMAIL PROTECTED]
http://www.dankulp.com/blog
--
View this message in context:
http://www.nabble.com/I-have-the-TRaX%2C-can-you-help--tp16455965p16597540.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: I have the TRaX, can you help?
I think this has to do with the XML jars in your path. What container are you in?
Re: I have the TRaX, can you help?
On Thursday 03 April 2008, jm1468 wrote: ... WARNING: org.apache.cxf.transport.http.WSDLQueryHandler Exception caught writing response: Failed to configure TRaX ... org.apache.cxf.interceptor.Fault: No such operation Ick.. there are several things wrong that I need to dig into quite a bit more: 1) The WSDLQueryHandler is throwing the above exception. However, we only log the basic getMessage() thing and not the full stack trace that would indicate any internal cause exceptions and stuff that would actually help to diagnose it. 2) If an exception is thrown, wrather than returning an error to the client like error generating wsdl, we try to dispatch the request into the interceptor chains like its a service invokation. Since it doesn't look like a normal request, it doesn't find an operaion. I'm going to fix both of those. It most likely won't fix your problem as it's having problems creating a transformer, but it MAY at least provide a better indication of WHY it's not working. -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
Re: I have the TRaX, can you help?
On Friday 04 April 2008, Daniel Kulp wrote: On Thursday 03 April 2008, jm1468 wrote: ... WARNING: org.apache.cxf.transport.http.WSDLQueryHandler Exception caught writing response: Failed to configure TRaX ... org.apache.cxf.interceptor.Fault: No such operation Ick.. there are several things wrong that I need to dig into quite a bit more: 1) The WSDLQueryHandler is throwing the above exception. However, we only log the basic getMessage() thing and not the full stack trace that would indicate any internal cause exceptions and stuff that would actually help to diagnose it. 2) If an exception is thrown, wrather than returning an error to the client like error generating wsdl, we try to dispatch the request into the interceptor chains like its a service invokation. Since it doesn't look like a normal request, it doesn't find an operaion. I'm going to fix both of those. It most likely won't fix your problem as it's having problems creating a transformer, but it MAY at least provide a better indication of WHY it's not working. Actually, I'm going to go one furthur and change from using a transformer to write the wsdl out to using our Stax based writers. Since Stax HAS to work for pretty much anything in CXF to work, that should be a bit more reliable. :-) It may be a bit quicker as well. -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
I have the TRaX, can you help?
) at org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:170) at org.apache.cxf.transport.servlet.AbstractCXFServlet.doGet(AbstractCXFServlet.java:152) at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:595) Caused by: ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:358) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434) at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:309) at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:273) at org.apache.catalina.connector.CoyoteOutputStream.close(CoyoteOutputStream.java:104) at org.apache.cxf.transport.http.AbstractHTTPDestination$WrappedOutputStream.close(AbstractHTTPDestination.java:509) at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66) at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) ... 29 more Caused by: java.net.SocketException: Software caused connection abort: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:737) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:349) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:761) at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFilter.java:124) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:570) at org.apache.coyote.Response.doWrite(Response.java:560) at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:353) ... 36 more Can someone please help? I've tried cxf-2.03 - cxf-2.0.5. Thanks, J -- View this message in context: http://www.nabble.com/I-have-the-TRaX%2C-can-you-help--tp16455965p16455965.html Sent from the cxf-user mailing list archive at Nabble.com.
