Map Viewer Errors Thrown

Question

This is a followup on the post "JAVA Error Messages Thrown When Deploying Map Viewer," from Jun 12, 2008 11:22 AM. (reprinted below)
Basically there are a number of java errors thrown when attempting to install Mapviewer. Has anyone else come across similar error messages? What do they mean? I can't imagine this hasn't happened before.
Also, if anyone might have a clue or a direction to point me in concerning this matter, that would really be greatly appreciated. I really need assistance here, as I really have no clue what is going on, and I haven't managed to find anything on the Web concerning these specific error messages.
Thank you,
John
The following is the previous post I am referring to:
Hello,
Thank you for taking the time to assist with this problem.
I am fairly new to java, and so I have little understanding of what certain error messages mean after I deploy Map Viewer through oc4j.
I have poked around on the Web enough to have a feeling that the application is searching for certain necessary classes, and that it can't fully deploy without these classes. If this is true, where are these classes located and/or how do I point to them so that the application can find them?
There are one group of errors thrown when attempting to deploy Map Viewer, and then another set when attempting to create a "dynamic data source" from the Map Viewer admin page.
Following are the error messages:
(happens upon attempted deployment:)
08/06/12 11:08:22 java.lang.NoClassDefFoundError
08/06/12 11:08:22 at java.lang.Class.forName0(Native Method)
08/06/12 11:08:22 at java.lang.Class.forName(Class.java:164)
08/06/12 11:08:22 at java.awt.Toolkit$2.run(Toolkit.java:821)
08/06/12 11:08:22 at java.security.AccessController.doPrivileged(Native Method)
08/06/12 11:08:22 at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:804)
08/06/12 11:08:22 at oracle.sdovis.GlobalVisContext.<clinit>(GlobalVisContext.java:48)
08/06/12 11:08:22 at oracle.sdovis.MapMaker.setUGP(MapMaker.java:2334)
08/06/12 11:08:22 at
oracle.lbs.mapserver.core.MapperConfig.loadMapViewerConfig(MapperConfig.java:1082)
08/06/12 11:08:22 at oracle.lbs.mapserver.core.MapperConfig.loadConfigFile(MapperConfig.java:492)
08/06/12 11:08:22 at oracle.lbs.mapserver.core.MapperConfig.<init>(MapperConfig.java:274)
08/06/12 11:08:22 at oracle.lbs.mapserver.MapServerImpl.<init>(MapServerImpl.java:125)
08/06/12 11:08:22 at oracle.lbs.mapserver.MapServerImpl.<init>(MapServerImpl.java:109)
08/06/12 11:08:22 at oracle.lbs.mapserver.oms$ColdStart.run(oms.java:212)
08/06/12 11:08:22 at java.lang.Thread.run(Thread.java:595)
(happens after I attempt to create a "dynamic data source":)
08/06/12 11:13:23 java.lang.NullPointerException
08/06/12 11:13:23 at oracle.lbs.mapcache.config.ConfigLoader.loadDBConfigs(ConfigLoader.java:239)
08/06/12 11:13:23 at oracle.lbs.mapcache.config.ConfigLoader.loadCacheConfigs(ConfigLoader.java:84)
08/06/12 11:13:23 at oracle.lbs.mapcache.MapCacheServer.<init>(MapCacheServer.java:83)
08/06/12 11:13:23 at oracle.lbs.mapcache.MCSServlet$ColdStart.run(MCSServlet.java:87)
08/06/12 11:13:23 at java.lang.Thread.run(Thread.java:595)
08/06/12 11:13:23 java.lang.NullPointerException
08/06/12 11:13:23 at oracle.lbs.foi.FOIServer.<init>(FOIServer.java:163)
08/06/12 11:13:23 at oracle.lbs.foi.FOIServlet$ColdStart.run(FOIServlet.java:127)
08/06/12 11:13:23 at java.lang.Thread.run(Thread.java:595)
Also, when the second series of error messages are thrown, a red error message displays on the admin html page, which reads, "MapViewer server is still starting up." It doesn't matter how long I wait, it never does start up, and of course the error messages tell something is wrong.
Do I need to modify a file somewhere to tell Map Viewer where to look for these classes?
By the way I am running on a Sun server with Solaris 9
Thank you much,
John
Message was edited by: John
user641525

Answer 1

For future reference,
The problem was finally solved. Someone suggested to me to make sure I was running jdk 1.5.0 by typing "java -version" It turns out I thought I was running 1.5.0, but in actuality I was running 1.4.2.
The reason this was confusing was because I was pointing to the newer version when exporting the JAVA_HOME env. variable, by typing "export JAVA_HOME=[full path to jdk folder].
But the trick was to append the full paths for jdk/bin and jdk/jre/bin to the front of the PATH variable. At first I appened the paths to the end of the PATH variable, and nothing happened.
Basically, the mapviewer installation needs to look at the bin folders for the 1.5.0 version of the jdk.
You can always test this by typing "java -version." If your PATH variable is correct, then you'll see information on the most recent jdk installation instead of an older version.
John