Application Server Solutions for Microsoft IIS and ASP.NET
       solutions   products   partners   company   support   downloads         store
ServletExec Self-Help: FAQ
Back to Search >  Back to Search Results

Faq ID 94
Product ServletExec
Category Miscellaneous, Registration, Version differences
Question How can I find out exactly which version and hotfix-level (formerly called "patch-level") of ServletExec I am running?
Answer
  • To check this for the "Java component" of SE, the ServletExecXX.jar file:
    Access the ServletExec Admin UI in a browser.
    • For SE 5.0 and greater, access http://<hostname>/servletexec/admin
      and view the SE JAR version at the bottom of the login page.
    • For SE 4.x and older, access http://<hostname>/servlet/admin
      and then click on the first link in the upper left-hand corner (labeled "help" or "support").
      At the top of the page in the right frame, you should see the exact version of ServletExec that is running. Possible values might be: 3.0, 3.0C, 3.0E, 3.1, 4.1, 4.1.1, 4.1.1p27, 4.1.1.28, 4.2, 4.2p20, 4.2.0.21 etc...

    If your SE JAR is patched then the version number should be followed by:
    pXX
    where XX is the patch level. SE 5.0p2 for example.

    If your SE JAR is hotfixed then the hotfix number is the number after the last dot:
    5.0.0.XX
    where XX is the hotfix level. SE 5.0.0.13 for example.

    Another way to learn the exact version of the SE JAR you are running is to examine the startup messages in ServletExec.log. The line which states that ServletExec has initialized will give the exact version.

  • To check this for the "Native component" of SE, (which is a DLL on Windows and is a .so on Unix):
    • If running on Windows, startup DBMON, then startup your webserver, then use a browser to send a request to your webserver, and view the messages that are output in DBMON.
      (if using SE ISAPI... not SE AS... then you could choose to view the contents of ServletExecNative.log instead of using DBMON).
      For example, with SE AS, the messages might look something like this:
      The ServletExec-<webserver-brand/version> Module/Adapter for ServletExec <version/patch-level> is initializing...
      ...
      ...
      The ServletExec-<webserver-brand/version> Module/Adapter for ServletExec <version/patch-level> has initialized...
      

      With Apache, it is normal to see these messages multiple times per Apache startup.

    • If running on Unix, you can't use DBMON.exe so you'll need to look for the above-mentioned messages in your webserver's log file. With Apache, you'd first need to set the LogLevel in httpd.conf to be info or debug and the messages would appear in Apache's error.log after Apache startup.


Special Note to ESRI ArcIMS customers who are using SE 5.0 AS with Apache 2.0.x (any platform):
If your SE native adapter reports that it is version 5.0 (no patch number or letter after the 5.0) then you will need to upgrade the native adapter component.
To do this you have 2 choices:
  1. You could uninstall SE 5.0 and then download a fresh SE 5.0 AS installer from the New Atlanta website which would give you an updated adapter that reports that it is SE 5.0c and which fixes:
    bug #956: Unable to Post more than 48k to a servlet running behind Apache 2
  2. You could leave your SE 5.0 installed and simply patch the native component by downloading SE 5.0 patch #2 or higher using the instructions given in FAQ #195 on this website, giving you an adapter that reports that it is SE 5.0p1 or higher and which also fixes bug #956 and possibly other native bugs depending on the hotfix/patch level (see the 5.0 hotfix ReleaseNotes.txt or the patch ReadMe.txt for more details).



   
company media information terms of use privacy policy contact us