Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

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

 
Hemanth H Bhat
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi everyone

I am using weblogic 8.1 and trying to post an XML of 40 MB size on the JMS queue
while posting this message i am getting the following exception and thus unable to post the message on the JMS queue can you please guide me in resolving this problem

Many Thanks
Hemanth
-------------------------------------------------------------------------
weblogic.jms.common.JMSException: Error sending message
at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:403)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:186)
at com.clsPostingMsg.main(clsPostingMsg.java:64)
Caused by: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested exception:
[java.net.SocketException: Software caused connection abort: socket write error]
at weblogic.jms.dispatcher.DispatcherImpl_814_WLStub.dispatchSyncTranFuture(Unknown Source)
at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncTran(DispatcherWrapperState.java:408)
at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:383)
... 2 more
 
Marcos Maia
Ranch Hand
Posts: 977
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

you have to define message and/or bytes thresholds and quotas, as well as a maximum allowable message size on your JMS servers, destinations, and templates.
I'd also consider compressing the message.
Take a look at:
http://edocs.bea.com/wls/docs81/messaging.html

you'll find more information on this from this link.

regards.
 
Hemanth H Bhat
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Marcos For your Timely reply

I made some configuration changes on the weblogic server as below

Click on the Name of the server (On which you have deployed your application and queues etc...)in the left Pane

Goto --> Protocols-->General--> Advanced Options
Increase the following Parameters

Complete Message Timeout:
Idle Connection Timeout:
Maximum Message Size:

By making these changes i am able to post the XML on the queue without any problems

Thanks
Hemanth
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic