Posts tagged "error messages"

Debugging LiveCycle – Working with logs (Part 2)

- Ankush Kumar, Lead Software Engineer @ Adobe

In Debugging LiveCycle – Working with logs (part 1), we covered how to handle logs at application server level. In this blog, we will cover a few areas where we can fine tune the logging in applications itself.

 LCM Logs

As you might have noticed LCM logs are found at <LiveCycle Installation Location>/configurationManager/log. Default logging level of this is INFO. This is governed by properties file kept inside adobe-lcm.jar: \com\adobe\livecycle\lcm\logging\log.properties.

Using this property file, you can:

  • Change Logging Level
  • Define file location and file name.
  • Define rotation policy

If you want to overwrite the default location of this file to a more convenient location, you can do so by modifying <LiveCycle Installation Location>/configurationManager/bin/ConfigurationManager.bat and specifying following system property:

-Djava.util.logging.config.file=<path to file>

 Generating ORB Trace

While working with natives like XMLForms, you can sometimes run into issues where an application abnormally terminates. Following parameters help in generating extra trace information for debugging such issues.

These are required to be placed as argument to the native application:

-ORBtraceLevel 25 -ORBtraceThreadId 1 -ORBtraceInvocations 1 -ORBtraceInvocationReturns 1 -ORBtraceTime 1 –ORBtraceFile <Path to log file>

Also, when we are debugging an issue related to native applications, in System Out logs we can find system natives being invoked and a large IOR is passed to them as input. This IOR can be analyzed by many easily available IOR parsers. (Just Google for them). This can be first step towards debugging natives related problem.

Variable Logging

In order to better understand and debug an orchestration, LiveCycle offers excellent process debug feature. Using workbench, one can easily trace every step of a process and find what exact values any variable hold. For more information, one can refer this blog.

http://blogs.adobe.com/shwetank/2011/11/21/process-recording-feature-of-livecycle-workbench/

But sometimes this gets difficult due to environment constraints and performance overheads. One may want to introduce a step which will log current state of all variables in either System Out log or the log of your choice.

This can be accomplished using Variable Logger service. One can introduce this while designing the orchestration. Now each time the orchestration runs, the values of variables will be logged as the step is executed.

Other Application Logging Locations

Content Services and CMSA Logs

Content Services and CMSA logs are created in working directory of the application server.

LiveCycle Installer Logs

Installer logs can be found in following two locations

  • <LiveCycle Installation Home>
  • <LiveCycle Installation Home>/logs

Service Pack Logs

Service pack logs can be found at <LiveCycle Installation Home>/patch/<Patch Name>/log

CRX and Correspondence Management Logs

From ES3 onwards, you will find CRX and CM logs at <CRX Repository Directory>/logs. (More on this will be covered in next part of blogs)

PDFG Configuration Logs

  • PDFG System Readiness Testing Logs:  <LiveCycle Installation Home>/pdfg_srt/reports
  • PDFG Config Logs: <LiveCycle Installation Home>/logs
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (1 vote cast)

Troubleshooting Common LiveCycle Configuration Errors

- Shishir Pandey, Software Engineer @ Adobe

The following lists the common configuration errors, why they occur, and steps to troubleshoot them.

  • Error: Component: com.adobe.xxx version: 10.0.3.20120511.1.316647 introduced a new service, it should not be patched
    Reason: This issue generally occurs when order of operation in Configuration Manager is incorrect after applying a patch. That is, the deployment of the component is performed before configuring and deploying of the EAR files. It usually occurs in command line execution because each step is run separately in this mode.
    Workaround: Re-run the Configuration Manager and ensure that configuration and deployment of ear is done before deploying components.
  • Error: In case of Weblogic, a “null” folder gets created after deploying EARs.
    Workaround: Stop the managed-server first, followed by the node manager, and finally stop the admin-server. Restart them in reverse order. You will see a folder Adobe gets created in the Weblogic domain.
  • Error: The following error occurred while executing this line: java.lang.OutOfMemoryError: Java heap space
    Reason:  This issue generally occurs if the XMX setting is missing from the server configuration.
    Workaround:  Increase the XMX value for the server or restart the server, and re-run Configuration Manager.
  • Error: weblogic.management.NoAccessRuntimeException: Access not allowed for subject: principals=[], on Resource AdobeService Operation: set , Target: EnableSSL at com.adobe.livecycle.bootstrap.bootstrappers.CoreBootstrapper.bootstrap(CoreBootstrapper.java:60)
    Reason:  This error generally occurs due to missing JMX policies in case of Weblogic during the Initialize LiveCycle step of the Configuration Manager.
    Workaround: Configure JMX as described in Creating JMX policies for database initialization. Restart the server and re-run the Initialize LiveCycle step.
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 7.0/10 (4 votes cast)

Debugging LiveCycle – Working with logs (Part-1)

Ankush Kumar, Lead Software Engineer @ Adobe

Logs are the first thing that come to the mind when we run into an issue. Following are some tips on improving the logging on the application side as well as the application server side.

Enabling/Modifying Logging of Application Servers


JBoss

Jboss, which is bundled with LiveCycle has a pre-configured log4j configuration file. It is present as <Appserver Home>/server/<profile>/conf/jboss-log4j.xml. you can track new packages or existing packages at debug level by simply using the following command:

<category name=”com.adobe.mypackage”>

<priority value=”DEBUG”/>

</category>

From here, you can do the following configurations:

  • Change log file path
  • Change log entry structure
  • Specifying log rotation policy
  • Enable cluster logging

The following JBoss wiki can help you play around the logging file.

https://community.jboss.org/wiki/Logging


Weblogic

Weblogic logging can be configured from Weblogic administration console. There are separate administration consoles for each managed server. On Weblogic administration console, logging can be accessed at Environment > Servers > [Name of Managed Server or Admin Server] > Logging.

Here, you can define following configurations

  • Log file path
  • Rotation Policy

However, in the advanced section, you can define:

  • Log entry layout
  • Logging Level
  • Specify package level logging in “Logger Severity Properties” box:
    com.adobe.mypackage=Debug

Note that on Weblogic, if you are running into issues while deploying EARs, you may want to look into Domain logs and Adminserver logs. Both of these are created under <Weblogic Domain>/servers/<Admin Server>/logs.


Websphere

Websphere logs can be found at <Websphere Home>/AppServer/profiles/<Profile Name>/logs/<server name>. You can configure it from Websphere administration console at Websphere Application Servers > [name of server] > Logging and Tracing.

In JVM Logs, you can configure SystemOut and SystemErr logs for your server.

Here, you can configure:

  • Location of Log file
  • Rotation Policy

From Logging and Tracing, with few simple steps, you can enable the trace level logging for a specific package:

  1. Select “Change Log Detail Levels” from General Properties section.
  2. Under “Change Log Detail Levels” page, you can find a text box and tree beneath it with root node as “* [All Components] “.
  3. Expand Root node “* [All Components] > com.adobe.livecycle.*” and click “com.adobe.mypackage.*”.
  4. This will open a context menu. Go to Message and Trace Levels and choose finest from sub menu.
  5. Click Apply button and Save the settings to master configuration. Now you should be back to “Logging and tracing”.
  6. Select Diagnostic Trace link. This will open Diagnostic Trace Service page.
  7. Make sure File radio button is selected. Increase the Maximum File Size to 50 MB, and Maximum Number of Historical Files to 5.
  8. File Name text box shows “${SERVER_LOG_ROOT}/trace.log” by default. This means trace logs are getting created at default logs folder. You can change it by giving any absolute path where you want diagnostic logs to be written.
  9. Click Apply and Save the settings to master configuration.
  10. Restart the server. File specified at step 8 should get created.
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 6.6/10 (7 votes cast)