Re: [Wrapper-user] System.in can not be used when the JVM is being controlled by the Java Service

[Everett T. <eve...@ne...>]

At 06:46 PM Tuesday 3/30/2004, you wrote:
>Everett,
>    The feature to cause the System.in to block does not exist in 
> currently released
>versions of the Wrapper.  This will not be available until 3.1.0.  Are you 
>using a
>released version or building from CVS?
>
>    You could probably figure out what is going on a little better by 
> adding some
>print statements after the call to read from System.in.   But from looking 
>at your
>code and the log output, I am betting that you are using 3.0.5 or earlier and
>the call to System.in.read is throwing an IOException.   Your code is simply
>ignoring any exceptions thrown and continuing on.  Try printing out the 
>exception
>you are catching.

you're right, i'm using 3.0.5.  i should've mentioned that in my question.


>    Strong advice.  Never, and I mean Never! simply eat an exception.
>If you
>are 100% sure that code will never actually throw an exception then printing
>it out should never happen and will not hurt.   If you do encounter an 
>unexpected
>exception then you will save yourself hours of hair pulling trying to 
>figure out the
>problem.  :-)  Speaking from experience.

i agree completely.  it wasn't my code originally, i was just trying to 
turn it into a service, but i guess i'll have to make some changes...


>    Let me know if I was wrong in any of my assumptions, I had to guess 
> because
>you didn't post the version you are using.
>
>Cheers,
>Leif

thanks for the help,
everett