Viewing transaction logs  Chapter 13: Importing, Exporting, and Deploying Portal Objects

Chapter 12: Using Enterprise Portal Agents

Limiting the log size

To prevent sending too much data to the browser and slowing down performance, define the number of message you want to display in global.properties.xml. For example:

<Property name="MaxLogRows" value="150"
description="The maximum number of log rows to return
on a view log request (set to zero for all)."

To view all messages in a sizable log, use SQL to display the log rather than View Log as the text returned over HTTP can be too enormous for the browser.

Logging is kept in the app_logs table. The objects that reference each table row are stored in the app_log_object_refs table. For example,

select * from app_logs

displays all log messages.

NoteThe agents transaction logging can fill a database quite fast. If the View Log or other agent functionality seems slow, check the database logs to see if the database is out of space. You may see an error like:

Tasks are sleeping waiting for space to become available in the log segment for database tempdb

To solve this problem, increase the database size. See the ASA Database Administration Guide on the Technical Library CD that comes with the product. If you are using a database other than Adaptive Server Anywhere with EP, refer to that product’s documentation for instructions on increasing the database size.





Copyright © 2004. Sybase Inc. All rights reserved. Chapter 13: Importing, Exporting, and Deploying Portal Objects

View this book as PDF