Hi:
The results of the votation:
http://marc.theaimsgroup.com/?t=10748904244r=1w=2
is:
A- [ +2] Cocoon will don't throw any exception when this happen.
B- [ -4] Log the event at INFO level.
C- [ +6] Log the event at DEBUG level.
Also Nicola comment:
snip
*IMPORTANT*
IIRC this
Antonio Gallardo wrote:
Hi:
This changes was suggested by Peter Hunsberger:
Overview:
=
When Cocoon attempt to close an already closed stream you get an IO
exception. If the user keeps closing the session the error doesn't tell
you why, just that it happened. If it's an error on the
Antonio Gallardo wrote:
Hi Peter:
Seems like we agree in the exception is not useful at all. Posible solutions:
1- Cocoon will don't throw any exception when this happen.
-0
2- Log the event at INFO level.
-1
3- Log the event at DEBUG level.
+1
Vadim
On Jan 22, 2004, at 10:58 AM, Antonio Gallardo wrote:
1- Cocoon will don't throw any exception when this happen.
-1
2- Log the event at INFO level.
-0
3- Log the event at DEBUG level.
+1 (and into its own special logger too)
-pete
Hi:
This changes was suggested by Peter Hunsberger:
Overview:
=
When Cocoon attempt to close an already closed stream you get an IO
exception. If the user keeps closing the session the error doesn't tell
you why, just that it happened. If it's an error on the client side and I
On Fri, Jan 23, 2004 at 02:40:55PM -0600, Antonio Gallardo wrote:
When Cocoon attempt to close an already closed stream you get an IO
exception. If the user keeps closing the session the error doesn't tell
you why, just that it happened. If it's an error on the client side and I
personally
Here is the vote:
1- [+1] Cocoon will don't throw any exception when this happen.
2- [-1] Log the event at INFO level.
3- [+0] Log the event at DEBUG level.
On 23.01.2004 21:40, Antonio Gallardo wrote:
Here is the vote:
1- [-0] Cocoon will don't throw any exception when this happen.
2- [+0] Log the event at INFO level.
3- [+1] Log the event at DEBUG level.
Joerg
Here is the vote:
1- [+0] Cocoon will don't throw any exception when this happen.
2- [-1] Log the event at INFO level.
3- [+1] Log the event at DEBUG level.
Vadim
Antonio Gallardo [EMAIL PROTECTED] writes:
Hunsberger, Peter dijo:
I'm not sure I even see a reason for logging it at INFO? If you've
got an error that occurs because the client closed the
socket you're
either going to know this, or if you turn up logging to the
INFO level
to
Hi Peter:
Seems like we agree in the exception is not useful at all. Posible solutions:
1- Cocoon will don't throw any exception when this happen.
2- Log the event at INFO level.
3- Log the event at DEBUG level.
Please tell me what of this options you prefer.
Best Regards,
Antonio Gallardo
Antonio Gallardo [EMAIL PROTECTED] asks:
Hi Peter:
Seems like we agree in the exception is not useful at all.
Posible solutions:
1- Cocoon will don't throw any exception when this happen.
+1
2- Log the event at INFO level.
-1
3- Log the event at DEBUG level.
+0
Antonio Gallardo [EMAIL PROTECTED] writes:
Hunsberger, Peter dijo:
It appears that if you attempt to close an already closed
stream you
get an IO exception. This means that if Cocoon gets stopped and
restarted it is possible, in at least some circumstances,
for Cocoon
to throw
Hunsberger, Peter dijo:
I'm not sure I even see a reason for logging it at INFO? If you've got
an error that occurs because the client closed the socket you're either
going to know this, or if you turn up logging to the INFO level to try
and find this out you're going to need some way to
Hunsberger, Peter dijo:
It appears that if you attempt to close an already closed stream you get
an IO exception. This means that if Cocoon gets stopped and restarted
it is possible, in at least some circumstances, for Cocoon to throw an
IOException in
15 matches
Mail list logo
