• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Broken Pipe error using batik (SVG conversion)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Broken Pipe error using batik (SVG conversion)


  • Subject: Re: Broken Pipe error using batik (SVG conversion)
  • From: Dev WO <email@hidden>
  • Date: Wed, 14 Jun 2006 21:08:06 +0200

Hello Chuck,


On Jun 14, 2006, at 10:05 AM, Dev WO wrote:

Hi guys,

I've created a method to rasterize an SVG image (using Batik). When I try to use this method in my application it appears it takes too long to execute (at least that's what I'm guessing), here's what I have in the log:

[2006-06-14 16:26:52 CEST] <WorkerThread0> <WOWorkerThread id=0 socket=Socket[addr=/10.0.1.8,port=49708,localport=49645]>
Exception while sending response: java.net.SocketException: Broken pipe


I also get:
"No instance available" in the web browser quite some time after it loads (probably due to the broken pipe)


One does not cause the other, but they are both symptoms of the app taking too long to respond.


The created image (in this case a JPG) is created but it behaves strangely:
I can't open it before moving it somewhere else on the hard drive... If I put it back to its initial place it is then OK to open it. Might be a process not fully executed and moving the file forcing it to end...


No idea about that.


I had to increase the memory (-Xmx400m -Xms200m) to get rid of the "out of memory error" I initially had.

Does anyone know how I could fix the broken pipe issue?


You can't fix the broken pipe directly, it is a warning that your app is responding too slowly for the woadaptor settings. One solution is to use something like the WOLongResponsePage so that the request does not drag on. You could also do it in the background and somehow notify the user.
Could you give me more input about this option?
The other "solution" is to increase the Connect and Receive timeouts for the woadaptor (see the App configuration page in JavaMonitor) until it waits long enough for this process to finish.
I'll try this one to see if it corrects the problem, but it appears you don't really like this option;) I'd rather like to notify the user one way or another...

Thanks

Xavier

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Broken Pipe error using batik (SVG conversion)
      • From: Robert Walker <email@hidden>
References: 
 >Broken Pipe error using batik (SVG conversion) (From: Dev WO <email@hidden>)
 >Re: Broken Pipe error using batik (SVG conversion) (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: Broken Pipe error using batik (SVG conversion)
  • Next by Date: Re: Broken Pipe error using batik (SVG conversion)
  • Previous by thread: Re: Broken Pipe error using batik (SVG conversion)
  • Next by thread: Re: Broken Pipe error using batik (SVG conversion)
  • Index(es):
    • Date
    • Thread