ci.docker.websphere-traditional icon indicating copy to clipboard operation
ci.docker.websphere-traditional copied to clipboard

Web application context root not accessible in websphere application server docker after deploying in minikube

Open GitHub87 opened this issue 5 years ago • 1 comments

Not sure if I should create an issue here, but I am facing a problem when I am trying to deploy a websphere image in Kubernetes. I created a docker image with my application and websphere application server traditional image. When I deployed the image in minikube I am getting the below error. It seems that when I hit the url the request is reaching the container, but then I might be missing some configurations in the websphere image? Any help please.

0000008d util W com.ibm.ws.webcontainer.util.VirtualHostContextRootMapper map SRVE0316W: Request matches the context root [/pseudo/application/] under the virtual host alias of [:5061].

0000008d util W com.ibm.ws.webcontainer.util.VirtualHostContextRootMapper map SRVE0317W: You may need to add a new virtual host alias of : to the same virtual host that [:5061] is under.

0000008d WebContainer E com.ibm.ws.webcontainer.internal.WebContainer handleRequest SRVE0255E: A WebGroup/Virtual Host to handle /pseudo/application/wsdl/app.wsdl has not been defined.

GitHub87 avatar Dec 20 '19 18:12 GitHub87

Am seeing a similar issue when trying to access the admin console on port 9043 or 9060 when it is exposed as a node port in kubernetes. It looks like the issue is down to the Host header value passed in the request - it contains the port number which is the node port and not the exposed admin port from for the container and therefore there is a mismatch in the virtual hosts.

Has anyone seen this before?

stevejr avatar Jan 28 '20 19:01 stevejr