Posts tagged "log"

Adobe CQ/AEM support tools available

We have recently published a package with support tools that can be useful to help diagnose issues encountered with Adobe Experience Manager.  As the tools project continues to mature, additional tools will be provided to ease the overall diagnosis and maintenance of CQ.

Overview of tools in 1st release:

  • Logs Viewer – Provides an easy way to download all CQ logs.  The tail functionality will open a new window and start tailing the log file.  Multiple log directories can be configured via Logs Tail Plugin.  The crx-quickstart/logs is used as default if configuration is not bound.  This tool can also be used with curl.  Allows you to package up all the logs in one single click making it easy to provide the logs when opening a Daycare ticket.  Detailed info here: http://helpx.adobe.com/content/help/en/cq/kb/logsviewer.html
  • Tar PM Scan – Scans tar files and displays node path and size for each record.  This can be useful when analyzing abnormal workspace growth.  Large individual node sizes could indicate a flat hierarchy (i.e. a large child node list > 1000).  The same nodes appearing repeatedly in the scan could indicate a code issue or some other problem related to updating the same nodes repeatedly.  Detailed info here: http://helpx.adobe.com/content/help/en/cq/kb/tarpmscan.html
  • Thread Dumps Collection & Analysis - Takes thread dumps at regular intervals and saves them in a file under crx-quickstart/threads.  The page will also display a list of links to existing thread dump files.  The tool can use jstack, if it is installed on the system, or JVM MBean.  Detailed info here: http://helpx.adobe.com/content/help/en/cq/kb/thread-dumps-collection-analysis.html
  • Content Compare & Import – Used to compare and import content differences from one CQ instance to another CQ instance.  This helps to ensure consistency across servers.  Detailed info here: http://helpx.adobe.com/content/help/en/cq/kb/contentcompareimport.html

Download and install

The tools are supported for use with CQ5.5, AEM5.6 and later versions.  Here are the instructions to download and install the support tools: http://helpx.adobe.com/cq/kb/support-tool-installation.html

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (6 votes cast)

LiveCycle: JBoss stopped logging in server.log

If you have installed LiveCycle in a JBoss application server the server activity will normally be logged in:

<JBOSS_HOME>\server\<profile>\log\server.log

If the JBoss log is no longer logging activity you should check the following:

1. Log4J

The jboss-log4j.xml file is located in <JBOSS_HOME>\server\lc_turnkey\conf and controls logging in JBoss.  If there is any problem with this file then logging may stop working.  You can download this file (jboss-log4j-working) from a fresh LiveCycle installation on JBoss and replace the original (make a backup first).  Restart JBoss after swapping the log4j file and logging should switch to the server1.log file.

2. User account

If you are starting JBoss using a Windows service ensure that the user account used for the service has administrative privileges.  See the installation documentation for further requirements such as disabling UAC on Windows.

reference: (183305796)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 1.5/10 (2 votes cast)

LiveCycle ES: warning in server log when passivating document

Issue

A Form Guide stitches a PDF from multiple XDP fragments and then returns the PDF to the process in LiveCycle ES 8.2.1 or 9. When you submit this Form Guide, a warning appears in the server log:

[12/18/09 15:34:08:003 EST] 0000015a SystemOut
 O XDP form1.xdp,form2.xdp,form3.xdp,form4.xdp,form5.xdp,form6.xdp
[12/18/09 15:34:08:004 EST] 0000015a SystemOut O OPS form1.xdp
[12/18/09 15:34:08:234 EST] 0000015a AdobeCacheImp W com.adobe.repository.cache.AdobeCacheImpl put Document error while passivating document [<document state=”passive” senderVersion=”3″ persistent=”false” senderPersistent=”false” passivated=”true” senderPassivated=”true” deserialized=”true” senderHostId=”127.0.0.1/10.101.158.145″ callbackId=”0″ senderCallbackId=”4228″ callbackRef=”com.adobe.idp._IDocumentCallbackStub:

Solution

This warning is an informational message from the repository cache and can be ignored. In the ADEP platform (ES3) Adobe will downgrade this warning to an INFO or FINE level message, so it doesn’t appear in the logs.

reference: (181308950/2523516)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES: JMXBeanManager warning filling up the server log

Issue

If you are using Adobe LiveCycle ES 8.2.1.2 or 8.2.1.3 you may notice that the server logs are filling up with warnings similar to those shown below:

####<Jan 27, 2010 9:27:11 AM MET> <Warning> <com.adobe.idp.dsc.jmx.JMXBeanManager> <sunc01016> <wl01qalc01> 
<[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> 
<1264580831624> <000000> <Failed to get mbean: server1:Type=AdobeService,Name=DirectoryManagerService,version=1.0. 
This message is a warning only. It should not impact LiveCycle's invocation>

####<Jan 27, 2010 9:27:11 AM MET> <Warning> <com.adobe.idp.dsc.jmx.JMXBeanManager> <sunc01016> <wl01qalc01> 
<[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> 
<1264580831649> <000000> <Failed to get mbean: server1:Type=AdobeService,Name=DirectoryManagerService,version=1.0. 
This message is a warning only. It should not impact LiveCycle's invocation>

####<Jan 27, 2010 9:27:11 AM MET> <Warning> <com.adobe.idp.dsc.jmx.JMXBeanManager> <sunc01016> <wl01qalc01> 
<[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> 
<1264580831694> <000000> <Failed to get mbean: server1:Type=AdobeService,Name=DirectoryManagerService,version=1.0. 
This message is a warning only. It should not impact LiveCycle's invocation>

This warning is harmless and can be ignored, however it can lead to the log files growing exponentially.

Solution

This issue is fixed in LiveCycle ES2 (9.0.0.0). Patches are available for LiveCycle ES SP2 (8.2.1.2) and LiveCycle ES SP3 (8.2.1.3). Contact enterprise support if you require one of these patches to ensure that they are compatible with your environment.

reference: (181407992/2540696)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 8.0/10 (1 vote cast)

LiveCycle 7: disable “An active transaction should be present…” message from the WebSphere log output

Issue

 If you are running LC7 products in the WebSphere application server you may notice the following message appearing repeatedly in the log file:

[21/09/07 15:40:24:562 IST] 72d82e0c ConnectionMan W J2CA0075W: 
An active transaction should be present while processing method allocateMCWrapper.
[21/09/07 15:40:24:578 IST] 72d82e0c ConnectionMan W J2CA0075W: 
An active transaction should be present while processing method initializeForUOW.

You may want to disable this message, to prevent it appearing in the log.

Reason

This message can be ignored as it is merely an informational message.  This message can appear so much, that it starts to fill up the log and makes it very difficult to see any actual problems in the log.

Solution

To simply suppress the messages from being logged to the SystemOut.log, do the following:

Open the <WEBSPHERE_HOME>\properties\j2c.properties file in a text editor.  Find the following block:

<!-- The cm-properties are in a comment block. Uncomment to use -->
 <!--
 <cm-properties>
     <manageCachedHandles>false</manageCachedHandles>
     <logMissingTranContext>true</logMissingTranContext>
 </cm-properties>
 -->

Remove the comments and change the true to false.  It should look like the following once complete:

<!-- The cm-properties are in a comment block. Uncomment to use -->
 <cm-properties>
 <manageCachedHandles>false</manageCachedHandles>
     <logMissingTranContext>false</logMissingTranContext>
 </cm-properties>

___________________________________
reference: (1-25647507)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)