Win a copy of Svelte and Sapper in Action this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

HELP!!! Intermittent Servlet problem

 
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm getting an intermittent Error 404 from WebSphere stating "No target servlet configured for uri: /mtd/com.mtd.dealer.SrvNavDirector". The SrvNavDirector is definitely configured, set up with the aliases of SrvNavDirector and com.mtd.dealer.SrvNavDirector, and has been used daily for the last three months with no problems. If I hit ctrl-refresh on the IE browser it usually works after about three tries. Many people are having this problem on the site, I'm not the only one. I have WebSphere Standard Edition 3.5.5 using MS-SQL 2000 as the administration database.
Please give any of your thoughts!!!
Thanks!
 
Ranch Hand
Posts: 515
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Trying hitting the servlet directly fully qualified.
com.mtd.dealer.SrvNavDirector
Can you do this?
-Dale
 
Gene Smith
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Dale:
No I can't load a servlet based on its classname because I removed the invoker servlet for security reasons. In the beginnings of the application we did use the invoker, but for production we removed the invoker and use an alias of the classname for the parts of the code that still use the full classname of com.mtd.dealer.SrvNavDirector.
 
Gene Smith
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Any other ideas? I've got 3000 customers trying to access this site and having problems.
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Are you getting any exceptions in the std out and std error logs? Usually this means something else is failing in the servlet engine...
Kyle
 
Gene Smith
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm not getting any errors in any of the logfiles.
 
Gene Smith
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
By the way Kyle, excellent book!!! I mean EXCELLENT! Bought it last year.
 
Gene Smith
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Actually I am getting very frequent errors now in WebSphere\AppServer\logs\trace.log.ibmhttp of the form:
Error: In do_service_time_request, enter_callback_mode failed
-- and --
Error - store_cipher_suite: no cipher suite
 
Kyle Brown
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Now that's interesting -- that log is from the IBM HTTP Server, and not WebSphere. Sounds like it might be dying before it ever reaches the app server.
Does bouncing the http server help? Is there a chance that your key file for security expired (or that your web server certificate expired)? There were some PMR's reported on these topics last year, but I don't remember if these were the symptoms...
Kyle
P.S. Thanks for the feedback on the book
 
Gene Smith
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
According to IKEYMAN when viewing the key file the certificate doesn't expire until Nov 16, 2002. Bouncing IHS doesn't help either, in fact I rebooted the entire machine. Poor users who were connected at that time!
The request makes it to WS because the 404 error on the browser is WS saying there is no target servlet configured for com.mtd.dealer.SrvNavDirector, which is a lie, hit refresh a couple of times and it works, go figure?
It's almost like WS is encountering intermittent, hiccups when it tries to read its servlet info out of its admin database. The admin db is MS-SQL. Looking through MS-SQL logs doesn't show any errors anywhere though. And WS and MS-SQL are both on the same physical machine.
 
Don't get me started about those stupid light bulbs.
    Bookmark Topic Watch Topic
  • New Topic