I suspect installing the 32-bit Java after the 64-bit Java installation may have had something to do with it, but my Tomcat configuration was pointing to the Program Files and not Program Files (x86), so I don't know if there's some registry setting that was off or something.
InetSoft calls the sree.jar from the web.xml. I don't know anything about why they placed files where they do as this is all vendor coded and I'm just installing as they have directed. However, these are the snippets of the web.xml file where InetSoft is making calls: <servlet> <servlet-name>replets</servlet-name> <servlet-class>inetsoft.sree.web.ServletRepository</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet> <servlet-name>manager</servlet-name> <servlet-class>inetsoft.sree.adm.AdmServlet</servlet-class> </servlet> <servlet> <servlet-name>ResourceServlet</servlet-name> <display-name>Resource Servlet</display-name> <servlet-class>inetsoft.sree.web.jsp.ResourceServlet</servlet-class> </servlet> <servlet> <servlet-name>team</servlet-name> <servlet-class>inetsoft.sree.web.team.TeamServlet</servlet-class> </servlet> <servlet> <servlet-name>WSServlet</servlet-name> <servlet-class>com.sun.xml.ws.transport.http.servlet.WSServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>team</servlet-name> <url-pattern>/team</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>replets</servlet-name> <url-pattern>/Reports</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>replets</servlet-name> <url-pattern>/Reports/dashboard/*</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>manager</servlet-name> <url-pattern>/EnterpriseManager</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>ResourceServlet</servlet-name> <url-pattern>/resources</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>WSServlet</servlet-name> <url-pattern>/SoapRepository</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>WSServlet</servlet-name> <url-pattern>/SoapDataService</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>WSServlet</servlet-name> <url-pattern>/PeopleService</url-pattern> </servlet-mapping> <taglib> <taglib-uri>sree.tld</taglib-uri> <taglib-location>/WEB-INF/lib/sree.jar</taglib-location> </taglib> I have upgraded to Tomcat 7.0.23 now as well. :-) Debbie Shapiro Data Warehouse Manager Cardiac Science Office: 425.402.2233 Visit us at www.cardiacscience.com Suppliers of Cardiac Science, Criticare, Unetixs, Powerheart, Burdick, and Quinton products Part of the Opto Circuits Family -----Original Message----- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Tuesday, January 10, 2012 5:26 PM To: Tomcat Users List Subject: Re: Tomcat 7 service not starting -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Debbie, On 1/10/12 4:41 PM, Debbie Shapiro wrote: > Tomcat7-stdout: > > 2012-01-10 12:46:15 Commons Daemon procrun stdout initializedError > occurred during initialization of VM > java/lang/NoClassDefFoundError: java/lang/Object It's clear that something is broken, here. > My order of operations for the upgrade was as follows: > > 1) stopped Tomcat service 2) upgraded the 64-bit Java to 1.6.0_30 > JRE 3) upgraded the 32-bit Java to 1.6.0_30 JRE Is it possible that upgrading the 32-bit version /second/ may have set the default JRE to the 32-bit version, and you are trying to use 64-bit components for everything else? > 4) replaced the jar files for the InetSoft application in the > following directories per InetSoft's directions: \Style Report > Enterprise\lib (design.jar and sree.jar) > \Tomcat\webapps\sree\WEB-INF\lib (sree.jar only) 5) change the > web.xml to use sree.jar (instead of InetSoft's previously named > sree_pro.jar - they did a name change with the new version). web.xml does not specify .jar files... so, what did you do, exactly? Can you check your tomcat6w.exe configuration (run the program; look at the configuration) to see what JRE you have selected when the [procrun] service starts? http://tomcat.apache.org/tomcat-7.0-doc/windows-service-howto.html#Tomcat7w_monitor_application I would also highly recommend at some point (after you have resolved this particular issue) that you upgrade Tomcat to at least 7.0.21 -- 7.0.6 was a looong time ago. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8M5R0ACgkQ9CaO5/Lv0PBtaQCgviXR96n3Je33k08BwKn/UmJy Hu0AnRnGB2vX8j3y3B9abbqZuIFpmhzQ =kPhA -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org