Expand my Community achievements bar.

Applications for the 2024-2025 Adobe Experience Manager Champion Program are open!
SOLVED

Server Log Confusion (message meanings)

Avatar

Level 1

I realize that there are several pieces to this whole LiveCycle thing, but I and my colleagues find the robustness of the server log files somewhat overwhelming and extremely daunting.  I am not even sure what question to ask or how to ask it.  Basically I would like a list or a link to the descriptions and troubleshooting guides for the various modules/statements/messages that can appear in the server log.  Some are rather easy to interpret, understand, and figure out.  BUT, many of them are worse than reading Latin especially those that reference a STACKTRACE.  Even a high-level breakdown of some of the more common things.  Just about any help would aid us.  Attempting to search Adobe or even the web for specific entries with the specifics stripped out produces few is any sound results.

I apologize if this seems like I am venting.  Some of it may be just that but I can not believe that I/we am the only one confused by the server log.

1 Accepted Solution

Avatar

Correct answer by
Level 9

Hi

You may find this blog posting gives you some background.

http://www.avoka.com/blog/?p=166

The real problem you're facing is that LiveCycle is a very complex product, and you're seeing log messages from lots of different modules and sub-systems all rolled up into a single file. Hang in there, it will start to make sense.

Howard

http://www.avoka.com

View solution in original post

3 Replies

Avatar

Level 1

I found that one and it is useful to an extent but only if the log entry has one of those codes and if the code is in that file.  It seems that 90% of the log entries I am dealing with do not have any of those codes.  This may mean that they are specific to LiveCycle but related to one of the other tools used by LiveCycle (i.e., JBoss).  I do not know and that is part of my frustration.

Avatar

Correct answer by
Level 9

Hi

You may find this blog posting gives you some background.

http://www.avoka.com/blog/?p=166

The real problem you're facing is that LiveCycle is a very complex product, and you're seeing log messages from lots of different modules and sub-systems all rolled up into a single file. Hang in there, it will start to make sense.

Howard

http://www.avoka.com