Install Tomcat as a service under Windows x64 editions
We've previously deployed RTC (and RQM and RRC for that matter) to servers which all run Windows 2003 Server 32-bit edition, and successfully set up Tomcat to run as a service on all 3 of them. We just deployed a new server which runs Windows Server 2003 R2 Standard
When attempting to start the service, the jakarta_service_YYYYMMDD.log file produces the following: [2010-03-15 09:28:03] [174 javajni.c] [error] %1 is not a valid Win32 application. (I know log is from RRC, not RTC, but I don't think that matters. It was the first server we hit this with). Initial googling shows a number of older (circa 2007-2009) posts about Tomcat5 having this problem on 64-bit systems. Newer posts (2009-2010) talk about tomcat 6. Seeing as it's v5 that is distributed with RTC/RRC/RQM...what's the method to get this running properly with the Jazz toolset? Thanks, David |
3 answers
Naturally, found "the" technote which I am now pursuing after posting. Isn't that always the case...can't find "the" note until posting for more help!
http://www-01.ibm.com/support/docview.wss?uid=swg21404257 |
Above referenced technote does, in fact, provide the solution. In our case there was some trepidation regarding binaries explicitly labeled "AMD64" being installed on a server with Intel Xeon processors (which is what we have). They do, however, appear to be working!
Best I could find so far was that the two instruction sets have few differences, and most binaries compiled for 64bit will work for both types of processors. Does anyone know of a specific reference I could provide which would satisfy our network group to say "these binaries referenced from the IBM technote are compatible with Xeon processors"? Sorry, not a Tomcat expert...this is probably a simple question/not a concern for them! |
Naturally, found "the" technote which I am now pursuing after posting. Isn't that always the case...can't find "the" note until posting for more help! I found a simple solution that seems to work fine. I setup a Windows Scheduler Task that executes the jazz server startup batch file. The Windows Scheduler allows you to run a task on "Startup" of the server. So I set it up to fire when the server starts. Works perfectly. This eliminates the need for the service - which I could not get to work reliably. Hope this helps. David |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.