The SIS lets you assign fine-grained tracing debug levels to components and subscriptions.

This means you do not need to enable debug logging for all calls that pass through the SIS — which can can significantly degrade performance — when you’re only interested in calls to (or with reference to) particular addresses or calls that trigger certain compositions.

Below are an overview of SIS trace debug levels, instructions for enabling fine-grained tracing, and an example.

Trace debug levels

The SIS currently supports the following trace debug levels:

Level Description

0

No debugging information output.

1

Trace messages output, summarising the flow of messages between the network, SIS and the SLEE.

2

Same as level 1, plus expanded detail of the contents of each message.

3

Same as level 2, plus all internal debugging of the SIS and its decision-making progress. (This is the most verbose debug level and produces a great deal of output.)

Component settings

You can assign fine-grained tracing debug levels to individual compositions, address subscriptions, service key subscriptions, and trigger addresses.

Tip
Initial settings, changes, and default

  • You can specify initial fine-grained trace level settings, that apply when a composition is installed or when a subscription is created.

  • Changes to component fine-grained trace level settings can be made at any time, and take immediate effect (if fine-grained tracing has been enabled).

  • The default component fine-grained trace level, if unspecified, is 0.
Warning
Changes only apply to new calls

The SIS determines the debug level for the lifetime of a call during composition selection. Any changes to debug levels in profiles, or enabling fine-grained tracing, apply only to new calls (those subsequently triggered in the SIS).

Fine-grained tracing

To use the SIS fine-grained tracing features:

  1. Enable fine-grained tracing in the SIS — required for the SIS to check any other fine-grained tracing settings.

  2. Reload the SIS configuration, for the configuration change to take effect.

  3. Configure fine-grained tracing debug levels for compositions, subscriptions, or trigger addresses in the SIS as required.

Example

Below are sis-console commands and Rhino log output for an example of assigning fine-grained tracing.

sis-console commands

[Rhino@localhost (#1)] setfinegrainedtracingenabled sis-cap true
Fine-grained tracing enabled

[Rhino@localhost (#2)] reload sis-cap
Reloaded SIS RA Entity sis-cap

[Rhino@localhost (#3)] updateaddresssubscription sis-cap 3460001234 -debuglevel 3
Updated subscription 34600001234

Rhino log output

2009-10-14 15:27:51.843  Info   [trace.sis_cap.insis.trigger-handler]  [Dialog[appContext=CAPv2:gsmSSF->gsmSCF,appID=6617,dialogID=4212,incarnationID=0]]  dialog debugging triggered for Dialog[appContext=CAPv2:gsmSSF->gsmSCF,appID=6617,dialogID=4212,incarnationID=0] at debug level 3 due to a subscription profile
2009-10-14 15:27:51.844  Info   [trace.sis_cap.insis-trace.flow]    Cap 0  NW   ---------O_InitialDP clg=600001234 cld=610031274---------> INSIS
2009-10-14 15:27:51.902  Info   [trace.sis_cap.insis-trace.detail]    Cap 0   NW -> INSIS(event:InitialDP)
    InitialDP[
        dialog=Dialog[appContext=CAPv2:gsmSSF->gsmSCF,appID=6617,dialogID=4212,incarnationID=0]
        invokeID=0
        serviceKey=50
        ...
        ]
2009-10-14 15:27:51.903  Info   [trace.sis_cap.insis.trigger-handler]  [Dialog[appContext=CAPv2:gsmSSF->gsmSCF,appID=6617,dialogID=4212,incarnationID=0]]  accepting open request
2009-10-14 15:27:51.948  Info   [trace.sis_cap.insis-trace.flow]    Cap 0  NW   <-----------------OpenResponse[accepted]------------------ INSIS
2009-10-14 15:27:51.948  Info   [trace.sis_cap.insis-trace.detail]    Cap 0   NW <- INSIS(event:OpenRequest)
    OpenResponse[
        accepted?=true
        appContext=CAPv2:gsmSSF->gsmSCF
        ]
2009-10-14 15:27:51.949  Info   [trace.sis_cap.insis.trigger-handler]  [Dialog[appContext=CAPv2:gsmSSF->gsmSCF,appID=6617,dialogID=4212,incarnationID=0]]  setState(SERVICE_COMPOSITION_DISCOVERY -> MONITORING)
2009-10-14 15:27:53.076  Info   [trace.sis_cap.insis.virtual-ssf]  [Dialog[appContext=CAPv2:gsmSSF->gsmSCF,appID=6617,dialogID=4212,incarnationID=0]]  setFlags(INITIAL: [] -> [BUSY_INPUT])
2009-10-14 15:27:53.154  Info   [trace.sis_cap.insis.virtual-ssf]  [Dialog[appContext=CAPv2:gsmSSF->gsmSCF,appID=6617,dialogID=4212,incarnationID=0]]  beginning event processing of: [OpenRequest, InitialDP, Delimiter]
2009-10-14 15:27:53.154  Info   [trace.sis_cap.insis.virtual-ssf]  [Dialog[appContext=CAPv2:gsmSSF->gsmSCF,appID=6617,dialogID=4212,incarnationID=0]]  setState(INITIAL -> SERVICE_COMPOSITION_EVALUATION: [BUSY_INPUT])
2009-10-14 15:27:53.173  Info   [trace.sis_cap.insis.model]   [Dialog[appContext=CAPv2:gsmSSF->gsmSCF,appID=6617,dialogID=4212,incarnationID=0]]  current call leg state: [1:{COLLECTED_INFO:[]}]
2009-10-14 15:27:53.216  Info   [trace.sis_cap.insis.virtual-ssf]   [Dialog[appContext=CAPv2:gsmSSF->gsmSCF,appID=6617,dialogID=4212,incarnationID=0]]  service composition says to invoke ServiceRefID[VPN]
2009-10-14 15:27:53.235  Info   [trace.sis_cap.insis.virtual-ssf]   [Dialog[appContext=CAPv2:gsmSSF->gsmSCF,appID=6617,dialogID=4212,incarnationID=0]]  entering event processing loop for event(s): [OpenRequest, InitialDP, Delimiter]
...
Previous page Next page
SIS Version 2.5.4