Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

[14:27:31 CST(-0600)] <EricDalquist> but thats about all I can say

[14:28:31 CST(-0600)] <b-sure> hmm I don't see anything else in there so far. I'll keep looking.

[14:28:46 CST(-0600)] <EricDalquist> for that first stack

[14:28:58 CST(-0600)] <EricDalquist> there should be addtional stack trace data immediately after what you shared

[14:29:09 CST(-0600)] <EricDalquist> like a whole additional Caused By section

[14:37:22 CST(-0600)] <b-sure> here is the last / bottom part of the trace http://pastebin.com/raw.php?i=Z3YV1WKp

[14:37:49 CST(-0600)] <EricDalquist> that doesn't match up

[14:37:57 CST(-0600)] <EricDalquist> so for http://pastebin.com/raw.php?i=jmgTGZPL

[14:38:19 CST(-0600)] <EricDalquist> immediately after the last line "... 75 more"

[14:38:35 CST(-0600)] <EricDalquist> there should be another "Caused by: " line

[14:39:07 CST(-0600)] <EricDalquist> that will probably be the root cause

[14:39:14 CST(-0600)] <EricDalquist> which is what we would need to actually figure something out

[14:41:20 CST(-0600)] <b-sure> ok. I think this is what follows http://pastebin.com/raw.php?i=bqw7ghQc

[14:42:39 CST(-0600)] <EricDalquist> hrm

[14:42:40 CST(-0600)] <EricDalquist> ok

[14:42:46 CST(-0600)] <EricDalquist> so the root cause is a NPE

[14:42:54 CST(-0600)] <EricDalquist> but it appears that the tomcat logger is truncating the stack trace

[14:43:02 CST(-0600)] <EricDalquist> is there a similar stack trace in the portal log file?

[14:43:09 CST(-0600)] <b-sure> yeah the last line of the trace is NPE

[14:43:22 CST(-0600)] <b-sure> I'll check portal log...

[14:55:10 CST(-0600)] <b-sure> hmm. Looks like the portal log is overwritten for that time. I do see this http://pastebin.com/raw.php?i=HKe6jcia but cannot tell if it is related. the timestamp is earlier than the other exceptions.

[14:56:38 CST(-0600)] <EricDalquist> doesn';t look like it

[14:58:37 CST(-0600)] <b-sure> ok. well thanks for your help. I'll try to catch this in the logs if it happens again. our logs are set to roll at 2MB looks like I need to bump it up to 4 or 5.