Title: ALTRAN OUEST
Guillaume Smet a écrit :
On 2/1/07, Gérard BUNEL <[EMAIL PROTECTED]> wrote:
  No, In fact I've many exceptions (each corresponding to a client request) with teir corresponding stack trace.
 Then restoring done without any warning/error as shown in logs here-after:
 java.net.SocketException
 MESSAGE: java.net.ConnectException: Connection refused

Outch. Sequoia catches RuntimeException and SQLException but not
others. In the case of RuntimeException and SQLException, it's
correctly handled (inserts in the recovery log are postponed) but not
in the case of ConnectException.
I think that we should fix this code to take into account any
exception. I'll open a JIRA issue to track this problem.

  I may contribute with this if I've no other alternative as I do need to know, and to alert responsible persons of a problem in the cluster

It could be really nice.

  I can't find this class in the 2.10.4 distribution. maybe in the 3.x ? I need to rely on a stable version. Is this code compatible with 2.10.4 version ?

I don't understand why it's not in the distribution. It's in the CVS
for a very long time and in the 2.10 branch from the beginning.
So you have more risks to have it outdated than too recent :).

 Is it possible to register a NotificationListener automatically at sequoia controller startup ? or do I need to create a new process to implement this ?

Well, not with this code. And IMHO, it's not a good idea to embed it
in the controller if you really want to use it to monitor the
controller.
I don't think it's a so bad idea. What I should expect from such module should be for example to send SNMP trap on backend activation/de-activation and on controller added/removed. This is already done for backend activation/de-activation in the JMX part. But I can't see anything about controllers.
The fact that it should be embedded in a controller is not a problem for me as controller process is also monitored externally.
In a first time I thought about using log4j and SNMPTrapAppender to do this, but I can't easily filter events from log4j as backend failure is ERROR but backend activation is INFO. And so on for controllers.

--
Guillaume Smet
Open Wide

_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia



--

Gérard BUNEL
Chef de Projet
____________________________________________________________________


Technopôle Brest Iroise
Site du Vernis – CS 23866
29238 Brest Cedex 3
Tél : + 33 2 98 05 43 21
Fax : + 33 2 98 05 20 34
www.altran.com

_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia

Reply via email to