HI there,

i am getting below error in the Browser after installing 219 version of VoiceBiometricsService snap-in. I uninstalled all the versions and still browser gives same errror. Breeze node restart has no effect either.

SRVE0255E: A WebGroup/Virtual Host to handle /VoiceBiometricsService-1.0.0.0.218/ has not been defined.

Only when i install same version of VoiceBiometricsService snap-in, the error goes away.

I have seen this issue before as well. but not sure, how to fix this one.

Thanks,
Rahul

your post lacks clarity. what do you mean "Only when i install same version of VoiceBiometricsService snap-in" same version as what?
Where did you find information indicating you can mix versions?

1. I installed my custom made Voice Biometrics snap-in on BREEZE. It worked. Version was 1.0.0.0.218.
2. I made changed in the code and created snap-in 1.0.0.0.219.
3. I uninstalled 218 snap-in and then Installed snap-in 219. Now, when accessing snap-in web UI page, I have this error mentioned.
4. Now, I deleted 218 version snap-in from SMGR. I rebuilt new snap-in with code changes but gave it number 218 again.
5. Installed this 218 snap-in and it starts working again.

So bottom line, any snap-in with other than 218, i have same error.

Hope this helps.

Google search mentioned this:

Looks like you are accessing your store either via http server or you have changed default web container port. Go to admin console Environment > Virtual hosts > default_host (or host that is mapped to your module if different) > Host aliases. Add new alias *:80. Restart the server.

And indeed i am using port 80.

But i don't know, how to access admin console of websphere. I have seen my ex-colleagues but i can't quite remember how they did it.

Thanks,
Rahul

I could enable was access from command line by using "was set console on" command.

The error message description that i have is:

A WebGroup/Virtual Host to handle <host>:9080 has not been defined.

On the IBM cosole, i saw that there is already *:9080 entry under the virtual host. So not sure what is wrong here.

Funny thing is, even if there is no Voice Biometrics snap-in installed, still the web URL can be hit and gives the same error. Hence, i am guessing something is cached in the Websphere configuration. I did restart the BREEZE node but problem perisists.

Only way i can continue my work right now is to by uninstalling and deleting existing 218 snap-in and installing new snap-in with code changes but still keeping 218 number.

Hi Rahul, can you send a screen shot of the webpage when you get that error. Or just the URL that you are using. I found one resolution was that if you are using http://127.0.0.1/Services/SnapInName to actually put a slash at the end of the URL like this http://127.0.0.1/Services/SnapInName/

HI Craig,

I have attached the screen shot. I have installed 219 snap-in and i am getting this error in the Browser.

I tried with and without / in the end and i have same issue. It is still stuck on error with 218 snap-in.

Only one thing I would like to say is, I started having this issue since i enabled the Breeze Cluster to accept HTTP connections. I unchecked the flag on BREEZE configuration (Only allow secure web communications) and then re-started the cluster. I could se port 80 on my snap-in but then started seeing this issue.

It sounds like you have verified the settings in the console, but just wanted to double check if you had seen this and verified

https://www.ibm.com/support/pages/how-diagnose-error-srve0255e-webgroupvirtual-host-handle-0-has-not-been-defined

Have you had a look at the SystemOut.log file to make sure everything is starting up successfully?

Yes, i have checked and verified this page before. And my setting is correct. No error can be seen in SystemOut.log as well

The cache is most likely in your browser or the nginx config file, and not WebSphere.

When your snap-in VoiceBiometricsService got deployed on Breeze node, http_VoiceBiometricsService_80.conf and https_VoiceBiometricsService_443.conf get created under /etc/nginx/ce_conf.d/. These two file include a line that will redirect http/https request containing “services/VoiceBiometricsService” to “services/VoiceBiometricsService-” where your snap-in is actually provide REST service.

Uninstall version 218 and install version 219 via SMGR should update the two config files with the new version for redirection. Given the fact that you got the same error even when your snap-in is not install at all let me believe that the cach is in your browser. You can run traceSM on Breeze node to see what is coming in on the REST request from the browser. It’s likely that you’ll see “services/VoiceBiometricsService-1.0.0.0.218” in the URL even when you actually have version 219 installed. To solve this, you’ll need to clear out the cache on your browser.