システム・メッセージ: IJINFRAカタログ100-199
|
105 |
ERROR: tpcommit reported err in reply processing | |
|
Description |
An attempt to call the |
Action |
Contact Oracle Customer Support. | |
106 |
WARN: transaction processing failure in reply processing | |
|
Description |
A transaction processing failure has been encountered during the processing of a reply. |
Action |
None. This may result in a more severe problem that will be logged as an error. | |
107 |
WARN: _tmfmsg_copy_tcm fails | |
|
Description |
A call to the |
Action |
None. This may result in a more severe problem that will be logged as an error. | |
108 |
ERROR: Failed to send reply: err | |
|
Description |
An attempt to send a reply has failed. The detailed error is provided in the error message |
Action |
Contact Oracle Customer Support. | |
109 |
WARN: Number of worker threads specified is too high. Resetting to 500. | |
|
Description |
The number of the worker threads specified in the |
Action |
None. | |
112 |
ERROR: Cannot open internal temporary file | |
|
Description |
The program could not create or open an internal temporary file in this directory. |
Action |
Make sure that permissions have been set so that this program can open, read, and write internal temporary files. | |
113 |
ERROR: Out of memory | |
|
Description |
An attempt to allocate space for internal data structures failed as the server process ran out of memory. |
Action |
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 | |
|
Description |
The program could not create or open an internal temporary file in this directory. |
Action |
Make sure that permissions have been set so that this program can open, read, and write internal temporary files. | |
127 |
ERROR: Cannot convert client_id field | |
|
Description |
An error occurred when converting |
Action |
Contact Oracle Customer Support. | |
131 |
WARN: Access control violation - user sub on sub tried to access sub sub | |
|
Description |
This is a warning message indicating an EJB method access control violation. A proper exception will be returned. |
Action |
Check the deployment descriptor for proper security setting. | |
132 |
WARN: .SysACLPerm: User sub on sub tried to access sub sub | |
|
Description |
This is a warning message indicating an EJB method access control violation. A proper exception will be returned. |
Action |
Check the deployment descriptor for proper security setting. | |
133 |
ERROR: ax_reg returns err | |
|
Description |
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. |
Action |
Contact Oracle Customer Support. | |
134 |
ERROR: Cannot init TLS | |
|
Description |
An attempt to initialize the WLE internal thread of the local storage data structure failed. |
Action |
Contact Oracle Customer Support. | |
135 |
ERROR: xa_open returns err | |
|
Description |
An attempt by the WLE infrastructure to initialize the Resource Manager via an |
Action |
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 | |
|
Description |
An attempt by the WLE infrastructure to perform |
Action |
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 Oracle Customer Support. | |
137 |
ERROR: xa_end returns err | |
|
Description |
An attempt by the WLE infrastructure to perform |
Action |
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 Oracle Customer Support. | |
138 |
ERROR: Out of memory | |
|
Description |
An attempt to allocate memory for WLE internal data structure failed. |
Action |
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 Oracle Customer Support. | |
139 |
ERROR: Cannot init TLS | |
|
Description |
An attempt to initialize the WLE internal thread of the local storage data structure failed. |
Action |
Contact Oracle Customer Support. | |
140 |
ERROR: Cannot init TLS | |
|
Description |
An attempt to initialize the WLE internal thread of the local storage data structure failed. |
Action |
Contact Oracle Customer Support. | |
141 |
WARN: Attempt to use multithreaded JavaServer without setting multithreaded RM option | |
|
Description |
This is a warning message to indicate that the multithreaded JavaServerXA is used without specifying the multithreaded option for the particular resource manager. |
Action |
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 | |
|
Description |
This is a warning message to indicate that an attempt by the WLE infrastructure to call |
Action |
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 | |
|
Description |
This is a warning message to indicate that an attempt by the WLE infrastructure to call |
Action |
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 | |
|
Description |
An attempt by the WLE infrastructure to initialize the resource manager via the |
Action |
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 | |
|
Description |
This is a warning message to indicate that an attempt by the WLE infrastructure to
call |
Action |
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 | |
|
Description |
This is a warning message to indicate that an attempt by the WLE infrastructure
to call |
Action |
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 | |
|
Description |
This is a warning message indicating that |
Action |
None. | |
149 |
ERROR: Cannot allocate FML32 buffer | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
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 | |
|
Description |
The server process was unable to call the |
Action |
Contact Oracle Customer Support. | |
151 |
ERROR: No MODULE specified | |
|
Description |
The |
Action |
Check and correct the | |
152 |
ERROR: Invalid Module name | |
|
Description |
Invalid |
Action |
Check and correct the | |
153 |
ERROR: Failed to initialize Request Level Interceptors | |
|
Description |
A problem was encountered while reading the Registry for Request Level Interceptors. |
Action |
Contact Oracle Customer Support. | |
154 |
WARN: JAVA_HOME not set. Cannot add tools.jar to CLASSPATH for debugging | |
|
Description |
This is a warning message indicating that |
Action |
Set the | |
155 |
ERROR: Cannot initialize Request Level Interceptors | |
|
Description |
A problem was encountered while setting up the Request Level Interceptors. |
Action |
Contact Oracle Customer Support. | |
156 |
ERROR: Cannot initialize buffer pool | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
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 | |
|
Description |
The server process initialization has failed because of an internal error. |
Action |
Contact Oracle Customer Support. | |
158 |
ERROR: Cannot get input buffer type | |
|
Description |
An attempt to get the incoming request buffer type failed. |
Action |
Contact Oracle Customer Support. | |
159 |
ERROR: Cannot allocate request input stream | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
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 | |
|
Description |
Cannot find the definition for the specified service request. |
Action |
Contact Oracle Customer Support. | |
161 |
ERROR: Cannot preserve input buffer | |
|
Description |
After the incoming request was processed, the associated internal buffer failed to be released. |
Action |
Contact Oracle Customer Support. | |
162 |
WARN: Unexpected context switch | |
|
Description |
This is a warning message indicating that an unexpected context switch occurred. |
Action |
None. | |
163 |
ERROR: Cannot reattach to Bulletin Board | |
|
Description |
An attempt to reattach the server process to the Bulletin Board failed while the JavaServer was trying to switch to |
Action |
Contact Oracle Customer Support. | |
164 |
ERROR: Cannot change FML32 buffer | |
|
Description |
An internal error occurred when the server process was preparing the data buffer to make the |
Action |
Contact Oracle Customer Support. | |
165 |
ERROR: Cannot initialize server main | |
|
Description |
The server process initialization has failed because of an internal error. |
Action |
Contact Oracle Customer Support. | |
166 |
ERROR: Failed read of Orb Registry | |
|
Description |
The JavaServer's attempt to read the Request Level Interceptor configuration failed on opening the Registry or accessing the appropriate configuration set. |
Action |
Contact Oracle Customer Support. | |
167 |
ERROR: Cannot access file sub | |
|
Description |
The jar file that contains the Request Level Interceptors cannot be found on the specified path. |
Action |
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 | |
|
Description |
The jar file that contains the Request Level Interceptors cannot be found relative to any path specified in the |
Action |
Check the Registry to see if the file was configured properly and check the paths in | |
169 |
ERROR: Cannot change FML32 buffer | |
|
Description |
An internal error occurred when the server process was preparing the data buffer to make the |
Action |
Contact Oracle Customer Support. | |
170 |
ERROR: Call to TMIB failed | |
|
Description |
The server process was unable to call the |
Action |
Contact Oracle Customer Support. | |
171 |
ERROR: System Registry open failed | |
|
Description |
The JavaServer failed to open the Registry. |
Action |
Contact Oracle Customer Support. | |
172 |
ERROR: AppRequestInterceptors key not found | |
|
Description |
The entry was not found in the Registry. |
Action |
Contact Oracle Customer Support. | |
173 |
ERROR: ImagePath key not found | |
|
Description |
The entry was not found in the Registry. |
Action |
Contact Oracle Customer Support. | |
174 |
ERROR: EntryPoint key not found | |
|
Description |
The entry was not found in the Registry. |
Action |
Contact Oracle Customer Support. | |
175 |
ERROR: EntryPoint value cannot be empty | |
|
Description |
The entry was not found in the Registry. |
Action |
Contact Oracle Customer Support. | |
176 |
ERROR: DisplayName key not found | |
|
Description |
The entry was not found in the Registry. |
Action |
Contact Oracle Customer Support. | |
177 |
ERROR: Group key not found | |
|
Description |
The entry was not found in the Registry. |
Action |
Contact Oracle Customer Support. | |
178 |
ERROR: ErrorControl key not found | |
|
Description |
The entry was not found in the Registry. |
Action |
Contact Oracle Customer Support. | |
179 |
ERROR: JavaServer cannot be part of MSSQ set | |
|
Description |
JavaServer will not work on an MSSQ set. The JavaServer is not started. |
Action |
Contact Oracle Customer Support. | |
180 |
WARN: REPLYQ=Y not supported in multithreaded mode. Reverting to REPLYQ=N | |
|
Description |
This is a warning message indicating that |
Action |
None. | |
181 |
ERROR: Green Thread is not supported on HPUX | |
|
Description |
An attempt to use Green Thread to build the JavaServer failed; the Green Thread model is not supported on HPUX. |
Action |
Check for a proper JDK development environment on your HPUX system. | |
182 |
ERROR: Out of memory | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
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 | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
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 |
エラー: 型スイッチ・バッファ初期化解除ルーチンに失敗しました | |
|
説明 |
リクエストの終了後にリクエスト・バッファを解放しようとしましたが、内部エラーが発生しました。 |
アクション |
Oracleカスタマ・サポートに連絡してください。 | |
189 |
ERROR: Cannot allocate reply buffer | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
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 | |
|
Description |
A zero length reply message was received for the service request. |
Action |
Contact Oracle Customer Support. |