A WebGroup Virtual Host to Handle Has Not Been Defined : IBM WebSphere Portal Server

By -

While creating an IBM WebSphere Portal Cluster and federating an additional node in that generally and mostly when you are migrating from an older version specifically, you might encounter this problem. This is because the default host port for the node2 might not be added in the Virtual hosts properly. By adding following Host Alias you can get rid of this problem.


com.ibm.ws.webcontainer.util.VirtualHostContextRootMapper map SRVE0316W: Request matches the context root [/SpringMVC/*] under the virtual host alias of [node02:9080].
com.ibm.ws.webcontainer.util.VirtualHostContextRootMapper map SRVE0317W: You may need to add a new virtual host alias of *:<your port> to the same virtual host that [node02:9080] is under.
webcontainer  E com.ibm.ws.webcontainer.WebContainer handleRequest SRVE0255E: A WebGroup/Virtual Host to handle /SpringMVC/new_car.html has not been defined.


From DMGR Go here: (Or Admin console if you have standalone installation)
Virtual Hosts > default_host > Host Aliases
Add a new entry */<node2 port> (In my case default host port: You can check ports from Websphere Application Servers tab by going inside server).
Restart node 2 / <your application server>.=

This resolved the issue.