Situation: Encountered the problem in runtime, it was running fine in previous application build, but not on the latest one. No major change to the code have been done.
Line 111 of FaxAdviceDispatcher:
My guess is, it's dying when it's trying to instantiate DataHandler(dataSource).
DataHandler is a class in activation.jar if any of u are familiar with the use of activation.jar (I'm not THAT familiar with it)
Question (1) What could this error trace possibly mean? (2) Anyone had similar problem/solution to this? (3) What can possibly fix it?
(my guess There is a change in the build procedure employed in previous and current version of the application. If LinkageError relates to the generated binary not able to link to classes in the Jars, then probably performing a clean build would resolve the issue?
( I need to wait till everyone go home and NOT using the server before I can do a full build so in the meantime I'm posting here).
posted 12 years ago
Apparently doing a full build of the application (clean the binaries, compiling, building, spitting ears, uninstall previous ear in server, dump the new ear, restart server) doesn't help.
Crap was giving me a hard time, turns out that Server already included activation.jar on runtime, and we had activation.jar in WEB-INF/lib, and the 2 jar are of different (seemingly incompatible) version!
removed the one in WEB-INF/lib and used the one set up for server runtime, and all is good.