Forum Discussion
NimbostratusSRVE0255E: A WebGroup/Virtual Host to handle /ktnb has not been defined
dear all
i had Pool KTNB with 4 member : 192.168.85.139:9081, 192.168.85.139:9082, 192.168.85.140:9081, 192.168.85.140:9082 run IBM Websphere 7. I had created HTTP Virtual Server KTNB 10.64.80.73 with non irule. Before using F5, you can access service over link http://10.64.80.54/ktnb. After config F5, I access http://10.64.80.73/ktnb but error message display: SRVE0255E: A WebGroup/Virtual Host to handle / has not been defined.
SRVE0255E: A WebGroup/Virtual Host to handle 10.64.80.73:9081 has not been defined.
IBM WebSphere Application Server
How to fix problem ?
Best Regards
8 Replies
Hi!
The error message indicates that there is no listener matching 10.64.80.73:9081.
Why is the virtual host (web sphere?) located on the same network as the VIP's?
Has there been any redirect in between? Try creating a new HTTP profile, set Redirect Rewrite to "All" and assign the profile to the VIP on the F5.
/Patrik
vhv84_96225Dear Patrik
My's Big-ip-01 self IP 10.64.80.70 and Big-ip-02 self IP 10.64.80.71,with float IP's 10.64.80.69. I want request System engineer config listener on KTNB App servers. What is IP and port service of Listener should be config on KTNB App Servers?
P/s I tried create HTTP profile and set Redirect Rewrite to "all" and assign to VIP on F5 but it is't working.
Thank you so much
- Sorry to hear that it's not working for you. I have no idea in terms of your application servers. My knowledge of Web sphere is very limited. :) You say these are your pool members? 192.168.85.139:9081 192.168.85.139:9082 192.168.85.140:9081 192.168.85.140:9082 Your VS on the F5 is: 10.64.80.73 But what is 10.64.80.54? Have you done any investigations with your browser to look for any redirects? Ie with Chrome developer tools. /Patrik
- vhv84_96225
Dear Patrick
Before using F5, my customer had accessed KTNB services with http://10.64.80.54/ktnb. I want replace web service 10.64.80.54 with VIP 10.64.80.73.
What redirect information do you want using Chrome deverloper tools ? and this is capture with 10.64.80.73/ktnb
Best regards
Seems like you're no longer redirected to http://10.64.80.54:9081? I think the problem here is that the application is still configured as a cluster, that is it will only accept requests on 10.64.80.54.
My advice would be to configure each of the servers to listen to the member config (ip+port): 192.168.85.139:9081 192.168.85.139:9082 192.168.85.140:9081 192.168.85.140:9082
If you don't the application will most likely always attempt to redirect traffic to 10.64.80.54. I bet if you browse http://192.168.85.140:9081 it would redirect you to 10.64.80.54, right?
/Patrik
- vhv84_96225
dear Patrick
I send topology help you clear issue,
Hi!
Are you still running the edge server (I guess this is a floating IP?)? My knowledge of Web logic is very limited but the little I remember was that it's a bit tricky to configure (at least it was in 2008 when I last encountered it).
Have you checked the deployment guides: https://f5.com/solutions/deployment-guides
There is one for v11.2 and Web sphere 8: http://www.f5.com/pdf/deployment-guides/ibm-websphere-8-dg.pdf
I read a bit of it and it looks pretty good. From what you described you want to follow scenario 2: Configuring the BIG-IP LTM for WebSphere 8 Web Tier.
Please note that you might need to remove the redundancy feature (the edge) of the WL cluster before being able to use the BigIP for load balancing.
/Patrik
My pleasure mate!
