Re: Problem with Mod_JK 1.2.15 and 1.2.18

2006-09-01 Thread Marcio Camurati
Hi,

Fred I forget to say at the post that I use it (JkOptions +FlushPackets) at my 
httpd.conf and it "fix" the flush call, but don't get a exception only when I 
shutdown the container. I found this post of another person about the same 
problem (http://threebit.net/mail-archive/tomcat-users/msg00254.html) but 
without answer.

Thanx

Marcio Camurati

On Fri, 1 Sep 2006 10:45:45 -0700 (PDT), fredk2 <[EMAIL PROTECTED]> escreveu:

> De: fredk2 <[EMAIL PROTECTED]>
> Data: Fri, 1 Sep 2006 10:45:45 -0700 (PDT)
> Para: users@tomcat.apache.org
> Assunto: Re: Problem with Mod_JK 1.2.15 and 1.2.18
> 
> 
> i think you need this in your httpd.conf mod_jk related configuration
> section:
> 
> JkOptions +FlushPackets
> 
> Rgds, Fred
> 
> 
> Marcio Camurati wrote:
> > 
> > Hi everyone, 
> > 
> > We have a application that run at the Tomcat container. This application
> > was made at the Tomcat 4.1 using the Mod_jk 1.2.12 with this configuration
> > the application run perfectly without any problem, at this days we want to
> > make an upgrade at the servers to use the new Mod_Jk 1.2.15 or 1.2.18, but
> > when we do this the application broken. The problem is that with this new
> > Mod_jk the Exceptions was never call for example at this code:
> > 
> > [code]
> > try
> > {
> >  while (true)
> >  {
> >   out.println("Nonononononnoonnonono");
> > 
> >   try
> >   {
> >Thread.Sleep(1000);
> >   } catch(Exception ex) {}
> >  }
> > } catch(Exception ex) {
> >  try {
> >   BufferedWriter writer = new BufferedWriter(new
> > FileWriter("/srv/www/default/html/log/exception.txt"));
> >   writer.write("Eror !");
> >   writer.close();
> >   writer = null;
> >  } catch (IOException ioe) {
> >   ioe.printStackTrace();
> >  }
> > }
> > [/code]
> > 
> > When the brownser is closed the server never create the file
> > (exception.txt) it will only create this file when the Tomcat is shuted
> > down, with the older version 1.2.12 or oldest the server always call this
> > exception beforer 1 or 2 seconds and create the file.
> > 
> > We open at the Bugzila a report of this problem
> > (http://issues.apache.org/bugzilla/show_bug.cgi?id=39290) but didn't have
> > any help to fix it.
> > 
> > Thanx.
> > 
> > Marcio Camurati
> > 
> > -
> > To start a new topic, e-mail: users@tomcat.apache.org
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> > 
> 
> -- 
> View this message in context: 
> http://www.nabble.com/Problem-with-Mod_JK-1.2.15-and-1.2.18-tf2202971.html#a6103299
> Sent from the Tomcat - User forum at Nabble.com.
> 
> 
> -
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Problem with Mod_JK 1.2.15 and 1.2.18

2006-09-01 Thread fredk2

i think you need this in your httpd.conf mod_jk related configuration
section:

JkOptions +FlushPackets

Rgds, Fred


Marcio Camurati wrote:
> 
> Hi everyone, 
> 
> We have a application that run at the Tomcat container. This application
> was made at the Tomcat 4.1 using the Mod_jk 1.2.12 with this configuration
> the application run perfectly without any problem, at this days we want to
> make an upgrade at the servers to use the new Mod_Jk 1.2.15 or 1.2.18, but
> when we do this the application broken. The problem is that with this new
> Mod_jk the Exceptions was never call for example at this code:
> 
> [code]
> try
> {
>  while (true)
>  {
>   out.println("Nonononononnoonnonono");
> 
>   try
>   {
>Thread.Sleep(1000);
>   } catch(Exception ex) {}
>  }
> } catch(Exception ex) {
>  try {
>   BufferedWriter writer = new BufferedWriter(new
> FileWriter("/srv/www/default/html/log/exception.txt"));
>   writer.write("Eror !");
>   writer.close();
>   writer = null;
>  } catch (IOException ioe) {
>   ioe.printStackTrace();
>  }
> }
> [/code]
> 
> When the brownser is closed the server never create the file
> (exception.txt) it will only create this file when the Tomcat is shuted
> down, with the older version 1.2.12 or oldest the server always call this
> exception beforer 1 or 2 seconds and create the file.
> 
> We open at the Bugzila a report of this problem
> (http://issues.apache.org/bugzilla/show_bug.cgi?id=39290) but didn't have
> any help to fix it.
> 
> Thanx.
> 
> Marcio Camurati
> 
> -
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Problem-with-Mod_JK-1.2.15-and-1.2.18-tf2202971.html#a6103299
Sent from the Tomcat - User forum at Nabble.com.


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Problem with Mod_JK 1.2.15 and 1.2.18

2006-09-01 Thread Marcio Camurati
Hi everyone, 

We have a application that run at the Tomcat container. This application was 
made at the Tomcat 4.1 using the Mod_jk 1.2.12 with this configuration the 
application run perfectly without any problem, at this days we want to make an 
upgrade at the servers to use the new Mod_Jk 1.2.15 or 1.2.18, but when we do 
this the application broken. The problem is that with this new Mod_jk the 
Exceptions was never call for example at this code:

[code]
try
{
 while (true)
 {
  out.println("Nonononononnoonnonono");

  try
  {
   Thread.Sleep(1000);
  } catch(Exception ex) {}
 }
} catch(Exception ex) {
 try {
  BufferedWriter writer = new BufferedWriter(new 
FileWriter("/srv/www/default/html/log/exception.txt"));
  writer.write("Eror !");
  writer.close();
  writer = null;
 } catch (IOException ioe) {
  ioe.printStackTrace();
 }
}
[/code]

When the brownser is closed the server never create the file (exception.txt) it 
will only create this file when the Tomcat is shuted down, with the older 
version 1.2.12 or oldest the server always call this exception beforer 1 or 2 
seconds and create the file.

We open at the Bugzila a report of this problem 
(http://issues.apache.org/bugzilla/show_bug.cgi?id=39290) but didn't have any 
help to fix it.

Thanx.

Marcio Camurati

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]