System Messages: RMI Catalog 100-199
|
100 |
IIOPRemoteObjectReference.invokeMethod | |
|
Description |
This should happen only if the Stubs were generated using the unsupported -v1.2 option to the RMI compiler. This option generates alternative stubs. |
Action |
Rerun the RMI compiler without the -v1.2 option. | |
101 |
Problems creating the descriptor | |
|
Description |
Someone attempted to access an internal API to obtain a "descriptor". This feature is not supported in WLE 5.0. |
Action |
Contact Customer Support | |
102 |
IIOPRemoteObjectReference.getHostID | |
|
Description |
This should never happen. |
Action |
Contact Customer Support. | |
103 |
IIOPRemoteObjectReference for val | |
|
Description |
The string representation for a IIOPRemoteObjectReference wrapping a CORBA Object. |
Action |
None. | |
104 |
No IIOPSupport class for val | |
|
Description |
Failed to instantiate an instance to support RMI on IIOP for the effective ORB class on startup. |
Action |
Check that the code is executing in a Oracle ORB and that it was properly initialized. Also check that any installed SecurityManager grants read access to the system property org.omg.CORBA.ORBClass. | |
105 |
Cannot find Stub class | |
|
Description |
The stub class for a remote object was not found. |
Action |
Check that the RMI compiler was run and that the generated stub class is in the class path or is otherwise loadable. | |
106 |
Cannot instantiate Stub class | |
|
Description |
A stub class for a remote object was found but it cannot be instantiated. |
Action |
Check that the RMI compiler was run and that the generated stub class is in the class path or is otherwise loadable. Check that there are no name collisions for the generated stub class. | |
107 |
Cannot instantiate Stub class | |
|
Description |
A stub class for a remote object was found but its default constructor is not accessible. |
Action |
Check that the RMI compiler was run and that the generated stub class is in the class path or is otherwise loadable. Check that there are no name collisions for the generated stub class. | |
108 |
Attempting to insert into a val | |
|
Description |
This internal insertion error should never happen in a properly configured system. |
Action |
Contact Oracle Customer Support. | |
109 |
Failed to marshal val as CORBA object | |
|
Description |
This is an internal error. Conceivably, this can occur when marshaling an incompatible RMI Stub. |
Action |
Contact Oracle Customer Support. | |
110 |
Attempting to extract void value | |
|
Description |
This is an internal error. It is almost certainly a result of a corrupted marshalling stream. |
Action |
Contact Customer Support. | |
111 |
Attempting to extract from a val | |
|
Description |
This internal assertion error should never happen in a properly configured system. The marshaling stream might have been corrupted. |
Action |
Contact Oracle Customer Support. | |
113 |
Failed to advertise class val as interface val | |
|
Description |
This internal error is most likely due to exceeding the configured limit on the interface service map. |
Action |
Raise the interface service map limit. | |
114 |
Oneway interfaces must not contain methods that throw exceptions. | |
|
Description |
The RMI compiler detected a problem using the undocumented and unsupported Oneway feature. |
Action |
Do not use Oneway until it is supported. | |
115 |
Oneway interfaces must not contain methods that return values. | |
|
Description |
The RMI compiler detected a problem using the undocumented and unsupported Oneway feature. |
Action |
Do not use Oneway until it is supported. | |
116 |
Async methods must return void or a valid async type. | |
|
Description |
The RMI compiler detected a problem using the undocumented and unsupported Oneway feature. |
Action |
Do not use Oneway until it is supported. | |
117 |
val is a remote class but remote interfaces could not be found. | |
|
Description |
This internal error should never occur in a properly configured system. A remote class was encountered that has no remote interfaces. |
Action |
Run the RMI compiler on this class and resolve the problems there. | |
118 |
INFO: Starting up virtualName with arguments | |
|
Description |
Indicates that an RMI startup class is being started based on a properties file that is compatible with the WebLogic Server product. |
Action |
None. | |
119 |
ERROR: Problem starting up virtualName | |
|
Description |
An attempt failed to start an RMI startup class based on a properties file that is compatible with the WebLogic Server product. |
Action |
Depends on the failure. | |
120 |
RemoteException occurred in server | |
|
Description |
A ServerException wraps a RemoteException to distinguish it from exceptions that might have occurred on the client. |
Action |
Depends on the nested exception. | |
See Also |
http://java.sun.com/products//jdk/1.2/docs/guide/rmi/spec/rmi-exceptions.doc4.html | |
121 |
ERROR: Failed to open RM | |
|
Description |
An attempt to call |
Action |
Check the resource manager vendor's trace file for additional
information, if any. If applicable, correct any resource manager problems.
Make sure that the | |
122 |
ERROR: Cannot enlist resources | |
|
Description |
An attempt to enlist the XA resources by the WLE infrastructure failed. |
Action |
Check the resource manager vendor's trace file for additional
information, if any. If applicable, correct any resource manager problems.
Make sure that the | |
123 |
ERROR: Cannot delist resources | |
|
Description |
An attempt to delist the XA resources by WLE infrastructure failed. |
Action |
Check the resource manager vendor's trace file for additional
information, if any. If applicable, correct any resource manager problems.
Make sure that the |