Should not happen unless default context failed to deploy

Question

          Can somebody please throw some light on this error?
          <Mar 5, 2001 10:07:26 AM EST> <Error> <HTTP> <HttpServer5173817,null
          default ctx,POSDev01) found no context for "GET /classes/ringout_statelessSession3@/RingoutSessionBeanHomeImpl_WLStub.class
          HTTP/1.0". This should not happen unless the default context failed
          to deploy.>
          Myself and lot of other people in my team are getting this error
          when using beans in a cluster.
          I am getting this error consistently whenever I make some code
          changes in my bean class (not interface changes) and redeploy it
          and try to lookup through a stand-alone client.
          The only way I could find to overcome this problem is:
          1) edit config.xml to remove the Application element completely
          corresponding to the bean
          2) remove jar files from the applications directory
          3) re-deploy and run the client again.
          Thanks a lot
          Kiran Ganuthula
          

Answer 1

Partly it could be WLS problem also. Under any circumstances default webapp should be able
          to deploy. I have seen somebody else also reported the same problem. The current problem is
          if you delete anything from apps dir, the corresponding entry is not being deleted from config.xml
          So next time when you boot the server, it tries to deploy the webapp and eventually it fails.
          I 'm not sure if this is the situation in your case.
          In anycase somehow Targets tag is not being picking up. That's why i asked you add
          "WebServers" tag. I think we have done some major changes in SP1, to make sure that
          default webapp deploys all the times.
          If you still have problems, post it to servlet or management group, we will discuss there.
          Kumar
          Kiran G wrote:
          > I edited the config.xml ONLY after getting this error. And, it worked.
          >
          > BTW, can you please be more specific about the changes to config.xml
          > to solve the problem?
          > If possible, can you give pertinent portion(s) of config.xml, highlighting
          > the changes.
          >
          > Thanks
          > Kiran G
          >
          > Kumar Allamraju <[email protected]> wrote:
          > >
          > >
          > >It appears your "default webapp" failed to deploy.
          > >Did you messed up with the config.xml?.
          > >
          > >Add the following to your default webapp tag?
          > >
          > ><Application
          > > Deployed="true"
          > > Name="DefaultWebApp_vindev1"
          > > Path="./config/vindev1/applications"
          > > >
          > > <WebAppComponent
          > > Name="DefaultWebApp_vindev1"
          > > Targets="vindev1"
          > > WebServers="vindev1"
          > > URI="DefaultWebApp_vindev1"
          > > />
          > > </Application>
          > >
          > >
          > >Here vindev1 is my domain's name..
          > >
          > >BTW, this is not a clustering question. So you better
          > >post it to servlet newsgroup where you get much
          > >better answers..
          > >
          > >Kiran G wrote:
          > >
          > >> I forgot to give these details about the problem.
          > >> I am running this cluster using WebLogic 6.0 on a SUN
          > >sparc machine.
          > >>
          > >> The error text given in my original posting appears
          > >in the managed
          > >> weblogic server's log. The exception that the client
          > >receives while
          > >> lookup is :
          > >>
          > >> javax.naming.CommunicationException. Root exception
          > >is java.rmi.UnmarshalException:
          > >> failed to unmarshal class java.lang.Object; nested exception
          > >is:
          > >> java.lang.ClassNotFoundException: RingoutSessionBeanHomeImpl_WLStub
          > >> java.lang.ClassNotFoundException: RingoutSessionBeanHomeImpl_WLStub
          > >>
          > >> "Kiran G" <[email protected]> wrote:
          > >> >
          > >> >Can somebody please throw some light on this error?
          > >> >
          > >> ><Mar 5, 2001 10:07:26 AM EST> <Error> <HTTP> <HttpServer5173817,null
          > >> >default ctx,POSDev01) found no context for "GET /classes/ringout_statelessSession3@/RingoutSessionBeanHomeImpl_WLStub.class
          > >> >HTTP/1.0". This should not happen unless the default
          > >context
          > >> >failed
          > >> >to deploy.>
          > >> >
          > >> >Myself and lot of other people in my team are getting
          > >> >this error
          > >> >when using beans in a cluster.
          > >> >
          > >> >I am getting this error consistently whenever I make
          > >some
          > >> >code
          > >> >changes in my bean class (not interface changes) and
          > >redeploy
          > >> >it
          > >> >and try to lookup through a stand-alone client.
          > >> >
          > >> >The only way I could find to overcome this problem
          > >is:
          > >> >1) edit config.xml to remove the Application element
          > >completely
          > >> >corresponding to the bean
          > >> >2) remove jar files from the applications directory
          > >> >3) re-deploy and run the client again.
          > >> >
          > >> >Thanks a lot
          > >> >Kiran Ganuthula
          > >> >
          > >> >
          > >> >
          > >> >
          > >> >
          > >
          > >
          > ><!doctype html public "-//w3c//dtd html 4.0 transitional//en">
          > ><html>
          > >It appears your "default webapp" failed to deploy.
          > ><br>Did you messed up with the config.xml?.
          > ><p>Add the following to your default webapp tag?
          > ><p><Application
          > ><br> Deployed="true"
          > ><br> Name="DefaultWebApp_vindev1"
          > ><br> Path="./config/vindev1/applications"
          > ><br> >
          > ><br> <WebAppComponent
          > ><br> Name="DefaultWebApp_vindev1"
          > ><br> Targets="vindev1"
          > ><br> <b><font color="#CC0000">
          > >WebServers="vindev1"</font></b>
          > ><br> URI="DefaultWebApp_vindev1"
          > ><br> />
          > ><br> </Application>
          > ><br>
          > ><p>Here vindev1 is my domain's name..
          > ><br><br>
          > >BTW, this is not a clustering question. So you better
          > >post it to servlet
          > >newsgroup where you get much
          > ><br>better answers..
          > ><p>Kiran G wrote:
          > ><blockquote TYPE=CITE>I forgot to give these details about
          > >the problem.
          > ><br>I am running this cluster using WebLogic 6.0 on a
          > >SUN sparc machine.
          > ><p>The error text given in my original posting appears
          > >in the managed
          > ><br>weblogic server's log. The exception that the client
          > >receives while
          > ><br>lookup is :
          > ><p>javax.naming.CommunicationException. Root exception
          > >is java.rmi.UnmarshalException:
          > ><br>failed to unmarshal class java.lang.Object; nested
          > >exception is:
          > ><br> java.lang.ClassNotFoundException:
          > >RingoutSessionBeanHomeImpl_WLStub
          > ><br>java.lang.ClassNotFoundException: RingoutSessionBeanHomeImpl_WLStub
          > ><p>"Kiran G" <[email protected]> wrote:
          > ><br>>
          > ><br>>Can somebody please throw some light on this error?
          > ><br>>
          > ><br>><Mar 5, 2001 10:07:26 AM EST> <Error> <HTTP>
          > ><HttpServer5173817,null
          > ><br>>default ctx,POSDev01) found no context for "GET /classes/ringout_statelessSession3@/RingoutSessionBeanHomeImpl_WLStub.class
          > ><br>>HTTP/1.0". This should not happen unless the default
          > >context
          > ><br>>failed
          > ><br>>to deploy.>
          > ><br>>
          > ><br>>Myself and lot of other people in my team are getting
          > ><br>>this error
          > ><br>>when using beans in a cluster.
          > ><br>>
          > ><br>>I am getting this error consistently whenever I make
          > >some
          > ><br>>code
          > ><br>>changes in my bean class (not interface changes)
          > >and redeploy
          > ><br>>it
          > ><br>>and try to lookup through a stand-alone client.
          > ><br>>
          > ><br>>The only way I could find to overcome this problem
          > >is:
          > ><br>>1) edit config.xml to remove the Application element
          > >completely
          > ><br>>corresponding to the bean
          > ><br>>2) remove jar files from the applications directory
          > ><br>>3) re-deploy and run the client again.
          > ><br>>
          > ><br>>Thanks a lot
          > ><br>>Kiran Ganuthula
          > ><br>>
          > ><br>>
          > ><br>>
          > ><br>>
          > ><br>></blockquote>
          > ></html>
          > >
          > >
          [att1.html]