bea Home | 製品 | dev2dev | support | askBEA |
![]() |
![]() |
|
![]() |
e-docs > Tuxedo > メッセージ > IJINFRA カタログ リスト > IJINFRA メッセージ 100-199 |
|
IJINFRA メッセージ 100-199
100 |
ERROR: Cannot find com.beasys.Tobj.threading.ApplicationThread class | |
|
説明 |
An attempt to find the |
アクション |
Make sure that the corresponding WLE Java JAR file is included in the class path. | |
101 |
ERROR: Cannot find com.beasys.Tobj.threading.ApplicationThread.infrastructure_queue field | |
|
説明 |
An attempt to find the |
アクション |
Contact BEA Customer Support. | |
102 |
ERROR: Cannot find com.beasys.Tobj.threading.ApplicationThread.infrastructure_queue | |
|
説明 |
An attempt to find the |
アクション |
Contact BEA Customer Support. | |
103 |
ERROR: Cannot find com.beasys.Tobj.infrastructure.Debug class | |
|
説明 |
An attempt to find the |
アクション |
Make sure that the corresponding WLE Java JAR file is included in the class path. | |
104 |
ERROR: Cannot find com.beasys.Tobj.infrastructure.Debug.setLevel | |
|
説明 |
An attempt to find the |
アクション |
Contact BEA Customer Support. | |
105 |
ERROR: tpcommit reported err in reply processing | |
|
説明 |
An attempt to call the |
アクション |
Contact BEA Customer Support. | |
106 |
WARN: transaction processing failure in reply processing | |
|
説明 |
A transaction processing failure has been encountered during the processing of a reply. |
アクション |
None. This may result in a more severe problem that will be logged as an error. | |
107 |
WARN: _tmfmsg_copy_tcm fails | |
|
説明 |
A call to the |
アクション |
None. This may result in a more severe problem that will be logged as an error. | |
108 |
ERROR: Failed to send reply: err | |
|
説明 |
An attempt to send a reply has failed. The detailed error is provided in the error message |
アクション |
Contact BEA Customer Support. | |
109 |
WARN: Number of worker threads specified is too high. Resetting to 500. | |
|
説明 |
The number of the worker threads specified in the |
アクション |
None. | |
110 |
ERROR: Cannot find com.beasys.Tobj.infrastructure.ServerMain.sendTransactionReply | |
|
説明 |
An attempt to find the |
アクション |
Contact BEA Customer Support. | |
111 |
ERROR: Cannot find com.beasys.Tobj.threading.ThreadMonitor.initThreadPool | |
|
説明 |
An attempt to find the |
アクション |
Contact BEA Customer Support. | |
112 |
ERROR: Cannot open internal temporary file | |
|
説明 |
The program could not create or open an internal temporary file in this directory. |
アクション |
Make sure that permissions have been set so that this program can open, read, and write internal temporary files. | |
113 |
ERROR: Out of memory | |
|
説明 |
An attempt to allocate space for internal data structures failed as the server process ran out of memory. |
アクション |
This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine, or increase the amount of physical memory on the machine. | |
114 |
ERROR: Cannot write to internal temporary file | |
|
説明 |
The program could not create or open an internal temporary file in this directory. |
アクション |
Make sure that permissions have been set so that this program can open, read, and write internal temporary files. | |
115 |
ERROR: Cannot advertise admin service | |
|
説明 |
An attempt to advertise the administration service for server threads administration failed. |
アクション |
Contact BEA Customer Support. | |
116 |
ERROR: Cannot unadvertise admin service | |
|
説明 |
An attempt to unadvertise the administration service for server threads administration failed. |
アクション |
Contact BEA Customer Support. | |
117 |
ERROR: Cannot find com.beasys.Tobj.threading.ThreadMonitor.getIdle | |
|
説明 |
An attempt to find the |
アクション |
Contact BEA Customer Support. | |
118 |
ERROR: Cannot find com.beasys.Tobj.threading.ThreadMonitor.getStarted | |
|
説明 |
An attempt to find the |
アクション |
Contact BEA Customer Support. | |
119 |
ERROR: Server initialization failed | |
|
説明 |
The initialization of the JavaServer failed. |
アクション |
Check the | |
127 |
ERROR: Cannot convert client_id field | |
|
説明 |
An error occurred when converting |
アクション |
Contact BEA Customer Support. | |
131 |
WARN: Access control violation - user sub on sub tried to access sub sub | |
|
説明 |
This is a warning message indicating an EJB method access control violation. A proper exception will be returned. |
アクション |
Check the deployment descriptor for proper security setting. | |
132 |
WARN: .SysACLPerm: User sub on sub tried to access sub sub | |
|
説明 |
This is a warning message indicating an EJB method access control violation. A proper exception will be returned. |
アクション |
Check the deployment descriptor for proper security setting. | |
133 |
ERROR: ax_reg returns err | |
|
説明 |
An attempt by the multithreaded JavaServerXA to dynamically register with the WLE infrastructure failed. The details of the error are provided in the error code err. |
アクション |
Contact BEA Customer Support. | |
134 |
ERROR: Cannot init TLS | |
|
説明 |
An attempt to initialize the WLE internal thread of the local storage data structure failed. |
アクション |
Contact BEA Customer Support. | |
135 |
ERROR: xa_open returns err | |
|
説明 |
An attempt by the WLE infrastructure to initialize the Resource Manager via an |
アクション |
Refer to the X/Open XA specification for a definition of the XA error code. Also check the resource manager vendor's trace file for additional information, if any. If applicable, correct any resource manager problems.
If it is a CORBA application, make sure | |
136 |
ERROR: xa_start returns err | |
|
説明 |
An attempt by the WLE infrastructure to perform |
アクション |
Refer to the X/Open XA specification for a definition of the XA error code. Also check the resource manager vendor's trace file for additional information, if any. If applicable, correct any resource manager problems. If the problem persists, contact BEA Customer Support. | |
137 |
ERROR: xa_end returns err | |
|
説明 |
An attempt by the WLE infrastructure to perform |
アクション |
Refer to the X/Open XA specification for a definition of the XA error code. Also check the resource manager vendor's trace file for additional information, if any. If applicable, correct any resource manager problems. If the problem persists, contact BEA Customer Support. | |
138 |
ERROR: Out of memory | |
|
説明 |
An attempt to allocate memory for WLE internal data structure failed. |
アクション |
This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine, or increase the amount of physical memory on the machine. If the problem persists, contact BEA Customer Support. | |
139 |
ERROR: Cannot init TLS | |
|
説明 |
An attempt to initialize the WLE internal thread of the local storage data structure failed. |
アクション |
Contact BEA Customer Support. | |
140 |
ERROR: Cannot init TLS | |
|
説明 |
An attempt to initialize the WLE internal thread of the local storage data structure failed. |
アクション |
Contact BEA Customer Support. | |
141 |
WARN: Attempt to use multithreaded JavaServer without setting multithreaded RM option | |
|
説明 |
This is a warning message to indicate that the multithreaded JavaServerXA is used without specifying the multithreaded option for the particular resource manager. |
アクション |
It is highly recommended that the multithreaded JavaServer should be used with the multithreaded resource manager option turned on. Otherwise, unexpected run-time behavior may result. Ignore this warning if the resource manager being used does not have a specific multithreading option. | |
142 |
WARN: xa_start() failed with error: err | |
|
説明 |
This is a warning message to indicate that an attempt by the WLE infrastructure to call |
アクション |
None. This may subsequently result in a more severe error. If so, the error message will be displayed in the ULOG. | |
143 |
WARN: xa_end() failed with error: err | |
|
説明 |
This is a warning message to indicate that an attempt by the WLE infrastructure to call |
アクション |
None. This may subsequently result in a more severe error. If so, the error message will be displayed in the ULOG. | |
144 |
ERROR: xa_open returns err | |
|
説明 |
An attempt by the WLE infrastructure to initialize the resource manager via the |
アクション |
Refer to the X/Open XA specification for a definition of the XA error code. Also check the resource manager vendor's trace file for additional information, if any. If applicable, correct any resource manager problems.
If it is a CORBA application, make sure | |
145 |
WARN: xa_start() failed in pre-prepare phase with error = err | |
|
説明 |
This is a warning message to indicate that an attempt by the WLE infrastructure to
call |
アクション |
None. This may subsequently result in a more severe error. If so, the error message will be displayed in the ULOG. | |
146 |
WARN: xa_end() failed in pre-prepare phase with error = err | |
|
説明 |
This is a warning message to indicate that an attempt by the WLE infrastructure
to call |
アクション |
None. This may subsequently result in a more severe error. If so, the error message will be displayed in the ULOG. | |
148 |
WARN: Switching to FASTPATH; PROTECTED is not supported for JavaServers | |
|
説明 |
This is a warning message indicating that |
アクション |
None. | |
149 |
ERROR: Cannot allocate FML32 buffer | |
|
説明 |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
アクション |
This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
150 |
ERROR: Call to TMIB failed | |
|
説明 |
The server process was unable to call the |
アクション |
Contact BEA Customer Support. | |
151 |
ERROR: No MODULE specified | |
|
説明 |
The |
アクション |
Check and correct the | |
152 |
ERROR: Invalid Module name | |
|
説明 |
Invalid |
アクション |
Check and correct the | |
153 |
ERROR: Failed to initialize Request Level Interceptors | |
|
説明 |
A problem was encountered while reading the Registry for Request Level Interceptors. |
アクション |
Contact BEA Customer Support. | |
154 |
WARN: JAVA_HOME not set. Cannot add tools.jar to CLASSPATH for debugging | |
|
説明 |
This is a warning message indicating that |
アクション |
Set the | |
155 |
ERROR: Cannot initialize Request Level Interceptors | |
|
説明 |
A problem was encountered while setting up the Request Level Interceptors. |
アクション |
Contact BEA Customer Support. | |
156 |
ERROR: Cannot initialize buffer pool | |
|
説明 |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
アクション |
This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
157 |
ERROR: Exception occurred in server main init | |
|
説明 |
The server process initialization has failed because of an internal error. |
アクション |
Contact BEA Customer Support. | |
158 |
ERROR: Cannot get input buffer type | |
|
説明 |
An attempt to get the incoming request buffer type failed. |
アクション |
Contact BEA Customer Support. | |
159 |
ERROR: Cannot allocate request input stream | |
|
説明 |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
アクション |
This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
160 |
ERROR: Cannot get service definition for sub | |
|
説明 |
Cannot find the definition for the specified service request. |
アクション |
Contact BEA Customer Support. | |
161 |
ERROR: Cannot preserve input buffer | |
|
説明 |
After the incoming request was processed, the associated internal buffer failed to be released. |
アクション |
Contact BEA Customer Support. | |
162 |
WARN: Unexpected context switch | |
|
説明 |
This is a warning message indicating that an unexpected context switch occurred. |
アクション |
None. | |
163 |
ERROR: Cannot reattach to Bulletin Board | |
|
説明 |
An attempt to reattach the server process to the Bulletin Board failed while the JavaServer was trying to switch to |
アクション |
Contact BEA Customer Support. | |
164 |
ERROR: Cannot change FML32 buffer | |
|
説明 |
An internal error occurred when the server process was preparing the data buffer to make the |
アクション |
Contact BEA Customer Support. | |
165 |
ERROR: Cannot initialize server main | |
|
説明 |
The server process initialization has failed because of an internal error. |
アクション |
Contact BEA Customer Support. | |
166 |
ERROR: Failed read of Orb Registry | |
|
説明 |
The JavaServer's attempt to read the Request Level Interceptor configuration failed on opening the Registry or accessing the appropriate configuration set. |
アクション |
Contact BEA Customer Support. | |
167 |
ERROR: Cannot access file sub | |
|
説明 |
The jar file that contains the Request Level Interceptors cannot be found on the specified path. |
アクション |
Check the Registry to see if the file was configured properly and check the path to see if it is correct and the file exists. | |
168 |
ERROR: Cannot access file sub in | |
|
説明 |
The jar file that contains the Request Level Interceptors cannot be found relative to any path specified in the |
アクション |
Check the Registry to see if the file was configured properly and check the paths in | |
169 |
ERROR: Cannot change FML32 buffer | |
|
説明 |
An internal error occurred when the server process was preparing the data buffer to make the |
アクション |
Contact BEA Customer Support. | |
170 |
ERROR: Call to TMIB failed | |
|
説明 |
The server process was unable to call the |
アクション |
Contact BEA Customer Support. | |
171 |
ERROR: System Registry open failed | |
|
説明 |
The JavaServer failed to open the Registry. |
アクション |
Contact BEA Customer Support. | |
172 |
ERROR: AppRequestInterceptors key not found | |
|
説明 |
The entry was not found in the Registry. |
アクション |
Contact BEA Customer Support. | |
173 |
ERROR: ImagePath key not found | |
|
説明 |
The entry was not found in the Registry. |
アクション |
Contact BEA Customer Support. | |
174 |
ERROR: EntryPoint key not found | |
|
説明 |
The entry was not found in the Registry. |
アクション |
Contact BEA Customer Support. | |
175 |
ERROR: EntryPoint value cannot be empty | |
|
説明 |
The entry was not found in the Registry. |
アクション |
Contact BEA Customer Support. | |
176 |
ERROR: DisplayName key not found | |
|
説明 |
The entry was not found in the Registry. |
アクション |
Contact BEA Customer Support. | |
177 |
ERROR: Group key not found | |
|
説明 |
The entry was not found in the Registry. |
アクション |
Contact BEA Customer Support. | |
178 |
ERROR: ErrorControl key not found | |
|
説明 |
The entry was not found in the Registry. |
アクション |
Contact BEA Customer Support. | |
179 |
ERROR: JavaServer cannot be part of MSSQ set | |
|
説明 |
JavaServer will not work on an MSSQ set. The JavaServer is not started. |
アクション |
Contact BEA Customer Support. | |
180 |
WARN: REPLYQ=Y not supported in multithreaded mode. Reverting to REPLYQ=N | |
|
説明 |
This is a warning message indicating that |
アクション |
None. | |
181 |
ERROR: Green Thread is not supported on HPUX | |
|
説明 |
An attempt to use Green Thread to build the JavaServer failed; the Green Thread model is not supported on HPUX. |
アクション |
Check for a proper JDK development environment on your HPUX system. | |
182 |
ERROR: Out of memory | |
|
説明 |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
アクション |
This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
183 |
ERROR: Out of memory | |
|
説明 |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
アクション |
This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
188 |
ERROR: Type switch buffer uninitialization routine failure | |
|
説明 |
An internal error occurred while attempting to free the request buffer after the request is finished. |
アクション |
Contact BEA Customer Support. | |
189 |
ERROR: Cannot allocate reply buffer | |
|
説明 |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
アクション |
This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
190 |
ERROR: Reply length is zero | |
|
説明 |
A zero length reply message was received for the service request. |
アクション |
Contact BEA Customer Support. |
![]() |
![]() |
![]() |
![]() |
||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |