WSVR

WSVR0603E: ComponentMetaDataAccessor beginContext method received a NULL ComponentMetaData.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .

WSVR0623W: Unexpected exception occurred: "{0}". The com.ibm.websphere.threadpool.clearThreadLocal property has been set and will be applied to the {0} thread pool. This option is deprecated.

Explanation

The com.ibm.websphere.threadpool.clearThreadLocal property is still used in this release, but will be removed in a future release.

Action

Remove the com.ibm.websphere.threadpool.clearThreadLocal property from the Java Virtual Machine (JVM) properties.

WSVR0629I: The request buffer for thread pool "{0}" has reached its capacity.

Explanation

The queue of pending work requests on the specified thread pool has reached its limit, which could potentially lead to performance issues.

Action

No immediate action is required; however, to prevent the situation in the future, the thread pool's request buffer size may need to be increased.

WSVR0630I: Growable thread pool "{0}" has been expanded beyond its initially-defined maximum capacity. The pool size is currently "{1}".

Explanation

The specified thread pool has reached its predefined maximum size and will be expanded.

Action

No immediate action is required; however, the pool will continue to grow as long as work requests outpace the current number of available threads.

WSVR8000E: The lookup of the resource with JNDI name {0} did not complete successfully.

Explanation

The resource that was requested could not be returned due to errors during its resolution.

Action

Contact IBM support.