Troubleshooting SOA Gateway Server issues

  • Cannot load mod_xmiddle.so into server: failed to map segment from shared object: Permission denied.

    This error can occur on Red Hat when SELinux is enabled. To disable it do the following:

    • As root, run system-config-securitylevel

    • Select SELinux Tab.

    • In the "Modify SELinux Policy" box, expand "HTTPD Service"

    • Tick the box "Disable SELinux protection for httpd daemon"

    • Click [ OK ]

    • Click [ YES ]

  • API module structure `xmiddle_module' in file XXX is garbled - perhaps this is not an Apache module DSO?

    Ensure that you have chosen the correct installation for your system. For example, this error can occur when SLES 9 files are installed on a SLES 10.

    Ensure that the version of Apache you are installing on is either v2.0 or v2.2. Other versions are not supported.

  • Failed to bind to <port number>, port already in use

    The port specified on the Listen directive in Apache's configuration file is already being used by another application. Change this to a port number not being used.

  • No error on command line, but Apache is not responding.

    Check Apache's error_log file for error messages from the SOA Gateway server.

    The default location of the Apache error_log is [SOAG_INST]/apache2/logs/error_log replacing [SOAG_INST] with the location you installed SOA Gateway in.

  • A SOAP Fault is generated

    Check the associated message in the <soap:faultString> element for error explanation. There may also be further messages available in the Apache's error_log.

    The default location of the Apache error_log is [SOAG_INST]/apache2/logs/error_log replacing [SOAG_INST] with the location you installed SOA Gateway in.

  • Abend S0C1 in module SAFASG

    When the SOA Gateway server is running with Security Level = User or Password and is protected by Adabas SAF this abend indicates that SAFASG has not been linked correctly, please revisit the Security Section and relink SAFASG accordingly.

  • Command 'LF' for dbid=212, fnr=9, Rsp 17 (Invalid file number)

    This error indicates you are accessing a file (number 9) that does not exist on the Adabas database (ID=212). For example, you may be running a installation verfication test, and the standard demo files ("Employees" and "Vehicles") delivered with Adabas have not been installed, or have not been installed in the standard locations.

  • Unicode char 0xF1 is not representable in encoding ASCII.

    See information about i18n here

  • PRNG still contains insufficient entropy! Failed to generate temporary 512 bit RSA private key. Configuration Failed

    Ensure the 2 following directives are enabled in your Apache configuration file (httpd.conf) 

    SSLRandomSeed startup builtin
SSLRandomSeed connect builtin

    If running on z/OS or z/VSE ensure the server is not active when submitting jobs which copy content to the SOA Gateway file system.