WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

Problem with Virtual Host and

  • 1.  Problem with Virtual Host and

    Posted 09/17/12 08:10 AM
    Hello

    I have deployed a WAR on Websphere Application Server ND version 7.0.0.21

    I have defined a Context Root For Web Modules :   for example  /MyContextRoot

    I have added the port "WC_defaulthost " on "environnement" -> "Virtual Host"-> "default_host"

    The application is running and accessible.

    The problem is that I have the following error message on my SystemOut.log:


    [9/17/12 11:06:50:762 GMT+00:00] 00000040 webcontainer  E com.ibm.ws.webcontainer.WebContainer handleRequest SRVE0255E: A WebGroup/Virtual Host to handle /AnotherContextRoot has not been defined.

    The error message is about another  Context Root that I haven't defined  (/AnotherContextRoot ).

    Can someone help me understand why I'm having this error message ?

    My OS is : Solaris 10

    Thank you.

    Regards,


  • 2.  Problem with Virtual Host and

    Posted 09/17/12 08:16 AM
    The problem appears every 30 secondes.


  • 3.  Problem with Virtual Host and

    Posted 09/17/12 09:14 AM
    Hi adilyos,

      Is the ContexRoot changed? that is, has it previusly /AnotherContextRoot and now /MycontextRoot?
     
      Do you have some application deployed with /AnotherContextRoot that is stopped?
     
      Do you have check your plugin (If you are using)? is regenerated and propagated? can you invoke directly to http://:>PORT>/AnotherContextRoot

      tell us if you need more support.
     
    regards


  • 4.  Problem with Virtual Host and

    Posted 09/17/12 11:16 AM
    Thank you  for your answer.

    Yes the application was installed with /AnotherContextRoot and I have changed it

    to /MycontextRoot.

    I have WAS 6.1 and WAS 7 on the same machine. /AnotherContextRoot is used for

    an application that is running on an WAS6.1 applicatioon server . So if there is a

    problem on it I should have the error message on SystemOut.log of WAS 6.1 and

    not in WAS 7 ?

    I haven't regenarated the plugin.

    So now I will Uninstall the application /MycontextRoot and install it again then

    generate a plugin and propagate it and tell you the result.

    Thank you


  • 5.  Problem with Virtual Host and

    Posted 09/17/12 11:52 AM
    Hi adilyos,

      You don't need to unnistall the application only regenerate plugin in WAS 7 and propagate it.
     
      If you had not propagated the plugin, it has the previus /AnotherContextRoot and is pointing to your WAS 7 that the reason why you are getting the error in WAS 7. Because the plugins think that the application still deployed in WAS 7 with /AnotherContextRoot if you redeploy application with new /MycontextRoot you need to regenerate the plugin and propagate it to your Web Server.


    regards,


  • 6.  Problem with Virtual Host and

    Posted 09/18/12 03:44 AM
    Hi Adilyos,

    You can do as suggested by Gabrial or try this option.

    Just replace the /MyContextroot in the plugin-cfg.xml and restart the webserver. It will also resolve the issue...

    Regards,
    Siva 


  • 7.  Problem with Virtual Host and

    Posted 09/18/12 05:31 AM
    Of course Siva,

    Although the restart of the web server normally is very quick, I normally prefer to regenerate and propagate to get a coherence in the environment.  Sometimes editing manually can cause the corruption of the plugin.

    The plugin will be refreshed when the refresh timeout established in Plugin file occurs.

    Refresh configuration interval

    "Specifies the time interval, in seconds, at which the plug-in should check the configuration file to see if updates or changes have occurred. The plug-in checks the file for any modifications that have occurred since the last time the plug-in configuration was loaded.

    In a development environment in which changes are frequent, a lower setting than the default setting of 60 seconds is preferable. In production, a higher value than the default is preferable because updates to the configuration will not occur so often. If the plug-in reload fails for some reason, a message is written to the plug-in log file and the previous configuration is used until the plug-in configuration file successfully reloads. If you are not seeing the changes you made to your plug-in configuration, check the plug-in log file for indications of the problem."


    If you have your Web Servers in HA then you can restart it without problem and without wait to refresh timeout.

    regards,


  • 8.  Problem with Virtual Host and

    Posted 09/18/12 09:21 AM
    I have unistalled the application and installed it. Now I'm not using a Web Server

    (plugin).

    I'm still having the same error message.


  • 9.  Problem with Virtual Host and

    Posted 09/18/12 09:46 AM

      Ok can you check in the web server the plugin file if you have and entry to /AnotherContextRoot?
     
      How many Web Servers do you have? you say that in the same machine you have WAS 6.1 and WAS 8.0 (I suppose each one with different Web container ports)
     
       If you are having the message every 30 seconds some client/process is invoking.

    regards,


  • 10.  Problem with Virtual Host and

    Posted 09/18/12 11:27 AM
    The application is not mapped to a webserver and the webserver is stopped. So I think the problem is far from to be due to the plugin.


  • 11.  Problem with Virtual Host and

    Posted 09/18/12 12:15 PM
    Ok if the Web Server is stopped sure, sorry had not understood that from the phrase "Now I'm not using a Web Server (plugin).".

    But someone is doing the calls to your server is you are having "SRVE0255E: A WebGroup/Virtual Host to handle /AnotherContextRoot has not been defined." because this is a Web Container error.

    another Web Server maybe? who calls/use that application? maybe can help to find the caller.