ERR_EMPTY_RESPONSE

Sometimes, when you access the webpage and it displays the home page with login and after the successful login, we can see that the error comes in the webpage with ERR_EMPTY_RESPONSE and cannot access page.

Please follow the below commands and restart the page.

Start the command prompt with Administrator Mode

ipconfig /release
ipconfig /all
ipconfig /flushdns
ipconfig /renew

netsh int ip set dns
netsh winsock reset

Brief description for each commands given below.

ipconfig /release – will release the current IP configuration.

ipconfig /all – Displays the full TCP/IP configuration for all adapters.

ipconfig /flushdns – Flush and reset the client resolver cache

ipconfig /renew – DHCP server will assign a new IP address for the computer

netsh int ip set dns – Change the DNS automatically

netsh winsock reset – reset winsock catalog back to the default settings.

Apache Virtual Host Rule for Configure the url based on context root – Virtual Host Proxy Pass and ReWrite Rule

ProxyPass and ProxyPassReverse directives are used to direct the traffic from webserver to apache server. For configuring the proxy, we can configure with mod_proxy and mod_jk. Mod_jk forward the request to an application server via AJP protocol. 

In the below configuration, we are configured the request to Tomcat application server. The public domain listens to the port number 98. If the request comes with context root, it will direct to the application server and will serve the request. If the application is starting with language parameter, then it will redirect to the application with different context root. Below entries can be customized for your requirments and add it in httpd-vhosts.conf file.

<VirtualHost *:98>

    ServerAdmin webmaster@dummy-host2.example.com

    DocumentRoot "/u01/apache/htdocs/mysite"

    ServerName public.domain.entry

       ProxyPass /contextroot http://x.x.x.x:port/contextroot

       ProxyPassReverse /contextroot http://x.x.x.x:port/contextroot

       RewriteEngine On

       RewriteOptions Inherit

       RewriteLog "/u01/apache/logs/rewrite_log.log"

       RewriteLogLevel 8

        RewriteRule "^/$" /ar/index.html [R=301,L]

       RewriteRule ^/en/(.*)$ /Application_ContextRoot/$1?languageCode=en&%{QUERY_STRING} [P,L]

       RewriteRule ^/ar/(.*)$ / Application_ContextRoot /$1?languageCode=ar&%{QUERY_STRING} [P,L] 

       Include conf/modjk/uriworkers.properties

  

       ErrorLog "/u01/apache/logs/error_log"

       CustomLog "/u01/apache/logs/access.log" common

</VirtualHost>

JDBC LLR, table verify failed for table WL_LLR_SOA_SERVER1', row 'JDBC LLR Domain//Server

When we are creating multiple domains in the same server and trying to run Oracle SOA Server, we gets the below error because the old domain was updated in the database and expecting the new domain value.

Below are the exception details.

javax.transaction.SystemException: Failed to call
registerLoggingResourceTransactions()
weblogic.transaction.loggingresource.LoggingResourceException:
weblogic.transaction.loggingresource.LoggingResourceException:
java.sql.SQLException: JDBC LLR, table verify failed for table
<schema>.WL_LLR_SOA_SERVER1', row 'JDBC LLR Domain//Server' record had
unexpected value <old domain>//soa_server1' expected
'<new domain>//soa_server1' ONLY the original domain and server that creates an
LLR table may access it

Solution: - Update the database with new domain entries and restart the SOA Server

Command :-

update <Shema>.WL_LLR_SOA_SERVER1 set RECORDSTR = '<New Domain>//soa_server1'
where XIDSTR = 'JDBC LLR Domain//Server'

Example :-

update MYSOA.WL_LLR_SOA_SERVER1 set RECORDSTR = 'soadomain//soa_server1'
where XIDSTR = 'JDBC LLR Domain//Server'

Checking for conflicts...Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit exceeded

While updating the weblogic server path using bsu.sh, we might get this error.

To resolve this issue, open  {MW_Home}/utils/bsu/bsu.sh and update the Xms and Xmx values.

Example :- 

/u01/app/oracle/product/fmw11g/utils/bsu/bsu.sh

MEM_ARGS="-Xms2048m -Xmx2048m"

Find the Weblogic version installed

Execute the below commands to retrieve the weblogic version installed.

Set the class path to the file for executing java command

#. {WL_HOME}/server/bin/setWLSEnv.sh

Example :-

#. /u01/app/oracle/product/fmw11g/wlserver_10.3/server/bin/setWLSEnv.sh

Execute below command to get the weblogic version

# java weblogic.version

Execute the below command to get the weblogic version in details with subsystems details.

# java weblogic.version -verbose

Encountered unrecognized patch ID: {Patch ID}

While updating the weblogic server path using bsu.sh, we might get this error. To resolve this error, extract the patch files (one xml file and the jar file with Path ID name) in to {MW_Home}/utils/bsu/cache_dir directory.

If cache_dire directory is not available in {MW_Home}/utils/bsu directory, then create it and copy the files.

Again Execute the command and the issue will be resolved.

# ./bsu.sh -install -patchlist={Patch ID}  -prod_dir={WL_HOME}

Example:-

#./bsu.sh -install -patchlist={Patch ID}  -prod_dir=/u01/app/oracle/product/fmw11g/wlserver_10.3/