|
Problem |
When migrating Websphere Application Server 3.5 to
WebSphere Application Server 4.0.x, you might have an application server
running a servlet engine in a WebSphere Application Server 3.5 domain that
is accessing an application server running an EJB Container in a WebSphere
Application Server 4.0.x domain. If this is the case in your enterprise,
warning messages such as the following might be displayed in the client's
stderr output:
[time_stamp] thread_ID ProxySelector W Encountered an invalid proxy
selector type
[time_stamp] thread_ID ServerGroup W Server group was not found in the
configuration
information manager within the read method |
|
Solution |
These warning messages are displayed due to a context data
missmatch between WebSphere Application Server 3.5 and 4.0.x but the
context data is not used or needed in Version 3.5 and will be ignored.
There will be no adverse affect on the functioning of the system. |
|
|
|
|
|
|
|