Cloud CM-IPMP Anleitung zur Fehlerbehebung Seite 120
- Seite / 201
- Inhaltsverzeichnis
- LESEZEICHEN
Bewertet. / 5. Basierend auf Kundenbewertungen
SBB
This example shows fragments of the JAIN SLEE 1.0 specification defined SBB deployment descriptor, and a corresponding
extension DD that informs Rhino that the SBB should use optimistic concurrency control.
SBB deployment descriptor fragment:
<sbb-jar>
<sbb id="TestSBB">
<description>Test SBB to show use of extension DD mechanism</description>
...
</sbb>
</sbb-jar>
SBB Extension deployment descriptor fragment:
<oc-sbb-jar>
<sbb id="TestSBB">
<lock-strategy>optimistic</lock-strategy>
...
</sbb>
</oc-sbb-jar>
18.6 Application Fail-Over
The JAIN SLEE programming model and the Rhino implementation of JAIN SLEE include some important robustness features
that should be considered by a developer when writing applications that will be in deployment for a long period of time.
One of the most important resources to manage when programming long running applications is memory. The JAIN SLEE
programming model alleviates a lot of the burden of memory management from the application developer by requiring the
SLEE implementation to manage the lifecycles of SBB entities and their state.
18.6.1 Programming Model
The JAIN SLEE programming model understands the relationship between an event producer and an event consumer. For
example consider that an SBB entity is an event consumer and an Activity is the event producer. If the SBB entity is not
attached to any ActivityContext then it will be deleted. Likewise if the ActivityContext ends then the SBB entities that are
attached to it are detached, in which case some SBB entities will not attached to any ActivityContext.
This model causes the following types of questions to be asked: What happens if the system is overloaded and cannot process
the activity as being ended? What happens if a Rhino node fails and the state of the SBB entity is replicated – will this leak
MemDB state?
The reason why Rhino SLEE will not run out of memory resource in either of these cases is that each Activity Rhino knows
of is periodically queried after it has been idle for a period of time. The RA is asked if the Activity has finished. The RA
understands the meaning of an activity and can end the activity if it has finished. This will cause the above deletion process to
occur thereby ensuring that resource is not leaked.
This process is explained using the following example for the SIP protocol.
Example
A developer writes an SBB that is interested in certain events (e.g. SIP events such as an INVITE and a BYE message). Assume
that the call progresses and a BYE is not received (either it was not sent by the SIP client, or the network between the SIP client
and Rhino was cut, or there could have been a 4xx message or a CANCEL message). If the SBB entity was not deleted by the
SLEE, then there would be a resource leak.
In the case of SIP all SIP messages are delivered on a SIP transaction activity. The SIP RA understands the SIP protocol and
Open Cloud Rhino 1.4.3 Administration Manual v1.1 111
- Open Cloud Rhino SLEE 1.4.3 1
- Administration Manual 1
- November 2, 2006 (1838) 2
- Contents 3
- Introduction 10
- The Rhino SLEE Platform 12
- 2.3 Integration 13
- 2.4 Service Development 14
- 2.5 Functional Testing 15
- 2.6 Performance Testing 15
- 2.7 Software Development Kit 16
- JAIN SLEE Overview 17
- 3.3 Event Driven Applications 18
- 3.4 Components 18
- 3.5 Provisioned Data 18
- 3.6 Facilities 18
- 3.7 Activities 19
- 4.2.3 Firewalls 22
- 4.2.4 Unpacking 22
- 4.2.5 Installation 22
- 4.2.6 Unattended Installation 23
- 4.2.7 Configuring a Cluster 23
- 4.2.9 Configuring the Cluster 25
- 4.3 Cluster Lifecycle 26
- 4.3.2 Starting a Node 27
- 4.3.3 Starting a Quorum Node 27
- 4.3.4 Automatic Node Restart 27
- 4.3.5 Starting the SLEE 27
- 4.4 Management Interface 28
- 4.5 Setting the system clock 29
- 4.6 Optional Configuration 30
- 4.7 Installed Files 31
- 4.8 Runtime Files 32
- 4.8.2 Logging output 33
- Management 35
- 5.2 Management Tutorials 36
- 5.3 Building the Examples 37
- 5.5 Installing a Service 40
- 5.6 Uninstalling a Service 43
- 5.8 Creating a Profile 46
- 5.9 SLEE Lifecycle 50
- 5.9.4 The Stopping State 51
- 5.9.2 The Starting State 51
- 5.9.3 The Running State 51
- Administrative Maintenance 52
- 6.2.2 Removing Activities 54
- 6.2.3 Inspecting SBBs 55
- 6.2.4 Removing SBB Entities 56
- 6.2.5 Removing All 56
- 6.3 Upgrading a Cluster 57
- 6.3.3 Deploying State 58
- 6.4 Backup and Restore 59
- Export and Import 60
- 7.2 Exporting State 61
- 7.3 Importing State 62
- 7.4 Partial Imports 63
- Statistics and Monitoring 65
- 8.2 Performance Implications 66
- 8.3 Console Mode 66
- 8.3.1 Useful output options 67
- 8.4 Graphical Mode 68
- Web Console 73
- 9.2.2 Managed Objects 74
- 9.2.3 Navigation Shortcuts 74
- 9.3 Deployment Architecture 75
- 9.3.2 Standalone Web Console 76
- 9.4 Configuration 77
- 9.5 Security 77
- 9.5.2 Declarative Security 78
- 9.5.3 JAAS 78
- Log System Configuration 79
- 10.3 Logging Configuration 80
- 10.3.2 Web Console Logging 81
- Chapter 11 84
- 11.2.2 Web Console 85
- Threshold Alarms 87
- 12.5 Types of Rule Conditions 88
- 12.6 Creating Rules 89
- 12.6.2 Command Console 90
- Chapter 13 92
- 13.3.1 Configuration 93
- Licensing 94
- 14.2 Alarms 95
- 14.2.4 Management Interface 96
- 14.2.5 Audit Logs 96
- Security Configuration 97
- 15.3 Network Connections 98
- 15.4 Signing Deployable Units 99
- 15.5 Key Stores 100
- 15.6 Transport Layer Security 100
- 15.7 JAAS Configuration 101
- Performance Tuning 103
- 16.2.3 Tuning Recommendations 104
- 16.2.1 Configuration 104
- 16.2.2 Stage Tuning 104
- 16.3 Object Pool Configuration 105
- 16.4 Fault Tolerance 106
- Clustering 109
- 17.3 Scenarios 110
- 17.4 Configuration Parameters 111
- Application Environment 113
- 18.2.2 Concurrency Control 114
- 18.3 Application Configuration 115
- 18.5.4 Example 119
- 18.6 Application Fail-Over 120
- 18.6.2 Management Interface 121
- Database Connectivity 122
- 19.3 Configuration Example 123
- 19.4 SBB use of JDBC 124
- 19.4.1 SQL Programming 125
- J2EE SLEE Integration 127
- PostgreSQL Configuration 131
- 21.4 TCP/IP Connections 132
- 21.5 Access Control 132
- SIP Example Applications 138
- 22.2 System Requirements 139
- 22.3 Directory Contents 139
- 22.4 Quick Start 139
- 22.4.2 Building and Deploying 140
- 22.5 Manual Installation 144
- 22.6 Using the Services 152
- 22.6.4 Enabling Debug Output 156
- JCC Example Application 157
- 23.2.1 Resource Adaptor 158
- 23.2.3 Service Logic 160
- 23.3 Directory Contents 163
- 23.4 Installation 163
- 23.6.1 Trace Components 170
- 23.6.3 Creating a Call 171
- 23.7 Call Duration Service 172
- Customising the SIP Registrar 178
- 24.4 Extending with Profiles 181
- Hardware and Systems Support 182
- A.2.4 Application Example 184
- Redundant Networking 186
- Entities 191
- C.3 Configuration Properties 192
- C.4 Entity Binding 193
- Transactions 194
- D.3.3 Summary 195
- D.4.3 Commit Protocols 196
- Audit Logs 197
- E.2 Example Audit Logfile 199
- Glossary 200
© 2020, manymanuals.de. Alle Rechte vorbehalten. | 0.050 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Kommentare zu diesen Handbüchern