It was clear that the problem occurs because of the network (you are
facing a SocketException, aren't you?), but without the configuration
details we won't be able to help.
In you previous email you said that you have 6 Axis2 services
deployed on Tomcat 6. If so, please post your axis2.xml file.
Michele
p.s. The aim of punctuation marks is to make a sentence clear. Please
use them -- it's very difficult to understand what you are trying to
say.
On 12 May 2008, at 19:40, Sushil Dodake wrote:
My client application is built using Spring + java services Wrapper
which is deployed in JAVA6 env.(http://wrapper.tanukisoftware.org/
doc/english/integrate-simple-win.html)
the client application is a batch controller application.
the java wrapper calls the controller class which in turn calls a
Axis 1.3 service A deployed on some other machin.
after getting the response XML from service A to the batch
controller it gives call to service B deployed with service A in
tomcat 6 in java 6 env.
in the Tomcat 6 container there are 4 more services along with A
and B.
the B service is a central service which inturns gives call to
remaining 4 services and then returns to batch controller.
but once B completes process it just returns null to Batch controller.
then the batch contoller updates DB tables to update the status of
the process.
If all the services and the batch controller are deployed on same
machine then it does not cause any problem.
but over the network it gives follwing error.
On Mon, May 12, 2008 at 5:55 AM, Michele Mazzucco
<[EMAIL PROTECTED]> wrote:
Can you post more information about your configuration (both server
and client)?
Thanks,
Michele
On 9 May 2008, at 19:45, Sushil Dodake wrote:
Hi all,
i have 6 Axis2 1.3 services deployed in a Tomcat 6 continer and on
JAVA 6 env.
out of the 6 services 1 is a central controller which calls other 5
services for diffrent data.
there is one application which is deployed on some other machin
which calls central controller service and one more service in the
container.
the data which flows across the services and the independent
application is big XMLs
it seems that if the application is running continously for 2-4
hrs... after 2 hrs roughly.. it thows an exception.
the scenario is not reproducible every time (lets say for same data
so definately its not a data issue.)
I am really confused.
any thoughts on this?
org.apache.axis2.AxisFault
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
at org.apache.axis2.transport.http.ApplicationXMLFormatter.writeTo
(ApplicationXMLFormatter.java:116)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.sendUsingOu
tputStream(CommonsHTTPTransportSender.java:294)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke
(CommonsHTTPTransportSender.java:211)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396)
at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusi
nessLogic(AbstractInOutSyncMessageReceiver.java:45)
at org.apache.axis2.receivers.AbstractMessageReceiver.receive
(AbstractMessageReceiver.java:96)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)
at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine
(RESTUtil.java:125)
at org.apache.axis2.transport.http.util.RESTUtil.processXMLRequest
(RESTUtil.java:78)
at org.apache.axis2.transport.http.AxisServlet
$RestRequestProcessor.processXMLRequest(AxisServlet.java:788)
at org.apache.axis2.transport.http.AxisServlet.doPost
(AxisServlet.java:193)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
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.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:175)
at org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke
(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke
(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service
(CoyoteAdapter.java:286)
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:447)
at java.lang.Thread.run(Thread.java:619)
Caused by: com.ctc.wstx.exc.WstxIOException: null
at com.ctc.wstx.sw.BaseStreamWriter.writeCharacters
(BaseStreamWriter.java:511)
at org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeCharacters
(MTOMXMLStreamWriter.java:196)
at org.apache.axiom.om.impl.llom.OMTextImpl.writeOutput
(OMTextImpl.java:212)
at org.apache.axiom.om.impl.llom.OMTextImpl.internalSerializeLocal
(OMTextImpl.java:371)
at
org.apache.axiom.om.impl.llom.OMTextImpl.internalSerializeAndConsume
(OMTextImpl.java:365)
at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize
(OMElementImpl.java:785)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsum
e(OMElementImpl.java:814)
at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize
(OMElementImpl.java:785)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsum
e(OMElementImpl.java:814)
at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume
(OMNodeImpl.java:421)
at org.apache.axis2.transport.http.ApplicationXMLFormatter.writeTo
(ApplicationXMLFormatter.java:114)
... 24 more
Caused by: ClientAbortException: java.net.SocketException:
Connection reset by peer: 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.tomcat.util.buf.ByteChunk.append(ByteChunk.java:349)
at org.apache.catalina.connector.OutputBuffer.writeBytes
(OutputBuffer.java:381)
at org.apache.catalina.connector.OutputBuffer.write
(OutputBuffer.java:370)
at org.apache.catalina.connector.CoyoteOutputStream.write
(CoyoteOutputStream.java:89)
at com.ctc.wstx.io.UTF8Writer.write(UTF8Writer.java:139)
at com.ctc.wstx.sw.BufferingXmlWriter.flushBuffer
(BufferingXmlWriter.java:1103)
at com.ctc.wstx.sw.BufferingXmlWriter.writeRaw
(BufferingXmlWriter.java:229)
at com.ctc.wstx.sw.BufferingXmlWriter.writeCharacters
(BufferingXmlWriter.java:543)
at com.ctc.wstx.sw.BaseStreamWriter.writeCharacters
(BaseStreamWriter.java:509)
... 34 more
Caused by: java.net.SocketException: Connection reset by peer:
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:126)
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)
... 44 more
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
