Meaningless Drivel is fun!*
The moose likes Tomcat and the fly likes Internal Error flushing the buffer in release() Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Products » Tomcat
Bookmark "Internal Error flushing the buffer in release()" Watch "Internal Error flushing the buffer in release()" New topic
Author

Internal Error flushing the buffer in release()

Alex Dovlecel
Greenhorn

Joined: Jul 29, 2004
Posts: 4
Hi all,

I hit a weird situation. I installed a Web Application in a Tomcat5, on a linux machine (suse 9.1). I start tomcat from command line and, when accessing the application, I get the error mentioned in the subject of the message.

But this DOES NOT HAPPEN ALL THE TIME!!! Sometimes it gives me plenty of there Warnings and sometimes it does not say anything about this...

I was not able to localize/find the problem that causes this output. Do you have any idea of what is wrong here?

I have no out.flush() in the code, so this is not the problem.

Thanks,
Alex
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 60800
    
  65

"Big Smiley",

We're pleased to have you here with us on the Ranch, but there are a few rules that need to be followed, and one is that proper names are required. Please take a look at the JavaRanch Naming Policy and adjust your display name to match it.

In particular, your display name must be a first and a last name separated by a space character, and must not be obviously fictitious.

Thanks!
bear
Forum Bartender


[Asking smart questions] [Bear's FrontMan] [About Bear] [Books by Bear]
Alex Dovlecel
Greenhorn

Joined: Jul 29, 2004
Posts: 4
Oki, heard that, done that.

Now, can I please get an answer??? 'cose I have a name!!!

I was hoping to see an answer when I saw the '1 message'... No answer yet.

Best wishes,
Alex
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 60800
    
  65

That basically means that Tomcat detected an IO exception while it was trying to flush the buffer (which it will do on its own when it gets full).

Was there no other information about the I/O exception itself anywhere in the logs?
Alex Dovlecel
Greenhorn

Joined: Jul 29, 2004
Posts: 4
Hi,

I did not find any error in the log. Not even an entry point.

The warning was written in the console.

There is one other line written in front of the warning:
<the date> PM org.apache.jasper.runtime.PageContextImpl release

I still have no idea what is going wrong... could not find information on google. ((

Thanks for the quick reply.
Alex
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 60800
    
  65

Hmmm, at this point it's hard to guess without more info.

Is this causing problems in your app, or are you just concerned with the error on the console?

I'm going to move this topic to the Tomcat forum where the Tomcat-savvy hang out to see if we can get other ideas.
Alex Dovlecel
Greenhorn

Joined: Jul 29, 2004
Posts: 4
For now I can't say if it causes any problems in my application. I have just installed it. But the browsing works oki...

But it makes me worry... and for shure the client will not like to see those warning messages.

And I still have no idea what could went wrong.

Cheers,
Alex
William Brogden
Author and all-around good cowpoke
Rancher

Joined: Mar 22, 2000
Posts: 12761
    
    5
If the message
PM org.apache.jasper.runtime.PageContextImpl release
is related to the source, here is the source code.

(Thats from Tomcat 4 source - what I have on hand but probably close)
From the documentation on JspWriter, that exception may be due to the response stream already being closed.
Bill
Antonio Signore
Greenhorn

Joined: Aug 01, 2004
Posts: 1
Alex:

I have the same problem and could not find a solution yet. Were you able to fix it?

best
antono
William Brogden
Author and all-around good cowpoke
Rancher

Joined: Mar 22, 2000
Posts: 12761
    
    5
Here is my guess - some component of the system is not calling release when it is supposed to, instead it is calling after the response has been sent. According to the javadocs, the release method "should not be used by page or tag library authors" so I suspect there is no simple way to fix it.
Bill
 
jQuery in Action, 2nd edition
 
subject: Internal Error flushing the buffer in release()
 
Similar Threads
casting with reflection ( or othre method)
Problem when code changes!!!
Error in deploying struts project in weblogic
com.orb failure in VAJAVA
JSP: IllegalStateException problem