6.0 jsp deploy

Question

I can't get a jsp to be served up from a managed server. It works from the
          admin server however.
          I created a new domain (FooDomain) and ran an admin server with
          a jsp copied into the default web app dir:
          C:\bea\wlserver6.0\config\FooDomain\applications\DefaultWebApp_fooAdminServe
          r
          I can bring this jsp up in the browser AND when I update the
          jsp it redeploys just fine.
          Then I do the same the thing with a managed server, putting the
          jsp in:
          C:\bea\wlserver6.0\config\FooDomain\applications\DefaultWebApp_fooManServer1
          This does not work at all. I can't see the jsp and I get the
          following error from the dos screen running the FooManServer:
          <Jan 7, 2001 11:24:38 PM EST> <Error> <HTTP> <HttpServer(4899834,null
          default ct
          x,fooManServer1) found no context for "GET /hello.jsp?name=bike HTTP/1.1".
          This
          should not happen unless the default context failed to deploy.>
          Right after the managed server boots it gives me this error:
          <Jan 7, 2001 11:40:30 PM EST> <Error> <J2EE> <Error deploying application
          Defaul
          tWebApp_fooManServer1: error retrieving component [Caching Stub]Proxy for
          FooDom
          ain:Name=DefaultWebApp_fooManServer1,Location=fooManServer1,Type=WebAppCompo
          nent
          Config,ApplicationConfig=DefaultWebApp_fooManServer1>
          I get a 400 error on the browser! Not a 404!
          Any ideas on what is going on here?
          

Answer 1

It looks like the default web app is not being loaded on your managed
          server. Two things to check are
          1. that DefaultWebApp_fooManServer1 is targeted to your managed server
          2. that it is deployed.
          I think that this is something we should do automatically for the default
          web app, but currently, we don't so its possible to have the system
          configured such that the default app is not acutally loaded for a particular
          server.
          mark
          Mike Sprague wrote:
          > I can't get a jsp to be served up from a managed server. It works from the
          > admin server however.
          >
          > I created a new domain (FooDomain) and ran an admin server with
          > a jsp copied into the default web app dir:
          >
          > C:\bea\wlserver6.0\config\FooDomain\applications\DefaultWebApp_fooAdminServe
          > r
          >
          > I can bring this jsp up in the browser AND when I update the
          > jsp it redeploys just fine.
          >
          > Then I do the same the thing with a managed server, putting the
          > jsp in:
          >
          > C:\bea\wlserver6.0\config\FooDomain\applications\DefaultWebApp_fooManServer1
          >
          > This does not work at all. I can't see the jsp and I get the
          > following error from the dos screen running the FooManServer:
          >
          > <Jan 7, 2001 11:24:38 PM EST> <Error> <HTTP> <HttpServer(4899834,null
          > default ct
          > x,fooManServer1) found no context for "GET /hello.jsp?name=bike HTTP/1.1".
          > This
          > should not happen unless the default context failed to deploy.>
          >
          > Right after the managed server boots it gives me this error:
          > <Jan 7, 2001 11:40:30 PM EST> <Error> <J2EE> <Error deploying application
          > Defaul
          > tWebApp_fooManServer1: error retrieving component [Caching Stub]Proxy for
          > FooDom
          > ain:Name=DefaultWebApp_fooManServer1,Location=fooManServer1,Type=WebAppCompo
          > nent
          > Config,ApplicationConfig=DefaultWebApp_fooManServer1>
          >
          > I get a 400 error on the browser! Not a 404!
          >
          > Any ideas on what is going on here?