You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sandesha-dev@ws.apache.org by "Paul Fremantle (JIRA)" <ji...@apache.org> on 2007/04/04 10:51:32 UTC

[jira] Created: (SANDESHA2-81) Logging the state of sequences

Logging the state of sequences
------------------------------

                 Key: SANDESHA2-81
                 URL: https://issues.apache.org/jira/browse/SANDESHA2-81
             Project: Sandesha2
          Issue Type: Improvement
            Reporter: Paul Fremantle


We need to deliberately log the behaviour of sequences. 

For example, we should log the creation of sequences, timeouts, inactivity, closing, termination, including

1.0: was there a LastMessage, were all messages acked, etc

1.1: was there a LastMessageNumber in the CS or TS? did it match the last message received? were all messages acked? was there a final ack?

I propose that we define a single target (classname) in log4j that captures these logs so that users can add a line to log4j.properties to log this to a file or other log4j target. Maybe org.apache.sandesha2.SequenceLogs



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org

RE: [jira] Created: (SANDESHA2-81) Logging the state of sequences

Posted by Sanjesh Pathak <sa...@soapknox.com>.
Paul,

Although not directly related to this thread, but one of the reasons for my
enhancement request here
(http://mail-archives.apache.org/mod_mbox/ws-sandesha-dev/200703.mbox/%3c200
70320150208.1A95F10FB010@herse.apache.org%3e) was that one could check and
log whether it is a last message from an application (service or module)
that is running outside Sanesha2.

Sanjesh

-----Original Message-----
From: Paul Fremantle (JIRA) [mailto:jira@apache.org] 
Sent: Wednesday, April 04, 2007 3:52 AM
To: sandesha-dev@ws.apache.org
Subject: [jira] Created: (SANDESHA2-81) Logging the state of sequences

Logging the state of sequences
------------------------------

                 Key: SANDESHA2-81
                 URL: https://issues.apache.org/jira/browse/SANDESHA2-81
             Project: Sandesha2
          Issue Type: Improvement
            Reporter: Paul Fremantle


We need to deliberately log the behaviour of sequences. 

For example, we should log the creation of sequences, timeouts, inactivity,
closing, termination, including

1.0: was there a LastMessage, were all messages acked, etc

1.1: was there a LastMessageNumber in the CS or TS? did it match the last
message received? were all messages acked? was there a final ack?

I propose that we define a single target (classname) in log4j that captures
these logs so that users can add a line to log4j.properties to log this to a
file or other log4j target. Maybe org.apache.sandesha2.SequenceLogs



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org

RE: [jira] Created: (SANDESHA2-81) Logging the state of sequences

Posted by Sanjesh Pathak <sa...@soapknox.com>.
Paul,

Although not directly related to this thread, but one of the reasons for my
enhancement request here
(http://mail-archives.apache.org/mod_mbox/ws-sandesha-dev/200703.mbox/%3c200
70320150208.1A95F10FB010@herse.apache.org%3e) was that one could check and
log whether it is a last message from an application (service or module)
that is running outside Sanesha2.

Sanjesh

-----Original Message-----
From: Paul Fremantle (JIRA) [mailto:jira@apache.org] 
Sent: Wednesday, April 04, 2007 3:52 AM
To: sandesha-dev@ws.apache.org
Subject: [jira] Created: (SANDESHA2-81) Logging the state of sequences

Logging the state of sequences
------------------------------

                 Key: SANDESHA2-81
                 URL: https://issues.apache.org/jira/browse/SANDESHA2-81
             Project: Sandesha2
          Issue Type: Improvement
            Reporter: Paul Fremantle


We need to deliberately log the behaviour of sequences. 

For example, we should log the creation of sequences, timeouts, inactivity,
closing, termination, including

1.0: was there a LastMessage, were all messages acked, etc

1.1: was there a LastMessageNumber in the CS or TS? did it match the last
message received? were all messages acked? was there a final ack?

I propose that we define a single target (classname) in log4j that captures
these logs so that users can add a line to log4j.properties to log this to a
file or other log4j target. Maybe org.apache.sandesha2.SequenceLogs



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org