Hi Oleg,
> But it is Windows problem (or JDK for Windows), as Daniel pointed out
> earlier. The message appears for each jar file and I have absolutely
> no way to improve the situation. And this is not a fatal error, since
> the old temporary files are removed during jBoss startup.
> Thus, we have an annoying useless message, which teaches jBoss users
> to ignore error messages.
I was thinking about this message and my opinion is: it has to be there,
because it indicates that there is something growing, the user has no
control on.
If the log files overgrow - the user/admin knows: ooops, my
configuration wasnt that smart...
If the databases overgrow - the user/admin knows: well maybe the other
dbms would have been the better one...
But if the tmp/deploy directory overgrows the user/admin has no idea
what he did wrong. And file names in that directory are not very self
explaining too. So my feeling tells me: inform the user/admin that there
is something he should keep an eye on.
Anyway, 3 opinions are more then 1 and yesterday was election day so if
I get no response to this mail, I will change the "couldnt remove"
messages to debug level messages.
\Daniel
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
