When a channel does not render, often due to timeout, the log message (see
below) indicates a WARNING rather than an error, even though the message
details refer to "ErrorDocument", "error channel", and "error code". It also
seems that when a channel does not render, that should be an error rather
than a warning. If a channel is timing out, I want to know about it. It may
indicate a database or ldap connectivity issue, for example. When I scan
logs for problems either programmatically or manually, I look for "ERROR".
The "Replacing channel" WARNING always slips through the cracks.
I am thinking of creating a JIRA issue to change the message category to
"ERROR". Are there any reasons not to do this that I am not aware of?
WARN [TP-Processor16] portal.ChannelManager.[] Aug/15 09:53:31 - Replacing
channel [BaseChannel: st
aticData = [.channel static data here .] isGuest:false] ] runtimeData =
[null]],
which had subscribeId [u43520l1n80] with error channel because of error
code Rendering timeout mess
age: unsuccessful rendering and throwable [null]
WARN [Thread-10770] error.CError.[] Aug/15 09:53:31 - ErrorDocument XML is
<error code="4">
<message>unsuccessful rendering</message>
<channel>
<id>u43520l1n80</id>
<name>PortalMail</name>
</channel>
</error>
Paul Gazda
Senior Web Developer
Information Technology Services
Northern Arizona University
[EMAIL PROTECTED]
(928) 523-6844
--
You are currently subscribed to [email protected] as: [EMAIL
PROTECTED]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
