|
Problem(Abstract) |
Your deployment manager servant region failed to start
after a synchronization or any restart of the deployment manager with the
following error printed to the joblog:
Trace: 2005/03/01 09:27:47.128 01 t=AF9228 c=UNK key=P8 (0000000A)
Description: Log Boss/390 Error
from filename: ./bbolrt.cpp
at line: 1746
error message: BBOO0021E Assertion failed: '!(env == NULL)', file
./bbolrt.cpp |
|
|
|
Cause |
The above error often indicates a failure to start the JVM
in a region (this same error could surface in either a controller region
or servant region). In this case, You could see the servant.jvm.options
file had an error in it which was caused this problem. You can manually
correct the error, however, after each synchronization or restart, the
error would reappear in the servant.jvm.options and you would have to
correct the error again. |
|
|
Resolving the
problem |
The deployment manager server.xml had an error contained
in the processDefinitions tag for the servant JVM. It was determined that
this error was inserted inadvertantly after a manual edit of the
server.xml.
When a synchronization happens, or when the deployment manager is
restarted, entries in server.xml are propogated to the native
configuration files (most notably, the servant.jvm.options,
controller.jvm.options, and was.env). The servant.jvm.options file
is written directly from values contained in the server.xml. If the
server.xml contains any errors, those would be propogated to the
servant.jvm.options. Once the error in the server.xml file was repaired
and the system was synchronized, the problem was resolved. |
|
|
|
|
|
|