If I start my WAS 5.1 in debug mode I get crazy pile of exceptions during the startup. I have a Struts 1 project that runs inside an EAR project on WAS 5.1.
Starting WAS in Run mode works fine, problem only in Debug mode.
The Struts project also used Spring and Hibernate.
The console throws all sorts of errors mainly related to class-loader confusion that I cannot list all here, but here is a glimpse of my nightmare with WAS 5.1:
The following console error gets thrown hundred times.
after hundred times of this error it throws this exception saying it cannot load the Servlet. Aparantly the Servlet crashed during init:
If this sounds familiar, please help!
This only happens in Debug mode, Run mode is manageable
Many thanks Mikalai (well done on the SCEA Study Guide ),
I tried that with different "WAR classloader Policy" modes (Module/Application). The crashes are gone, but so as the application which fails to start.
Class Loader Setup:
for [my EAR App]
Classloader mode: PARENT_LAST WAR Class Loader Policy: APPLICATION Start weight: 10
For [my Web module]
Classloader mode: PARENT_LAST Start weight: 10000
There is that fine tuning mystery which I don't know yet!
See console below:
back to my wall
Joined: Jun 04, 2002
It's not possible to tell exactly why it failed to start - too few info in logs.
Quick question: do you have WAR file name with spaces ? Good practice is to give EAR/WAR names without spaces (as well as deploy EARs to folders without spaces)
Joined: Jul 07, 2008
No spaces in my EAR and WEB (I just replaced the real names with aliases, sorry if that confused).