blob: 0d1ea8db316237c4ae0d0659d7ac9d5286f934b6 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
|
This test has two parts, which run automatically:
Part 1:
IIOP_Transport_Current test: Demonstrates how in the application the
user can resolve the IIOP_Transport_Current and use it to obtain
IIOP-related transport properties for the current Transport.
Part 2:
Multi threading test: In this test the server has a Thread Pool. Using
Interceptors, the test tracks the transports that are used in the
individual invocations at various stage of the up-call. This validates
that the TC framework accurately tracks the correct transport for an
invocation, no matter what stage of the up-call in a multi-threaded
environment.
We force creation of multiple transport by using the: static
Client_Strategy_Factory "-ORBTransportMuxStrategy exclusive"
directive. While this isn't 100% guaranteed, having multiple client
threads and making simultaneous invocations should trigger new transport
creation (as it did in lab conditions).
See ../Framework/README for more detail on how and what contexts are
tested.
This test has two parts, which run automatically:
Part 1:
IIOP_Transport_Current test: Demonstrates how in the application the
user can resolve the IIOP_Transport_Current and use it to obtain
IIOP-related transport properties for the current Transport.
Part 2:
Multi threading test: In this test the server has a Thread Pool. Using
Interceptors, the test tracks the transports that are used in the
individual invocations at various stage of the up-call. This validates
that the TC framework accurately tracks the correct transport for an
invocation, no matter what stage of the up-call in a multi-threaded
environment.
We force creation of multiple transport by using the: static
Client_Strategy_Factory "-ORBTransportMuxStrategy exclusive"
directive. While this isn't 100% guaranteed, having multiple client
threads and making simultaneous invocations should trigger new transport
creation (as it did in lab conditions).
See ../Framework/README for more detail on how and what contexts are
tested.
|
