java.net.SocketException: Software caused connection abort: socket write error

MuleSoft JIRA | pawan modi | 9 years ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    Mule2.0.3 is working fine with openmq4.1 jms broker. publisher & consumer are exchanging messages using jms transport. But some time following socket exception is occuring & causing message loss. Due to the following socket exception receiver is not able to receive messages sent by publisher. It is observed that 5-6% of messages losses are due to the following socket exception. ERROR 2008-09-15 15:55:18,108 [connector.tcp.0.receiver.5] org.mule.DefaultExceptionStrategy: Caught exception in Exception Strate gy: Software caused connection abort: socket write error java.net.SocketException: Software caused connection abort: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(Unknown Source) at java.net.SocketOutputStream.write(Unknown Source) at java.io.BufferedOutputStream.flushBuffer(Unknown Source) at java.io.BufferedOutputStream.flush(Unknown Source) at java.io.DataOutputStream.flush(Unknown Source) at org.mule.transport.tcp.protocols.LengthProtocol.writeByteArray(LengthProtocol.java:96) at org.mule.transport.tcp.protocols.AbstractByteProtocol.write(AbstractByteProtocol.java:81) at org.mule.transport.tcp.protocols.AbstractByteProtocol.write(AbstractByteProtocol.java:77) at org.mule.transport.tcp.protocols.SafeProtocol.write(SafeProtocol.java:56) at org.mule.transport.tcp.TcpMessageReceiver$TcpWorker.handleResults(TcpMessageReceiver.java:412) at org.mule.transport.AbstractReceiverWorker.doRun(AbstractReceiverWorker.java:132) at org.mule.transport.AbstractReceiverResourceWorker.doRun(AbstractReceiverResourceWorker.java:51) at org.mule.transport.AbstractReceiverWorker.run(AbstractReceiverWorker.java:62) at org.mule.work.WorkerContext.run(WorkerContext.java:310) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575) at java.lang.Thread.run(Unknown Source)

    MuleSoft JIRA | 9 years ago | pawan modi
    java.net.SocketException: Software caused connection abort: socket write error
  2. 0

    Mule2.0.3 is working fine with openmq4.1 jms broker. publisher & consumer are exchanging messages using jms transport. But some time following socket exception is occuring & causing message loss. Due to the following socket exception receiver is not able to receive messages sent by publisher. It is observed that 5-6% of messages losses are due to the following socket exception. ERROR 2008-09-15 15:55:18,108 [connector.tcp.0.receiver.5] org.mule.DefaultExceptionStrategy: Caught exception in Exception Strate gy: Software caused connection abort: socket write error java.net.SocketException: Software caused connection abort: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(Unknown Source) at java.net.SocketOutputStream.write(Unknown Source) at java.io.BufferedOutputStream.flushBuffer(Unknown Source) at java.io.BufferedOutputStream.flush(Unknown Source) at java.io.DataOutputStream.flush(Unknown Source) at org.mule.transport.tcp.protocols.LengthProtocol.writeByteArray(LengthProtocol.java:96) at org.mule.transport.tcp.protocols.AbstractByteProtocol.write(AbstractByteProtocol.java:81) at org.mule.transport.tcp.protocols.AbstractByteProtocol.write(AbstractByteProtocol.java:77) at org.mule.transport.tcp.protocols.SafeProtocol.write(SafeProtocol.java:56) at org.mule.transport.tcp.TcpMessageReceiver$TcpWorker.handleResults(TcpMessageReceiver.java:412) at org.mule.transport.AbstractReceiverWorker.doRun(AbstractReceiverWorker.java:132) at org.mule.transport.AbstractReceiverResourceWorker.doRun(AbstractReceiverResourceWorker.java:51) at org.mule.transport.AbstractReceiverWorker.run(AbstractReceiverWorker.java:62) at org.mule.work.WorkerContext.run(WorkerContext.java:310) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575) at java.lang.Thread.run(Unknown Source)

    MuleSoft JIRA | 9 years ago | pawan modi
    java.net.SocketException: Software caused connection abort: socket write error
  3. 0

    Mule - User - SocketException Software caused connection abort socket write error

    nabble.com | 12 months ago
    java.net.SocketException: Software caused connection abort: socket write error
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Mule - User - tcp error

    nabble.com | 2 years ago
    java.net.SocketException: Software caused connection abort: socket write error
  6. 0

    Exception loading simple GWT view

    Stack Overflow | 4 years ago | MayoMan
    com.google.gwt.dev.shell.BrowserChannel$RemoteDeathError: Remote connection lost

  1. nasimk 1 times, last 1 week ago
  2. derprogger 1 times, last 3 weeks ago
5 unregistered visitors
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. java.net.SocketException

    Software caused connection abort: socket write error

    at java.net.SocketOutputStream.socketWrite0()
  2. Java RT
    DataOutputStream.flush
    1. java.net.SocketOutputStream.socketWrite0(Native Method)
    2. java.net.SocketOutputStream.socketWrite(Unknown Source)
    3. java.net.SocketOutputStream.write(Unknown Source)
    4. java.io.BufferedOutputStream.flushBuffer(Unknown Source)
    5. java.io.BufferedOutputStream.flush(Unknown Source)
    6. java.io.DataOutputStream.flush(Unknown Source)
    6 frames
  3. TCP Transport
    TcpMessageReceiver$TcpWorker.handleResults
    1. org.mule.transport.tcp.protocols.LengthProtocol.writeByteArray(LengthProtocol.java:96)
    2. org.mule.transport.tcp.protocols.AbstractByteProtocol.write(AbstractByteProtocol.java:81)
    3. org.mule.transport.tcp.protocols.AbstractByteProtocol.write(AbstractByteProtocol.java:77)
    4. org.mule.transport.tcp.protocols.SafeProtocol.write(SafeProtocol.java:56)
    5. org.mule.transport.tcp.TcpMessageReceiver$TcpWorker.handleResults(TcpMessageReceiver.java:412)
    5 frames
  4. Mule Core
    WorkerContext.run
    1. org.mule.transport.AbstractReceiverWorker.doRun(AbstractReceiverWorker.java:132)
    2. org.mule.transport.AbstractReceiverResourceWorker.doRun(AbstractReceiverResourceWorker.java:51)
    3. org.mule.transport.AbstractReceiverWorker.run(AbstractReceiverWorker.java:62)
    4. org.mule.work.WorkerContext.run(WorkerContext.java:310)
    4 frames
  5. Backport of JSR 166
    ThreadPoolExecutor$Worker.run
    1. edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
    2. edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
    2 frames
  6. Java RT
    Thread.run
    1. java.lang.Thread.run(Unknown Source)
    1 frame