• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

ContextManager: Assertion failed: container==null (no Default Context?)

 
Srinivasa Kadiyala
Ranch Hand
Posts: 237
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am getting the error as mentioned below when I am running Tomcat 3.3.1

ContextManager: Assertion failed: container==null (no Default Context?)

Appreciate help

Thanks
 
Srinivasa Kadiyala
Ranch Hand
Posts: 237
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Can any one help me on this matter?
 
Ulf Dittmer
Rancher
Posts: 42968
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Unlikely. You're using software that's been deprecated for years, and you provide next to no detail on what exactly it is you're doing.
 
Srinivasa Kadiyala
Ranch Hand
Posts: 237
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Ulf

There is a project that needs to be upgraded and I started working on that.

The existing web app is on Tomcat 3.1 and I have taken the src code and put in my sand box. I would like to see the app behavior logic and functionality beforeI recode.

Rebuild- OK( JDK 1.3)

when I am running the project I am getting the above mentioned error.

I am stuck here .......
 
William Brogden
Author and all-around good cowpoke
Rancher
Posts: 13064
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
ContextManager: Assertion failed: container==null (no Default Context?)

As I recall, you can get that if the init method uses the form
init( ServletConfig config )
but fails to call the super init method to transmit the config to the base class.
See the docs for javax.servlet.http.GenericServlet
Bill
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic