following problem: we have an ear deployed on serveral test and production websphere (v 6.1) servers. now all of a sudden ( after a restart or whatnot) on two of the production servers (test servers are fine and have the same configuration)
there is an
exception when a certain action is executed and we have the suspicion that it might have to do with the classloader, in that there are several versions of that class and the one of them that is loaded has not got the method.
the thing is we havent changed anything on that server but restarting it. the classloader method ist parent first, so would a change to parent last solve the problem? we cannot test thoroughly, because we have to shut down production for that
time and we cannot expect that from our customers... or is it an jdbc problem or something of the like?
somebody got any help?
You can try following two options. After making the change stop and start the WebSphere process.
(a) WebSphere Console: Under "Class loading and update detection", select following two options: Classes loaded with local class loader first (parent last) and Single class loader for application.
(b) WebSphere Console: Under "Manage Modules" for the WAR file(s) present in the EAR, selected "Classes loaded with local class loader first (parent last)" option.
Joined: Jul 28, 2011
hi thanks for your answer.
When i try to do option a: i cant chang anything in class loading and upload detection because the values are greyed out. do i have to do something before i can change these values? stopping the enterprise application wont do the job any suggestion
edit:sorry that is because i used a testenvironment