• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

flushing problems using out.flush() on WAS

 
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Please take a look at this simple piece of code:

<BODY>
<%
for(int i=0;i<10;i++)
{
%>
<%=i%><br>
<%
out.flush();
Thread.sleep(500);
}
%>
</BODY>

Executing it on a TOMCAT 5.0 AppServer makes it work exactly the way I want it to work - you can watch the page beeing build up step by step, one line by another.
Unfortunately the same code doesn't behave the same way on our Websphere 5.01 AppServer. Instead of building up the page line by line, you have to wait first and then the output is done all at a time.

Does anybody have a clue to this strange WAS behavior?
Tried some combinations using response.flushBuffer() as well as the "buffer" and "autoFlush" page-directives, but without success...
 
Sebastian Krzyzanowski
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
UPDATE:

Calling the JSP directly via the appropriate IP address plus AppServer SOAP-connector port (eg.: http://192.168.1.210:9089/testit.jsp) WORKS!!!

This leads me to the conclusion that it might be a
a) WebServer problem (IBMIHS 2.0.47) or
b) WebServer-to-WAS-plugin problem

I found a forum entry describing the same problem where the apache WebServer used content-encoding: gzip as default encoding which resulted in this strange behavior, but our WebServer doesn't use any mod_gzip modules...
 
Sheriff
Posts: 67746
173
Mac Mac OS X IntelliJ IDE jQuery TypeScript Java iOS
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Moved to the Websphere forum.
[ June 22, 2005: Message edited by: Bear Bibeault ]
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic