javax.jms.JMSException: rollback

If you like a tip written by other Samebug users, mark is as helpful! Marks help our algorithm provide you better solutions and also help other users.
tip

Upgrade your docker-selenium

tip

Probably there is a bug in TestNG Eclipse plugin (6.8.6.20130607_0745), try an other version (e.g. 6.8.0.20121120_1820)

tip

before running my test in debug mode, i open the debug view, and remove some breakpoints (such as some remaining on NullPointersExceptions, and Sockets)

tip

Try removing all the breakpoints (even if breakpoints are disabled the problem still occurs, yes even if both disabled entirely and piecewise).

tip

There is a known issue between TestNG 6.4 and IDEA, the next EAP will fix this but in the meantime, use the previous version.

tip

Client closed the websocket connection (safe to ignore)

tip

*not english*


poroszd
tip

Nginx does not handle websocket requests. Configure nginx proxy for websockets.

tip

Set larger socket timeout (or 0 to set no timeout).

tip

Upgrade your nanohttpd

tip

It takes too long time for the JVM to find enough entropy for secure connection. Use this jvm option: '-Djava.security.egd=file:/dev/./urandom'.

tip

Upgrade yokozuna

tip

Here is a animation for the life cycle. http://tcp.cs.st-andrews.ac.uk/index.shtml?page=connection_lifecycle

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

  • Exception loading simple GWT view
    via Stack Overflow by MayoMan
    ,
  • Mule - User - tcp error
    via by Unknown author,
  • Disconnecting question
    via by Unknown author,
  • 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)
    via by pawan modi,
  • 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)
    via by pawan modi,
    • javax.jms.JMSException: rollback at com.evermind.server.jms.JMSUtils.make(JMSUtils.java:1034) at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1114) at com.evermind.server.jms.JMSRemoteServer.reconnect(JMSRemoteServer.java:1093) at com.evermind.server.jms.JMSRemoteServer.tryIt(JMSRemoteServer.java:1057) at com.evermind.server.jms.JMSRemoteServer.rollback(JMSRemoteServer.java:557) at com.evermind.server.jms.EvermindSession.localClose(EvermindSession.java:601) at com.evermind.server.jms.JMSObject.close(JMSObject.java:428) at com.evermind.server.ejb.MessageDrivenConsumer.destroyJMSResources(MessageDrivenConsumer.java:618) at com.evermind.server.ejb.MessageDrivenConsumer.run(MessageDrivenConsumer.java:175) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814) at java.lang.Thread.run(Thread.java:595) 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 java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) at java.io.DataOutputStream.flush(DataOutputStream.java:106) at com.evermind.server.jms.JMSRemoteServer.exec(JMSRemoteServer.java:1244) at com.evermind.server.jms.JMSRemoteServer.rollback(JMSRemoteServer.java:575) at com.evermind.server.jms.JMSRemoteServer.access$900(JMSRemoteServer.java:71) at com.evermind.server.jms.JMSRemoteServer$10.run(JMSRemoteServer.java:560) at com.evermind.server.jms.JMSRemoteServer.tryIt(JMSRemoteServer.java:1053) ... 7 more

    Users with the same issue

    nasimk
    nasimk1 times, last one,
    derprogger
    derprogger2 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    207 more bugmates