Rails 2.3.2 and output window on Windows

[zwadar]

Hi,
I'm sorry if it's duplicate or well known issue, but I found nothing about it.

On my Vista x64 NB 6.5.1 and 6.7 Rails 2.3.2 don't write anything to NB output window exept

=> Booting Mongrel
=> Rails 2.3.2 application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server

and than nothing about performed actions, caught exceptions etc. It's newly generated rails project. Loading this project with rails 2.2.2 fixes it. Tested with MRI and latest Jruby.

Is there anything what I can do to fix it, or its just impossible to use 2.3.2 in NB now?

Thanks

Roman

EDIT
Well, now I found that it works, but it takes couple of minutes to synchronize rails log outpput with NB outputwindow. Times are higher with jruby (1.3.1) : 5 to 20 minutes (both 2.2.2 and 2.3.2), and lower with MRI (2.2.2 works well, but in 2.3.2 it takes 1-2 minutes to synchrnoze)

[Erno Mononen]

Hi Roman,

zwadar wrote:

[zwadar]

Hey,
Lately I edited my first postu on the forums, but edit didn't arrived by
mail.


EDIT
Well, now I found that it works, but it takes couple of minutes to
synchronize rails log outpput with NB outputwindow. Times are higher with
jruby (1.3.1) : 5 to 20 minutes (both 2.2.2 and 2.3.2), and lower with MRI
(2.2.2 works well, but in 2.3.2 it takes 1-2 minutes to synchrnoze)

But I'll follow your guidlines when Iwill be at home..

Thanks

Roman

-----Original Message-----
From: address-removed [mailto:address-removed]
Sent: Wednesday, July 08, 2009 7:21 AM
To: address-removed
Subject: Re: Rails 2.3.2 and output window on Windows


Hi Roman,

zwadar wrote:

[zwadar]

so, here are results form testing on different Pc with win XP, NB 6.7.1 and Jruby 1.3.1, rails 2.3.2.
I ran rails, send couple of requests, but nothing appeared in output windows. It looks like output is flushed to this window only when break point is reached.
Another thing which log vcan show is that when I exit rails aplication, error message box appears with message

[Erno Mononen]

zwadar wrote:

[zwadar]

It's the same with or without debugger. With debugger it's even better, since output is flushed when breakpoint is reached
This behaviour is same on my home (Vista X64) and work (XP) computer, so I hope it is nothing machine specific.. maybe user specific

Or maybe its because I'm using older JDK? I'm sticked to jdk1.6.0_06 because newer versoins came with strange font changes and code is hard to read in NB. (small difference between normal and bold text, maybe because of some strange antialiasing or something)

Roman

[zwadar]

After updating to jdk1.6.0_14 I've got fixed some small issues I had before, but both delayed output and hanging java.exe after debug persists.
I've checked just run command better, and it seems, that while just running the app no output is printed at all, just initial mongrel message. So I have
no output while running the app, and delayed output while debugging the app.

[Erno Mononen]

zwadar wrote: