Oracle AD4J Installation on Linux

Today I tried to install Oracle AD4J on a Linux server that I have at home. The installation procedure is really simple and fully described here. Unfortunately, when I tried to access the console for the first time (that access is one of the installation steps), the HTTP server returned an internal server error (500). In the mod_jserv.log logfile I found the following error messages:

[13/02/2009 10:06:38:079] (EMERGENCY) ajp12: can not connect to host 127.0.0.1:3501
[13/02/2009 10:06:38:181] (EMERGENCY) ajp12: connection fail
[13/02/2009 10:06:38:181] (ERROR) an error returned handling request via protocol "ajpv12"

Mhmm… a listener should be available on port 3501. But, no such listener was available on my system (note that port 3500 is used for the HTTP listener):

oracle@helicon:/u00/app/oracle/product/ad4j/ [rdbms11107] netstat -l --numeric-ports | grep 350[01]
tcp        0      0 *:3500                      *:*                         LISTEN

A quick search in Metalink revealed that at least another person has hit the same issue few days ago (see bug# 8235076). Since OSS is still working on it, I’ll wait to see what the findings are. In the mean time, I was able to successfully install it on my Windows laptop.

Anyway, if somebody of you managed to successfully install AD4J on Linux, please, let me know!

ADDENDA (February 16th, 2009): Because of the comments of Charles and Michael I spent a bit more time looking at the problem. In fact, the first time I stopped immediately after seeing the bug in Metalink… I was lazy ;-). Hey, I try to optimize my worktime as well. Anyway, both suggested to manually start jserv. When I tried to do so, I received an error (at last). Based on it the problem was self explanatory! The java environment was causing the problem… In fact, with the default installation of CentOS 4.4 only the package java-1.4.2-gcj-compat was installed. After downloading and installing the most recent version of HotSpot (build 1.6.0_12-b04) the problem was solved.

6 Comments

  1. February 13, 2009    

    I think I might have hit something similar. I vaguely remember that you need to start the jserv manually, then start ad4j.

  2. michael avrahamov's Gravatar michael avrahamov
    February 13, 2009    

    This is an apache/jserv issue; try running jserv manually as suggested in a previous comment.

  3. February 16, 2009    

    Hi Charles, Michael

    Thank you very much for your comments. I added an addenda to the original post with the last findings…

    Cheers,
    Chris

  4. February 20, 2009    

    Hi Chris!
    I installed it on RedHat4 32-bit and encountered some problems as well but I found that it was due to the java version. NOTE: the RedHat bundled version of Java as well as the one found in $ORACLE_HOME will not work! Here is my installation how-to:

    1. Download AD4J from OTN and the latest Java JDK from java.com. (I downloaded JDK version 1.6.0_11)
    2. Install JDK 1.6.0_11 as root
    3. Unpack AD4J in ex. /u01/app/jamserv
    4. Run: /u01/app/jamserv/configuer.sh “/usr/java/latest”
    Answers:
    #1: SE
    #2: .
    #3: .
    #4. company name
    #5. Dept. name
    #6. jamserve_host.domain
    #7. user@jamserve_host.domain

    Repeat identically the second time.

    5. Start Apache: /u01/app/jamserv/bin/apachectl start
    6. Login to console: http://jamserve_host.domain:3500
    7. Create a tablespace for ad4j data in the repository database (sqlplus)
    8. Create a ad4j user in the repository database (sqlplus)
    9. Go to AD4J console and click “Setup”
    (This will modify /u01/app/jamserv/conf/adminDB.properties)
    10. Fill in connection details to repository database
    11. Restart Apache
    12. Click to reload AD4J console page
    13. Click “Setup”
    14. Click “Repository DB” and scroll down to bottom of page
    15. Click “GO” to create tables etc…
    16. Click “Login” (admin/welcome)
    17. Change admin password :-)
    18. Re-Login
    19. Now you can build the war file and deploy on iAS

    Regards
    Måns

  5. February 20, 2009    

    Sorry, a remark:
    At the point 4, (answer #1) I wrote “SE”. Ofcourse this should be YOUR country code. :-)
    //Måns

  6. February 20, 2009    

    Hi Måns

    Thank you very much for posting the detailed installation how-to! It’s interesting to see that several people experienced the same problem…

    Cheers,
    Chris

Leave a Reply

Your email address will not be published. Required fields are marked *