bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Deploying Liquid Data

Troubleshooting a Deployment

This topic provides information to help you troubleshoot a BEA Liquid Data for WebLogicTM deployment. It includes the following sections:

- Troubleshooting Resources

- Troubleshooting Out of Memory Exceptions

This section provides general troubleshooting tips. For information about known limitations in specific Liquid Data releases, see the Liquid Data Release Notes.

Troubleshooting Resources

The following sections describe resources that you can use to troubleshoot a Liquid Data deployment:

- Liquid Data Resources

- WebLogic Server Resources

- Application Integration (AI) Resources

- Business Process Management (BPM) Resources

- WebLogic Portal Resources

- WebLogic Workshop Resources

- BEA Developer Center

Liquid Data Resources

Liquid Data provides log entries and release notes for troubleshooting resources.

Log Entries

Review the log entries in the domain log for errors. Liquid Data records status, problem, and performance information in the domain log. For more information, see "Monitoring the Server Log" in Monitoring the Server in the Liquid Data Administration Guide.

Release Notes

The Liquid Data Release Notes provide information about known limitations and workarounds for the version of Liquid Data that you are using.

Product Documentation

The Liquid Data product documentation provides detailed information about all aspects of the Liquid Data product. For more information, see the documentation CD that comes with the Liquid Data package or go to the Liquid Data Documentation page.

WebLogic Server Resources

The BEA WebLogic ServerTM server log contains valuable information about startup and run-time events that can help you troubleshooting a Liquid Data deployment. You can configure the amount of information that the WebLogic Server saves in the log file.

To configure the WebLogic Server server log:

1. On the Liquid Data server, start the Administration Console:

2. In the left pane of the Administration Console, click the name of the Liquid Data server for which you want to configure the log.

3. Click the Logging tab.

   The Administration Console displays the General tab showing the current log settings.

4. Change the log settings as needed.

   If you want the WebLogic Server to save the maximum amount of information to the log, select Log to Sdout, Debug to Stdout, and select a severity level of Info.

5. Click Apply.

Note: For debugging purposes, you can also click the Debugging tab, select Log Remote Exceptions and Instrument Stack Traces, and click Apply.

In a clustered environment, the domain log provides an aggregated view of log events for all servers in the cluster. For detailed information about WebLogic Server logs, see Using Log Messages to Manage WebLogic Servers in the WebLogic Server Administration Guide.

Application Integration (AI) Resources

BEA WebLogic IntegrationTM maintains separate logs for the Application View Management Console and for each adapter. These logs are located in the parent directory of the config/domain directory, where domain is the name of the domain that is currently running.

The Application View Management Console allows you to configure logging levels, as described in "Deploying the Application View" in "Steps for Defining an Application View" in Defining an Application View in Using Application Integration.

Business Process Management (BPM) Resources

You can enable debugging to route event data to the WebLogic Server Administration Console by setting the following debug flag on the server startup command line:

>     -Dwli.bpm.server.eventprocessor.debug=1

For more information, see the Debug Flags document in the WebLogic Integration documentation.

WebLogic Portal Resources

BEA WebLogic PortalTM uses the WebLogic Server logging mechanism to save messages to the WebLogic Server log. WebLogic Portal applications can control logging levels using classes and interfaces in the WebLogic Portal API, as described in the WebLogic Portal Javadoc.

WebLogic Workshop Resources

BEA WebLogic WorkshopTM uses the log4j Java logging facility developed by the Jakarta Project of the Apache Foundation. You can learn more about log4j at The Log4j Project.

You configure logging in WebLogic Workshop by changing settings in the workshopLogCfg.xml file, which by default is located in BEA_HOME/weblogic700/common/lib. For more information, see workshopLogCfg.xml Configuration File in the WebLogic Workshop documentation.

By default, WebLogic Workshop uses two log files:

- workshop.log—configured to receive all internal logging messages emitted by the WebLogic Workshop runtime.

- jws.log—configured to receive all logging messages emitted by user code associated with web services. This includes code in JWS files, but also code in JSX and JAVA files that are used by a web service.

BEA Developer Center

The BEA Developer Center provides a range of technical resources, including newsgroups on technical topics, such as installation, clustering, JDBC, EJBs, servlets, and JSPs. For more information, visit the BEA Developer Center at the following URL:

http://www.bea.com/support/welcome.jsp

Troubleshooting Out of Memory Exceptions

This topic describes how to handle out of memory exceptions that can occur in a deployment. The following table provides a list of possible causes and associated fixes.

Table 4-1 Causes and Solutions for Out of Memory Exceptions

Possible Cause | Problem Description | Solution
--- | --- | ---
User Error | Design flaw in the query. For example, a query attempts to perform a three-way join (table1, table2, and table3), but a join predicate exists between table1 and table2 only. | Fix the query design.
Lack of Proper Hints | Lack of proper or correct hints. | Specify proper hints, as described in Optimizing Queries in Building Queries and Data Views. Alternatively, redesign the query.
Query Plan Not Optimized | Lack of proper or correct hints. Possible limitations in Liquid Data Server implementation. | Specify proper hints. Redesign the query.
Large Result Set | Query returns a very large result set. For example, a query retrieves all the customers in the database. | Increase the heap size from the default (256MB) to as high as possible. Specify hints. For example, for RDBMS data sources, use the merge hint, if applicable, although using the merge hint might slow query performance. Use disk swapping, which improves system availability but might slow system performance.
Large Intermediate Result Set | Query returns a very large intermediate result set. For example, an analytical query, or a query that processes a large XML document, which Liquid Data loads entirely into memory before any query processing. | Increase the heap size from the default (256MB) to as high as possible. Use disk swapping, which improves system availability but might slow system performance.