Win a copy of Machine Learning Systems: Designs that scale this week in the Scala forum
or Xamarin in Action: Creating native cross-platform mobile apps in the Android forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Websphere sudden error on file not found, bean not found, etc.  RSS feed

 
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi everyone,
I recently developed application using Spring, jsp, java code for the web application deployed on WebSphere.  Once a while, suddenly, when I started or redeployed, I got error, file not found, spring bean can't instantiated, path, etc, many beans have found errors. even though I did not change anything in the application-context.xml

One time, I found a solution to fix this error was that websphere suddenly changed my jar run time from websphere 8 jre to jre 1.7x.  After changing the build path, everything back to normal.  But this time, I checked build path and it is still intact.  I have not changed the code or config at all.
I use myeclipse ide with websphere 8.0.

The only thing is that wrote a junit test have its own context.xml.  I wonder if I have touched something and websphere did a hot deploy that I did not know.  Any answer is appreciated.

Because this causes panicking when I my code worked and did not change but suddenly does not work.  Well, something must have changed but I have not been able to catch that.  Thank you very much.

John
 
Ranch Hand
Posts: 974
9
IBM DB2 Java Netbeans IDE Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
First, are we talking about a WebSphere instance in production or just a developer instance you connect to via MyEclipse to develop / debug / and so on ?

I wonder if I have touched something and websphere did a hot deploy that I did not know.


Sounds practically impossible... tipically even on fastest machine Websphere takes a while to hot deploy an EAR /WAR, so if we are in production someone should have noticed a temporary outage of the application, maybe yourself if we're talking about a developing instance you were connected to.
Anyway have a look at the System.out and System.err files, where restart / redeploy are clearly logged. Always logged, even if you use the autodeploy folder provided by WebSphere 8.0+ versions.
About files not found, where are they located ? Inside the EAR/WAR ? Or in any other directory ?


 
No one can make you feel inferior without your consent - Eleanor Roosevelt. tiny ad:
Rocket Oven Kickstarter - from the trailboss
https://coderanch.com/t/695773/Rocket-Oven-Kickstarter-trailboss
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!