Restrictions on the Component Transaction Service
Restrictions on the Component Transaction Service
The Component Transaction Service be used with the following products:
•Interstage Application Server Enterprise Edition
•Interstage Application Server Standard Edition
•Interstage Application Server Plus
Table 2-14 Restrictions on the Component Transaction Service
No. | Restriction | Remarks | Date of |
|
|
| Removal |
|
|
|
|
1 |
| None | Not |
| If Interstage is initialized in succession using the |
| determined |
|
|
| |
| Interstage operation tool or the isinit command, |
|
|
| the initialization of Interstage may fail. |
|
|
2 |
| Set the installation path | Not |
| When the Component Transaction Service is | of Interstage to no more | determined |
| than 230 bytes |
| |
| used, the start of Interstage and the start of the |
|
|
| WorkUnit may become unusual if the installation |
|
|
| path of Interstage exceeds 230 bytes. |
|
|
|
|
|
|
3 |
| Start OD, then re- | Not |
| If the tdc command is executed before OD has | execute the tdc | determined |
| command. |
| |
| been started, the following message is displayed |
|
|
| ("/tmp/aaa" and "1.0" is variable): |
|
|
| "/tmp/aaa", line 1: |
|
|
| CORBA_ORB_init Error |
|
|
| tdc: Stop. IDLparser status = 4 |
|
|
| IDLdestroy_rep (I/R) |
|
|
| :CORBA_ORB_init |
|
|
| :IDL:CORBA/StExcep/UNKNOWN:1.0 |
|
|
