OSE Plugin Error Messages

Technote (FAQ)
Problem
What does this error message for the OSE Plugin mean?
Solution
Overview: The OSE Plugin is a set of two utilities provided in code libraries. One set of utilities is loaded under an HTTP Server process. OSE Plugin functions are invoked by the HTTP Server on a per request basis. Another set of OSE Plugin Utilities is loaded under the JVM of a WebSphere AppServer.

For the set of OSE Plugin utilities loaded by HTTP Servers, trace and error messages are printed to a log file most commonly located under \WebSphere\AppServer\logs directory. The filename for the log is in the format trace.log.<http-server>.<date-time-stamp>.

For the set of OSE Plugin utilites that are loaded under the JVM of a AppServer the trace and error information is produced in a file with the format native.log.was-oop.<date-time-stamp>

Some error codes listed in both trace files are produced by the OSE functions themselves. Other error codes are generated from the operating system's network protocol such as TCP/IP. OSE defined error codes are listed below. TCP/IP or Domain Named pipes error codes can be found in OS documentation provided by the vendor.

OSE Error Codes
0 Success - not really an error.
1 OSE failure - generic error code used when there is no specific information.
2,3 Internal Error
8 Temporary failure, try again later. ( usually related to connection attempts )
9 Not found. (vhost, uri, queue, etc... Not found )
10 Client error. Client/browser closed connection prior to HTTP Reponse delivery.

OSE Initialization Messages:

Message: Error initializing cache callbacks for [xxxxx] from [xxxxx]: Error [OS-ERR]
Cause: Failed to locate a function pointer within a dll.Possibly the dll is bad.Resolution: Transfer the dll in binary. Ensure that the dll is correct.

Message: Error [OS-ERR] loading cache library [XXXX]: [XXXXX]
Cause: Failed to load the cache library. Possibly missing the dll.
Resolution: Resolve the location of the dll.

Message: Initialization Failed: No connection data pointer provided.
Initialization Failed: No initialization data pointer provided.
Cause: Webserver plugin didn’t provide required data.
Resolution: Rare - possibly caused by low memory,
or plugin/webserver version mismatch.

Message: Initialization Failed: No bootstrap properties provided.
Cause: Bootstap.properties file not loaded on plugin initialization.
Resolution: Configuration ( looking in the wrong place for the file), or out of memory.

Message: Initialization Failed: OSE Version mismatch.
Cause: Mixing and matching different versions of the plugin libraries.
Resolution: Make sure that fixpacks are installed correctly.
In an OSE Remote configuration ensure fixpacks are applied to both
HTTP Sever and WAS machines.
During Fixpack installations ensure that ALL processes are shutdown.
If HTTP Server processes have libraries loaded then the install cannot
overwrite the binaries.

Message: ose_init : Init error [ose error code] in sysmgmt_create
Cause: Possibly out of memory.
Resolution: Check messages prior to this one for details of the failure.

Message: ose_init : Cannot get bootstrap.properties
Cause: Could not load bootstrap.properties
Resolution: Could be missing/locked file, a rights problem,
or a web server configuration problem.

Message: ose_init : sysmgmt_init failed with [ose error code]
Cause: Incidental message caused by other errors.
Resolution: Look at prior messages to determine cause.

Message: ose_init : Init error [OS-ERR] in security_init
Cause: Incidental message caused by other errors.
Resolution: Look at prior messages to determine cause.

Message: ose_init : Failed to initialize
Cause: Failure while initializing/loading the OSE system.
Resolution: Look at prior messages to determine cause.

Message: ose_get_instance : malloc failed
Cause: Out of memory.
Resolution: Check memory utilization on the machine.


OSE Request Handling Errors

Message: Invalid service request: No Connection data pointer provided.
Invalid Service request: No plugin private data pointer provided.
Invalid Service request: No Service data provider provided.
Invalid Service request: No HTTP method specified.
Invalid Service request: No request URI specified.
Invalid Service request: No Read callback provided.
Invalid Service request: No Alias Translation callback provided.
Invalid Service request: No MIME Translation callback provided.
Invalid Service request: No Write callback provided.
Invalid Service request: No prepare_for_write callback provided.
Invalid Service request: No send error callback provided.
Cause: An Internal OSE structure is not initalized properly for current request.
Very unlikely
Resolution: Different versions of the plugin libraries were mixed together or memory
corrupted..

Message: sec_is_request_protected returned [ose error code]
Cause: Error while checking authorization on a resource external to WAS.
Resolution: Prior messages have details of failure.

Message: ws_ose_run_servlet : Failed [OS-ERR]
Cause: Could not locate appserver that would handle the URI.
Resolution: Refer to prior error messages for more troubleshooting information. This is usually only seen for configuration problems.

Message: Invalid data passed to ose_destroy method.
Cause: Unlikely, probably only possible with an out of memory condition.
Resolution:

Location: commonserv.c
Message: cond_router_refresh: Router refresh has failed, no further attempts
Cause: Tried to open the properties files for rereading 10 times, failed in all attempts.
Resolution: Check the temp/properties files, be sure rights are correct, and no other
process has the properties files locked so they can’t be read.

Message: refresh_router : Init error [ose error code] in router_init
Cause: Missing/corrupted/locked properties files.
Resolution: Refer to prior messages for more details.

Message: can't alloc security
Cause: Out of memory.
Resolution:

Message: sec_is_request_protected : Failed to locate a rule for [rule] and vhost [vhost]
sec_protect : Failed to locate a rule for [rule] and vhost [vhost]
Cause: There was no queue that matched the URI and vhost combination.
Resolution: Possible configuration problem - also possible after a configuration change
during the time it takes the new properties files to be generated
and read back in.

Message: error from ose_run_servlet: [OS-ERR]
Cause: Incidental message that occurs when a request can’t be sent to an appserver.
Resolution: Messages prior to this one should contain details of the error.

Message: router_init : NULL input
Cause: Unlikely, could be caused by an out of memory condition.
Resolution:

Message: router_init : Failed to allocate a router object
Cause: Out of memory.
Resolution:

Message: router_init : Failed to initialize the router object
Cause: Out of memory.
Resolution:

Message: router_run_servlet : Failed no default server group found
Cause: No queues defined in the queues.properties file.
Resolution: A configuration problem, caused by mistakes in hand editing property files.
For WAS to operate, there must be at least one queue defined to handle
requests

Message: router_service : Invalid queue name
Cause: A queue was referenced in rules.properties that wasn’t in the
queues.properties.
Resolution: This is a configuration issue - there should not be references to nonexistent
queues unless the properties files were hand edited, or there was a problem
with the plugin config file regeneration.

Message: router_service : Failed [ose error code]
Cause: Could not determine where to send the current web request.
Resolution: This is an incidental message, caused by a failure somewhere else. Messages
prior to this one will narrow down where the failure is. In most cases, this is
caused by a missing vhost or a request for a URI on a vhost that doesn’t
handle that URI.

Message: find_rule: Error - NULL input
Cause: Problem reading the properties files on the fly.
Resolution: Check for existence of properties files. Ensure orphaned processes do not have
property files locked, verify properties files are not corrupted.

Message: ws_rule_find_queue: Error - NULL input
Cause: Problem reading the properties files on the fly.
Resolution: Check for existence of properties files. Ensure orphaned processes do not have
property files locked, verify properties files are not corrupted.

Message: ws_rule_find_sec: Error - NULL input
Cause: Problem reading the properties files on the fly.
Resolution: Check for existence of properties files. Ensure orphaned processes do not have
property files locked, verify properties files are not corrupted.

Message: ws_create_rule_base: Error - NULL input
Cause: Problem reading the properties files on the fly.
Resolution: Check for existence of properties files. Ensure orphaned processes do not have
property files locked, verify properties files are not corrupted.

Message: ws_destroy_rule_base : Error - NULL input
Cause: Out of Memory condition or a problem rereading properties files during reload.
Resolution:

Message: ws_create_vhost_base : NULL input
Cause: Out of memory
Resolution:

Message: ws_create_vhost_base : Can not make properties out of the vhosts file [file]
Cause: Error while reading/parsing one of the properties files.
Resolution: Verify properties file exists, that it’s readable and not corrupted. Messages
prior to this message can give more information for troubleshooting the problem.

Message: ws_create_vhost_base : Error allocating memory
Cause: Out of memory
Resolution:

Message: ws_destroy_vhost_base : NULL input
Cause: Unlikely, possibly caused by an out of memory condition or a previous problem
reading the properties files.
Resolution: Check for messages prior to this one to see if a problem occurred while trying
to read the properties files. Verify properties files exist, that they are readable
and not corrupted.

Message: ws_vhost_find : NULL input
Cause: Debugging message, unlikely except when out of memory.
Resolution:

Message: ws_list_vhost_base : NULL input
Cause: Debugging message, unlikely except when out of memory.
Resolution:

Message: sysmgmt_init : Error in parameters
Cause: Debugging message, can be caused by initialization problems that occur before
it and out of memory conditions.
Resolution: Check memory, and check for messages prior to this one in the log.

Message: sysmgmt_init : Failed in properties creation from [filename]
Cause: Incidental message caused by failure to load properties files.
Resolution: Refer to previous messages in the logs for troubleshooting.

Message: sysmgmt_init : Failed to validate properties created from [filename]
Cause: Incidental message caused by a validation failure.
Resolution: Refer to prior error messages that describe the item that failed validation.

Message: sysmgmt_is_servlet_uri : failure in sysmgmt_queue_for_uri rc=[ose error code]
Cause: A problem occurred while trying to find the queue to service the current request.
Resolution: Look up the ose error code - if it doesn’t help, messages prior to this one will
help narrow things down. Is usually caused by requests for vhosts that aren’t
defined in WebSphere, or similar configuration problems.

Message: sysmgmt_destroy : Error in parameters
Cause: Not possible in the current code.
Resolution:

Message: sysmgmt_vhost_for_aliasport : Error in parameters
Cause: Can be caused by a previous error.
Resolution: Refer to previous error messages to see what caused this.

Message: sysmgmt_sec_for_uri : Error in parameters
Cause: Rare, but can be caused by malformed request headers to some of the
webservers. ( Common example: a HTTP/1.1 request that has no Host header )
Resolution: Turning on TRACE can give clues as to what piece of information is missing -
webserver error logs may also contain entries for any bad HTTP requests.

Message: sysmgmt_sec_for_uri : Error returned from ws_rule_find_sec rc=[ose error code]
Cause: This message is caused by an error while trying to find a security rule.
Resolution: Refer to previous error messages to see what triggered this.

Message: sysmgmt_queue_for_uri : Error in parameters
Cause: Rare, but can be caused by malformed request headers to some of the
webservers. ( Common example: a HTTP/1.1 request that has no Host header )
Resolution: Turning on TRACE can give clues as to what piece of information is missing -
webserver error logs may also contain entries for any bad HTTP requests.

Message: sysmgmt_queue_for_uri :
Error returned from sysmgmt_vhost_for_aliasport rc=[ose error code]
Cause: Error while trying to find a vhost for a particular host name and port number.
Resolution: If the ose error code is “Not Found” (9), then it’s very likely the configuration is
missing a vhost for that host and port number. Otherwise, refer to previous
messages for more information.

Message: sysmgmt_queue_for_uri : vhost not found for hosttemp [hostname:port]
Cause: No vhost found for the specified host name and port number/
Resolution: Add the a virtual host to the configuration for this host name.

Message: sysmgmt_queue_for_uri : Error returned from ws_rule_find_sec rc=
[ose error code]
Cause: Could not find a queue that matched the vhost and uri combination.
Resolution: Most often caused by configuration problems - turn on INFORM tracing to see
which uri and vhost combinations are failing, and check them against the
rules.properties files.

Message: sysmgmt_get_queue_properties : Error in parameters
Cause: Out of memory condition, or failure to read queues.properties file.
Resolution: Check previous messages in log for failures trying to read properties files.

Message: ws_open_domain_client_socket - CreateFile \n Error is [Win32 error code]
Cause: NT specific: Failure trying to create a local pipe connection to the appserver.
Resolution: Rare - it’s usually a resource problem, or a severely overloaded appserver.
Looking up the Win32 error code can sometimes give more information on the
error’s cause.

Message: ws_open_domain_client_socket-WaitNamedPipe return [Win32 error code] error
Cause: NT specific: An error occurred while waiting for one of the app server's named
pipes to become available to be connected to. Never seen in practice, though it
could be caused by resource problems.
Resolution: Looking up the Win32 error code might be helpful, but this is probably only going
to happen on an overloaded system.

Message: ws_open_domain_client_socket cannot create client socket after
[platform error code] attempts, last error [OS-ERR]
Cause: UNIX specific: Either the socket creation or the socket connection attempts
have failed. The first can be caused by running out of file handles for the
process - in all other cases, the appserver is probably not running.
Configuration problems can also cause this.
Resolution: Look up the platform error code. If it indicates “file not found” or “connection
refused”, then verify the appserver is up and running. If the appserver is
running, and there have been configuration changes recently, make sure the
properties files have been updated, so the plugins are trying to connect to the
address the appserver is advertising at.

Message: open_inet_client_socket port [port] sd [socket] errno [platform error number]
Cause: (OSE remote specific) Could not create a socket endpoint. The only known
cause for this is running into the per process file handle limit. In theory, low
memory could also cause this one.
Resolution: Look up the platform error code - if it indicates a file handle problem, the only
recourse on a UNIX box is to adjust your hard and soft ulimit for handles per
process for the user that the webserver runs as. On windows, there is no
documented hard limit, and the number of handles is bounded by available
resources only.


Message: ws_open_inet_client_socket - setsockopt(TCP_NODELAY) err [OS-ERR]
ws_open_inet_client_socket - setsockopt(SO_REUSEADDR) err [OS-ERR]
Cause: Never been encountered. It’s unusual for setsockopt() to fail.
Resolution:

Message: open_inet_client_socket port [port] sd [socket] failed after [x] attempts, error
[OS-ERR]

Cause: Could not connect to the appserver using an INET socket. Configuration
problems are a possibility - especially if the transport type was recently
changed. And any kind of network problem can cause this - anything from a
network outage to a misconfigured firewall.
This also occurs when the appserver is down.
Resolution: Verify you can make connections from the webserver machine to the appserver
machine, on the same port that OSE is using. Check the configuration, and
make sure that both the properties files and the admin console agree on the
host, port number and transport of the appservers.

Message: Attempting restart of clone [OS-ERR](WARN)
Cause: A clone went down prior to this message and it is now time to try the clone
again to see if it has come back up.
Resolution: This is just an informational message stating that at one point one of your
clones has been marked down and now the plugin is going to retry it to see if it
has come back up.


Message: Clone [clone id] failed at some earlier time and has now recovered (WARN)
Cause: A clone went down prior to this message and has successfully come
back up so the plugin will resume sending requests to the clone again.
Resolution: This is just an informational message stating a clone that had been marked
down is now back up and the plugin is sending requests to it again.

Message: p_clones or interface_name could not be allocated, returning [OS-ERR]
Cause: Out of memory
Resolution:

Message: Error passing service/run request ... Could not locate a clone
Cause: No clone could be found to pass the request too - all clones are marked as
being down.
Resolution: Verify appserver is up, verify connections can be made from webserver machine
to appserver machine. Also check the temp/properties files and verify the
configuration looks correct. The plugins will wait a certain amount of time
before retrying appservers that have gone down - this defaults to ten seconds,
and is configurable in the bootstrap.properties file with the
ose.failure.retry_timer parameter.

Message: Error : sei_create_se_interface NULL input
Cause: Unlikely, out of memory condition or a problem reading properties files.
Resolution: Refer to previous messages to see if any errors occurred while reading the
properties files.

Message: ERROR: In do_service_time_request, marshale_service_stub_2_m failed
ERROR: In do_service_time_request, marshale_servlet_data_2_m failed
ERROR: In do_service_time_request, maybe server_message_flush failed

Cause: All of these can be caused a loss of network connection while the plugins are
writing the details of the request over to the appserver.
Resolution: Verify the appserver didn’t go down at the time of the failure - also try to verify
there were no network problems at the time of the failure.

Message: ERROR: In do_service_time_request, enter_callback_mode failed
Cause: Error either communicating with the appserver, or writing the response out to
the client.
Resolution: Messages prior to this message will help further determine the source of the
problem.

Message: Error create_server(%s, %d, %d, %x): %d
Cause: Incidental error message logged when there was a problem advertising the
appserver.
Resolution: Refer to previous messages to see what error triggered this message.

Message: Failed to allocate server queue data internal
Cause: Out of memory
Resolution:

Message: Failed to create new server socket internal
Cause: There was a problem creating a socket/named-pipe to listen for requests on.
Resolution: This is an incidental message, information on the error will be in messages prior
to this one.

Message: Faild to allocate new server socket memory
Faild to allocate new inet server socket memory
Faild to allocate new server socket memory
Faild to allocate new domain server socket
Cause: Out of memory
Resolution:

Message: Getting new connection failed
Cause: Incidental message caused by an error while waiting for incoming connections
from the webserver plugin.
Resolution: Refer to prior messages in the logs for details on what triggered this error.

Message: For socket [socket id] and connection [connection id], Data demarshal failed
Cause: Error occurred while trying to read request data over from webserver plugin.
Resolution: Usually caused by connection loss, or early connection closes by
clients/browsers. For large groups of these errors, check web server logs to
see if the webserver went down at the time of the errors.

Message: write_inet_server_socket: [socketid], total length [len], bytes ok [# of bytes],
error [platform error ](WARN)
Cause: Error occurred while writing response back to webserver plugins.
Resolution: Caused by connection going down - in most cases, this is where clients are
closing connection before the response is finished. For large groups of these
errors, check webserver logs to see if the webserver went down around the time
the errors occurred, and also check to see if the network was down around that
time.

Message: read_inet_server_socket: %d, error len %d
Cause: The network connection went down while trying to read the request information
over from the webserver plugins.
Resolution: For large groups of these errors, check webserver logs to see if the webserver
went down around the time the errors occurred, and also check to see if the
network was down around that time.

Message: open_inet_server_socket_listener: [socket], port [port], error bind/listen
Open_unix_domain_server_socket_listener [port] name [xxx] - error bind/listen
Cause: An error occurred while trying to set up to listen for incoming connections.
Resolution: Could be caused by two appservers on the same machine trying to listen on
the same INET port, due to a configuration problem. ( each appserver must
have it’s own port, the admin console should guarantee this, so this will
probably only occur for hand edited properties files, as used in some OSE
remote setups )

Message: open_inet_server_socket_listener: [socket], port [port number] error
Open_unix_domain_server_socket_listener [socket] name - error socket
Cause: Could not create a socket to listen for incoming requests on.
Resolution: Can probably only be caused by resource problems or by running out of file
handles for the appserver process. Check the machine resources, and on
UNIXes, the hard and soft limits for per process file handles.

Message: Attempts to reopen the listen socket failed after [# of attempts] tries.
Server listen shutdown
Cause: Incidental message caused by other errors.
Resolution: Refer to prior error messages for details on why the server listen socket
couldn’t be created.

Message: Socket_based_server_loop accept error [platform error]
Cause: select() indicated there was a connection waiting to be accepted, but accept
failed.
Resolution: Can either be caused by running out of resources, a connection dropped at just
the right time ( which could be an early client close ), or on UNIX, running out of
file handles. Check platform error code for clues as to which was the cause.


Message: Socket_based_server_loop select error [platform error]
Cause: Error occurred while waiting for an incoming connection. Very rare.
Resolution: Look up the platform error code to see if it indicates what the problem was.
Unless there is a resource problem, this should be a recoverable error.

Message: create_inet_server_socket [socketid], open_socket_based error [OS-ERR]
create_inet_server_socket open_socket_listener error [OS-ERR]
Cause: Incidental error message caused by a failure to open a server socket to listen for
requests on.
Resolution: Refer to prior messages in the log for more details.


Message: Read_domain_server_socket [socket] - GetOverlappedResult1 [platform error]
Read_domain_server_socket [socket] - GetOverlappedResult2 [platform error]
Read_domain_server_socket [socket] - ReadFile [platform error]
Do_domain_server_loop - GetOverlappedResult3 [platform error]
Do_domain_server_loop - WaitForMultipleObjects [platform error]
Write_domain_server_socket - GetOverlappedResult [platform error]
Write_domain_server_socket error [platform error]
Cause: Error while blocking on a read. Caused by the connection going down - which
in most cases is due to an early client close.
Resolution: None, unless there is reason to believe the error was not caused by an early
client close. Examining the platform error code may provide clues as to the
cause if this is the case.

Message: Read_domain_server_socket [platform error] - connect_named_pipe error
Cause: Incidental message caused by an error trying to accept a connection to a
named pipe.
Resolution: Possibly caused by a closed connection - if groups of the error occur, check
and see if the web server went down in this time frame. The platform error code
may help determine the exact cause.

Message: Generate_new_domain_read_list - connect_named_pipe [pipe name] error
[OS-ERR]
Cause: Incidental error message, caused by failure while trying to accept a new
connection.
Resolution: Refer to prior messages for details on the error.

Message: Create_domain_server_socket failed open_socket_based %d name %s
Cause: Incidental message caused by an error trying to open a listener socket for local
pipes on UNIX systems.
Resolution: Refer to prior messages for details on the error.

Message: nativeRead: Error: function pointer for read callback function is null
nativeWrite: Error: function pointer for write callback function is null
Cause: This shouldn’t be possible, barring problems outside of the plugin code.
Resolution:

Message: nativePrepareForWrite: malloc failed.
Cause: Out of memory
Resolution:


Message: Error : in cfg_get_file_in_tmp_dir, property [property_name] is missing
Cause: ose.temp.dir property is missing from bootstrap.properties file
Resolution:

Message: cfg_get_native_log_level : [level string] is not available
Cause: The level specified isn’t a valid log level.
Resolution: Modify the log level setting to an accepted level.

Message: cfg_get_native_log_level : Error parsing attribute %s
Cause: An invalid log level is specified and isn’t recognized.
Resolution: Modify the log level setting to an accepted level.

Message: Error : in function cfg_get_name_of_run_servlet_queue, can not locate
[queue-name]
Cause: Could not locate a queue name. An invalid queue name was passed into the
function.
Resolution: The internal OSE configuration has been corrupted and contains the names of
queues that don’t exist. Restart the webserver.

Message: Error : in function cfg_get_names_of_se_inters, can not locate [queue name]
Cause: Could not locate a queue name. An invalid queue name was passed into the
function.
Resolution: The internal OSE configuration has been corrupted and contains the names of
queues that don’t exist. Restart the webserver.

Message: Error : in function cfg_get_names_of_se_inters, memory allocation error or
empty property
Cause: Memory Allocation Failure
Resolution:

Message: Error : in function cfg_get_names_of_se_inters, memory allocation error
Cause: Memory Allocation Failure
Resolution:

Message: Error : in function cfg_get_ose_lib, can not locate [library-name]
Cause: The libpath property for OSE is NULL.
Resolution: Set the libpath to be used by OSE.

Message: Error : property [property string] is missing or have a bad value
Cause: The given property is expected and isn’t present or the value is invalid.
Resolution: Add the given property or set the value so that it is valid.


Message: Error [OSE-ERR] loading transport layer library [library-name]
Cause: Incorrect path to the transport library or the file does not exist.
Resolution: Resolve the location of the library or change the location in the property file
where OSE is attempting to load the library from.

Message: Error : in cfg_get_interface_type_by_name can not get the ose lib [libname]
Cause: The library could not be found.
Resolution: The library failed to be loaded in which case we would fail earlier so this
message is unlikely to be seen.

Message: Error loading function pointer for [function] from [libname]: Error [OS-Error]
Cause: The function pointer could not be resolved in the given library.
Resolution: The most likely cause is a corrupt dll or incompatible version of the library.

Message: Error [OS-ERR] loading ose router library [library-name]
Cause: Incorrect path to the router library or the file does not exist.
Resolution: Resolve the location of the library or change the location in the property file
where OSE is attempting to load the library.

Message: Error : in oseu_get_ose_init_func can not get the ose router lib
Cause: Failed to find the router library. Possibly the path being used is invalid or the file
does not exist.
Resolution: Resolve the location of the router library and either create the file or fix the path.

Message: Error : wrong input to oseu_create_ose_obj
Cause: Sanity check for development. Either the properties structure,
ose_connection_data structure, or the ose_init_data structure has been
corrupted.
Resolution: Unlikely to see this since if any of these parameters are NULL the error will be
caught earlier on in OSE initialization.

Message: Error : in oseu_create_ose_obj can not locate ose init method
Cause: Failed to resolve the function pointer for the OSE initialization method in the plugin
shared library.
Resolution: The library must have been corrupted or is not complete.

Message: Error : in oseu_validate_queue_props_value, cfg_get_interface_type_by_name
failed
Cause: Failed to get the type of interface used with this queue.
Resolution: Invalid setting in the queues.properties files. Unlikely to see this unless you
have been modifying the queues.properties by hand.

Message: Error : in oseu_validate_queue_props_value, creat_func failed
Cause: Failed to create the se_interface structure.
Resolution: Invalid setting in the queues properties files. Unlikely to see this unless you
have been modifying the queues.properties by hand.

Message: Error : in oseu_validate_queue_props_value, sei_verify_interface_configuration
failed
Cause: Validation of the queues properties file failed.
Resolution: Check the queues properties file to see if anything isn’t well formed in there.

Message: Error locking file. Error is [OS-Error]
Cause: WIN32 only. Unable to unlock the access file.
Resolution: The file doesn’t exist or doesn’t have the correct permissions.

Message: Error : in oseu_locate_clone_id_in_session_state, bad input
Cause: Sanity check on incoming parameters. Either the ose_server_stub structure,
the session_id_name, or the session_id itself is NULL.
Resolution: Unlikely to be seen since it will be only be called if the plugin is trying to do
session affinity and has these components.

Message: create_props_from_dst: malloc failure
Cause: Memory Allocation Failure
Resolution:

Message: destroy_properties : Error - NULL input
Cause: . The properties structure is NULL.
Resolution: Possibly a problem with the property file.

Message: get_properties : Error - NULL input
Cause: The properties structure is NULL.
Resolution: Possibly a problem with the property file.

Message: list_properties : Error - NULL input
Cause: The properties structure is NULL.
Resolution: Possibly a problem with the property file.

Message: set_property : Error - NULL input
Cause: Either the properties structure is NULL, the name of the property, or the value.
Resolution: Possibly a problem with the property file but unlikely this will ever be seen.

Message: get_property : Error - NULL input
Cause: Either the properties structure is NULL or the name of the property to get.
Resolution: Possibly a problem with the property file but unlikely this will ever be seen.

Message: load_properties : Couldn't find property file [filename] (WARN)
Cause: The property file specified could not be found.
Resolution: Create the property file in that location or modify the path to the correct location
of the property file.

Message: Failed to load bootstrap properties file: [filename]
Cause: The bootstrap.properties file could not be opened or failed to get parsed
correctly.
Resolution: Ensure that the path to the bootstrap.properties file is correct, the file exists,
and that it is well formed.

Message: Failed to validate bootstrap properties file: [filename]
Cause: The validation of the bootstrap.properties file failed.
Resolution: Other log messages will help you figure out which part of the validation failed.

Message: ThreadID Error in ns_read_cb
Cause: WIN32 only. The thread OSE is currently running in isn’t a NSAPI thread.
Resolution: Somehow the OSE processing was switched onto a thread that isn’t running in
Netscape.

Message: ThreadID Error in ns_prepare_for_write_cb
Cause: WIN32 only. The thread OSE is currently running in isn’t a NSAPI thread.
Resolution: Somehow the OSE processing was switched onto a thread that isn’t running in
Netscape.

Message: OSE specification violation!!! ns_prepare_for_write() was already called
Cause: It is not acceptable to attempt to write the headers
out more than once.
Resolution: Only seen when a bug has been introduced to the code in which case support
will need to be contacted.

Message: Exiling ns_prepare_for_write_cb with failure
Cause: Some error occurred write the response to the browser.
Resolution: None really, this most likely is just a result of the user hitting the stop button on
the browser.

Message: ThreadID Error in ns_write_cb
Cause: WIN32 only. The thread OSE is currently running in isn’t a NSAPI thread.
Resolution: Somehow the OSE processing was switched onto a thread that isn’t running in
Netscape.

Message: OSE specification violation!!! prepare_for_write() was not called before write()
Cause: It is not acceptable to attempt to write the response body before the headers
have been written.
Resolution: Only seen when a bug has been introduced to the code in which case support
will need to be contacted.

Message: Exiting ns_write_cb with failure
Cause: The attempt to write the response back to the browser failed.
Resolution: This isn’t really an error but is logged as such. This can be issued for a variety
of reasons including the user hitting the stop button on the browser.

Message: net_write error
Cause: The attempt to write the response back to the browser failed.
Resolution: This isn’t really an error but is logged as such. This can be issued for a variety
of reasons including the user hitting the stop button on the browser.

Message: ThreadID Error in ns_send_error_cb
Cause: WIN32 only. The thread OSE is currently running in isn’t a NSAPI thread.
Resolution: Somehow the OSE processing was switched onto a thread that isn’t running in
Netscape.

Message: OSE specification violation!!! ns_send_error_cb() was called after
prepare_for_write()
Cause: It is not acceptable to call this function after the headers have already been
written to the client.
Resolution: Only seen when a bug has been introduced to the code in which case support
will need to be contacted.

Message: ThreadID Error in ns_alias_translation_cb
Cause: WIN32 only. The thread OSE is currently running in isn’t a NSAPI thread.
Resolution: Somehow the OSE processing was switched onto a thread that isn’t running in
Netscape.

Message: Length error in ns_alias_translation_cb
Cause: The buffer to copy the translated path into is too small for the length of the path.
Resolution: Shorten the path so that it can fit in the buffer.

Message: ThreadID Error in ns_mime_translation_cb
Cause: WIN32 only. The thread OSE is currently running in isn’t a NSAPI thread.
Resolution: Somehow the OSE processing was switched onto a thread that isn’t running in
Netscape.

Message: Error : in validate_dir, [dir_name] is not a directory
Cause: The given directory name isn’t really a directory.
Resolution: Modify the value of the property so that it points to a directory.

Message: Error : wrong input to validate_java_lib_path
Cause: Put in mainly as a sanity check for development. Either the interface_name
isn’t given or the properties structure is NULL.
Resolution: If this is a problem it will be detected earlier on during OSE initialization.

Message: Error : in validate_java_lib_path no java libpath given in [path-name].
Cause: The libpath for java was not set.
Resolution: Set the libpath for java.

Message: Error : wrong input to validate_java_path
Cause: Put in mainly as a sanity check for development. Either the interface_name
isn’t given or the properties structure is NULL.
Resolution: If this is a problem it will be detected earlier on during OSE initialization.

Message: validate_java_path : Can not get [path]
Cause: The path to java could not be determined.
Resolution: Set the path to the Java executable.

Message: Error : in validate_temp_dir, property [property-name] is missing
Cause: The given property is missing and is expected.
Resolution: Add the property that is missing.

Message: Error : in validate_ose_lib_dir, property [property] is missing
Cause: The given property is missing and is expected.
Resolution: Add the property that is missing.

Message: Error : in validate_server_dirs, property [property] is missing
Cause: The given property is missing and is expected.
Resolution: Add the property that is missing.

Message: Error : in validate_server_dirs, can not generate directory from
[directive]& [directive]
Cause: Failed to build a directory path from a couple of variables.
Resolution: The path was to long to fit in the buffer. Shorten the path so that it will be able
to fit in the buffer.

Message: Error : in validate_conf_prop_values, can not validate properties for the admin
queue.
Cause: Validation of the queues.properties failed. The format of the file was invalid.
Resolution: Fix the syntax in the queues file.

Message: Error : in [functionname], can not get the name of the common services DLL.
Cause: Unable to determine the name of the common services dll, most likely because
the property designating the name is missing.
Resolution: Add the property specifying the location of the common services dll.

Message: Error : in validate_conf_prop_values, common services DLL [dllname] is not
readable or not a file.
Cause: The file specified to use for the common library either doesn’t exist or has
incorrect permissions.
Resolution: Fix the path to the location of the common library or change the permissions so
that it is readable.

Message: bootstrap properties failed validation test
Cause: Something went wrong during the validation of the bootstrap.properties file.
Resolution: Look at the previous error messages and fix those problems.

Message: Missing required property [property name]
Cause: The given property is not present and is required.
Resolution: Add the given property to the property file.

Message: invalid bootstrap property [bootstrap.property filename]
Cause: The specified property isn’t a valid one.
Resolution: Either delete the property or modify it so that it is acceptable.

Message: validate_java_cp_generation : cfg_get_use_sys_cp failed
Cause: It couldn’t be determined whether the plugin should use the system classpath or
not.
Resolution: Set whether or not the system classpath should be used.

Message: validate_java_cp_generation : java classpath is missing for interface
[interfacename]
Cause: The classpath could not be determined.
Resolution: Set the classpath to be used by the plugin.

Message: validate_java_cp_generation : cfg_get_java_cp_raw failed
Cause: The classpath could not be determined.
Resolution: Set the classpath to be used by the plugin.

Message: validate_java_cp_generation : server root is missing
Cause: The path for the server_root is not known and therefore can’t be used in
constructing the Classpath.
Resolution: Set the server.root variable in the bootstrap.properties to the location of the
server root.

Message: validate_java_cp_generation : Can not create classpath
Cause: The plugin could not generate the classpath or figure out the classpath to use.
Resolution: Set the classpath to be used by the plugin.

Message: Detected bad classpath entry: [classpath entry] (WARN)
Cause: The classpath contains either files or directories not present on the file system.
Resolution: Create the file or directories on the file system or remove the bad entries from
the Classpath.

Message: Missing property [propery-name] (WARN)
Cause: The given property isn’t present and the plugin expected it would be.
Resolution: Set the property to the value you want to use.

Message: Missing property [property-name] using default [default value](WARN)
Cause: The given property isn’t present so the default value will be used.
Resolution: Not really a problem in most cases. This is more of an informational type of
message.

Message: bootstrap property [property-name]
Cause: Something is wrong with the property or the value for the property given.
Resolution: Verify that the given property name/value are acceptable and correct.

Message: p_clones or interface_name could not be allocated, returning [xx]
Cause: Memory Allocation Failure.
Resolution:

Message: Error passing service/run request ... Could not locate a clone
Cause: All the clones are currently marked down by the plugin so none could be found
to route the request too.
Resolution: Restart the clones on the app server side.

Message: Error : sei_create_se_interface NULL input
Cause: One of the input parameters to the function was NULL
Resolution: This is an error message that was added mainly for development purposes. A
check is performed to make sure the se_interface structure and the properties
structure isn’t NULL. If either are you will see this.

Message: mediate_service_to_clone: Error [ose error code] from clone [cloneid], uri
Cause: Could not connect to clone/appserver.
Resolution: Verify appserver is up, verify connections can be made from webserver machine
to appserver machine. Messages prior to this error message can shed light on
the exact cause of the problem.

Message: mediate_service_to_clone: Return [ose error code] from clone [clone id], uri
Cause: Could not connect to clone/appserver.
Resolution: Verify appserver is up, verify connections can be made from webserver machine
to appserver machine. Messages prior to this error message can shed light on
the exact cause of the problem.












    Document Information

    Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Plug-in
    Operating system(s): Multi-Platform
    Software version: 3.5.4
    Software edition: All Editions
    Reference #: 1050313
    IBM Group: Software Group
    Modified date: 2002-03-14