aspose file tools*
The moose likes Websphere and the fly likes WriteBeyondContentLen Kyle...Please help Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "WriteBeyondContentLen Kyle...Please help" Watch "WriteBeyondContentLen Kyle...Please help" New topic
Author

WriteBeyondContentLen Kyle...Please help

Bhiku Mhatre
Ranch Hand

Joined: Apr 08, 2002
Posts: 127
Hello,
we are developing a content management where our client can upload and download contents.
The client wants to keep track the no. of times a file is accessed.
We wrote a servlet that intercepts the request.
increase the access count by one and then


this.getServletConfig().getServletContext().getRequestDispatcher("Uploads/"+((Integer)session.getAttribute("company_no")).toString()+"/"+fileName).forward(request,response);


Here we have a weird problem. When the file is accessed on port 9080 it works fine.
It also works when the file is accessed on the server browser using localhost in url(Without port 9080).
But otherwise I get an error

com.ibm.servlet.engine.srt.WriteBeyondContentLengthException.


Any one has already faced this problem ??

Thanks in advance for your help.
Regards,
Bhiku.


The difference between winner and loser is making things happen and letting things happen.
David Hibbs
Ranch Hand

Joined: Dec 19, 2002
Posts: 374
I haven't specifically seen this problem, but the port 9080 rings a bell. If you don't regen the web server plugin, then 100% restart the http server, you get some strange behavior. So try this:
1) regen the plugin
2) Stop the IBM HTTP Server service
3) Check for any running apache processes -- stop them if there are any**
4) Start the IBM HTTP Server service
5) Restart your app server
**this was my problem, even though I stopped the service, the HTTP admin service was still running so I had to stop that, too.
Hopefully this will help...


"Write beautiful code; then profile that beautiful code and make little bits of it uglier but faster." --The JavaPerformanceTuning.com team, Newsletter 039.
Danl Thompson
Ranch Hand

Joined: Apr 04, 2001
Posts: 93
I have seen this problem. I was generating PDF documents using FOP in WAS and any time the document was over 100kb I got this error. The problem is that WAS is a poor file server. It is well documented, for example, not to use the file servlet in production. I had to write the PDF to a temporary file and serve it up from the HTTP server. I hear there may be improvements in some of the fix packs.
dt
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: WriteBeyondContentLen Kyle...Please help