You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Asankha C. Perera (JIRA)" <ji...@apache.org> on 2008/10/07 17:05:44 UTC
[jira] Created: (SYNAPSE-467) Categorize fault counts as far as
possible (for logging, auditing and JMX monitoring)
Categorize fault counts as far as possible (for logging, auditing and JMX monitoring)
-------------------------------------------------------------------------------------
Key: SYNAPSE-467
URL: https://issues.apache.org/jira/browse/SYNAPSE-467
Project: Synapse
Issue Type: Improvement
Components: Core
Affects Versions: 1.2
Reporter: Eric Hubert
Assignee: Asankha C. Perera
Fix For: 1.3
It must be possible to query at least the following fault counts separately:
- faults received from the service implementations
- connection closes by client
- connection closes by server
- timeouts by Synapse nhttp-setting
- failovers (only for LB endpoints and proxy services)
- custom faults sent back to the client
- Any other special faults which could be clearly separated and which would help to identify problems, like message parsing errors or something like this should be counted individually as well.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Resolved: (SYNAPSE-467) Categorize fault counts as far as
possible (for logging, auditing and JMX monitoring)
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asankha C. Perera resolved SYNAPSE-467.
---------------------------------------
Resolution: Fixed
Fixed on trunk with the initial error codes and expansion as follows:
00000 Generic Error
101000 199999 Transport Errors
101000 101999 HTTP/S
101000 101499 HTTP/S Listener
101000 IO Error sending
101001 IO Error receiving
101500 101999 HTTP/S Sender
101500 IO Error sending
101501 IO Error receiving
101503 Connection failed
101504 Connection timeout
101505 Connection closed
101506 Protocol violation
101507 Connect cancel
101508 Connect timeout
102000 102999 JMS
103000 103999 VFS / File
104000 104999 Mail
105000 105999 FIX
106000 106999 AMQP
107000 107999 UDP / TCP
108000 199999 For future transports
200000 299999 Sequence faults
300000 399999 Endpoint faults
301000 301999 Address Endpoints
302000 302999 WSDL Endpoints
303000 303999 Load Balance Endpoints (incl SA)
303000 LB Endpoint has no ready endpoint to fail over
303100 LB Endpoint failed over to another node
304000 304999 Failover Endpoints
304000 FO Endpoint has no ready endpoint to fail over
304100 FO Endpoint failed over to another node
305000 305999
306000 306999
307000 307999
308000 308999
309000 309999 Generic endpoint failure
309000 No child endpoint ready
More documentation and examples to follow
> Categorize fault counts as far as possible (for logging, auditing and JMX monitoring)
> -------------------------------------------------------------------------------------
>
> Key: SYNAPSE-467
> URL: https://issues.apache.org/jira/browse/SYNAPSE-467
> Project: Synapse
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.2
> Reporter: Eric Hubert
> Assignee: Asankha C. Perera
> Fix For: 1.3
>
>
> It must be possible to query at least the following fault counts separately:
> - faults received from the service implementations
> - connection closes by client
> - connection closes by server
> - timeouts by Synapse nhttp-setting
> - failovers (only for LB endpoints and proxy services)
> - custom faults sent back to the client
> - Any other special faults which could be clearly separated and which would help to identify problems, like message parsing errors or something like this should be counted individually as well.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org