Login:
  • Home
  • →
  • Desktops
  • →
  • Free manual HP   HP NonStop G-Series
Votes - , Average rating: ( )

User manual HP, model HP NonStop G-Series

Manafacture: HP
File size: 22.45 kb
File name:

Language of manual:en

The document is loading, please wait
Download nowClose
The document is loading, please wait
Download nowClose


Other manuals for this model:

manual abstract


file:///C|/Corba Readmes/ReadmeCORBA23u3.txt
The BSD uses a standard interoperable protocol to bootstrap to
the initial root naming context on any arbitrary host.
ORBs that implement this protocol issue Bootstrap GIOP
Request messages.
CORBA::ORB::resolve_initial_reference(ObjectId)
This operation is equal to "get".
CORBA::ORB::ObjectIdList CORBA::ORB::list_initial_services()
This operation is equal to "list".
3) When a transaction context is inherited from one process to
another, an imported transaction branch is created. A
transaction branch is represented by a new TMF transaction
identifier called the XID. The root XID and any branch XIDs are
not recognized by TMF nor SQL as representing the same
transaction. This means that if a process such as an application,
starts a transaction and makes multiple invocations on server
processes, multiple XIDs can be created resulting in SQL errors
or blocking. Graphically, this situation is often referred to
as the diamond access problem. It is up to the application
designer to avoid this. However, if more than one NSotsTM is
configured in a server pool, then multiple requests on the same
transaction branch may be routed through more than one NSotsTM.
This also produces the diamond access problem and is beyond the
control of the application designer.
To solve this problem NSots includes an XID Broker function.
The XID Broker brokers requests for imported transactions within
the pool of NSotsTMs by routing secondary import requests back
to the NSotsTM that originally imported the transaction. This
breaks the diamond pattern. In previous versions of NSots, the
broker function was provided through a shared file. Although
accessed at low priority, the shared file implementation was a
bottleneck because of process blocking during I/O. The B12
release of NSots replaces the file implementation with a
singleton process named NSotsXID.

If and only if more than one NSotsTM process is configured in a
process pool it is necessary to also configure one and only one
NSotsXID process. It is also necessary to define the environment
variable NSOTS_XID_BROKER_REQUIRED. These steps are shown in
commentary form in the script file NSDSTART. They are also
supported by the administration Console. If the environment
variable is defined and NSotsXID is not available because it was
not configured or crashed, the applications should receive the
exception CORBA::TRANSIENT.
4) Previously, the UNINSTALL script did not remove the TMF
Resource Managers created by the OTS components. The script has
been enhanced to perform this function.
In order to execute this step, you must be logged on as a super
group user.
5) Previously, the C++ process runtime created a single file
system connection (AKA open) between a client and server.
Ten WRITEREAD operations were allowed to travel across this
file:///C|/Corba Readmes/ReadmeCORBA23u3.txt (11 of 15) [4/27/2004 11:41:35 AM]

...

Other models in this manual:
Desktops - HP NonStop L-Series (22.45 kb)

Reviews



Your review
Your name:
Please, enter two numbers from picture:
capcha





Category