Salesforce

Web clients report "System unavailable" or are automatically logged out of a web session

« Go Back

Information

 
TitleWeb clients report "System unavailable" or are automatically logged out of a web session
SummaryThere are several reasons why the system will appear to be unavailable, slow or users connected to the system might be kicked out and not able to log in again. The information presented here is meant to help tune the amount of available connections to the database for the web application in order to increase system availability.
URL NameSystem-unavailable-or-automatically-logged-out-of-web-session
Resolution
1. Log into the Web Server, often the same server as the application server.

2. Go to the JBOSS log folder which is usually at:

     cd $APPS_HOME/server/$APPS_PART/log

3. Open the server log file which is usually called "server.log".

     view server.log

4. Search for errors such as:

     Caused by: javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout

     org.jboss.util.NestedSQLException: Unable to get managed connection for OracleDS

5. If any of the previous errors are present then review the oracle-ds.xml file to determine the connection pool size.

     cd $APPS_HOME/server/$APPS_PART/deploy/

6. Search for the oracle-ds.xml

     ls -ltr oracle-ds*

7. Open the oracle-ds.xml file and search for the xml tag <max-pool-size>. If it is non existent or commented then the default size of the pool is 10.

8. If the system is used by a considerable amount of users at a single time then it is recommended to increase the max-pool-size. Follow these steps:

     A) Stop JBOSS, this can be done through appcontrol option "Shut down web client app server"

     B) If the tag does not exist, it is recommended to be placed at the end just after the <query-timeout> and before the <metadata> as shown below.

          Example:
          <query-timeout>300</query-timeout> 
          <max-pool-size>100</max-pool-size> 
          <metadata> 
          <type-mapping>Oracle9i</type-mapping> 
          </metadata>

     C) Start JBOSS, this can be done through appcontrol option "Start up web client app server"
ProductsDispatcher WMS
ModuleWeb client
Versionv2005.2.2 and above, JBOSS v6.1 and lower
Error Message Code
For JBOSS v6.1 and earlier there are several possible errors that can point to a problem with connection pool size:

1. ERROR [STDERR] Caused by: javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] ) 

2. ERROR [STDERR] (http-0.0.0.0-8080-66) org.jboss.util.NestedSQLException: Unable to get managed connection for OracleDS; - nested throwable: (javax.resource.ResourceException: Unable to get managed connection for OracleDS) 

 
Cause
The number of connections available to the web application may not be enough to satisfy all the requested transactions by all concurrent users using the system.
Additional Information
The configuration can also be viewed from the JBOSS administration console.
Publication StatusPublished

Powered by