search

testdriven / psi-probe

Advanced manager and monitor for Apache Tomcat, forked from Lambda Probe
8 stars 1 forks source link

IllegalArgumentException when viewing a single log #341

Open padcom opened 10 years ago

padcom commented 10 years ago

From milosz.e...@gmail.com on March 28, 2013 14:15:48

What steps will reproduce the problem? 1. Click on Logs menu

  1. Click on application specific logfile What is the expected result? Display contents of log file What happens instead? Error page What version of Probe are you using? 2.3.2 What environment (browser version, Tomcat version, JVM version, server OS)? IE 8.0, windows XP, Tomcat 6.0.36 x64, JVM x64 1.7.u9, Log files are stored in non_default location Please provide any additional information below. (Attach logs or stack traces as files instead of pasting the contents here.) Above situation occurs for every log file listed in the menu, even for probe.log, localhost etc.

Attachment: error page.txt loglist.png

Original issue: http://code.google.com/p/psi-probe/issues/detail?id=341

padcom commented 10 years ago

From MALfunct...@gmail.com on March 28, 2013 07:53:11

Can you try with the newest 2.3.3 release?

Status: NeedInfo

padcom commented 10 years ago

From milosz.e...@gmail.com on March 29, 2013 05:37:40

I would if i'm able to deploy it. As for know i have to wait for production to stop since undeploying of version 2.3.2 wasn't fully successful. File jcommon-1.0.8 was busy and i can't deploy new version

padcom commented 10 years ago

From milosz.e...@gmail.com on March 29, 2013 06:03:51

After closing handle to jcommon i was able to deploy again psi probe 2.3.3. New version still presents the same error when accessing log files.

padcom commented 10 years ago

From MALfunct...@gmail.com on March 29, 2013 06:50:50

Ok, thanks. I will investigate.

Status: Accepted
Labels: -Milestone-TBD Milestone-2.4.0

padcom commented 10 years ago

From MALfunct...@gmail.com on March 29, 2013 16:05:56

Similar to issue 328 , but for the LogSourceComparator.

Summary: IllegalArgumentException when viewing a single log (was: ERROR page instead of displaying the logfile for specifig application)
Status: Started

padcom commented 10 years ago

From milosz.e...@gmail.com on March 31, 2013 11:07:48

just quick explanation. Tomcat is running on Windows Server 2008 R2 x64. Tomcat version 6.0.36 x64, Java version 1.7u9 x64. Client computer is Windows xp x32, IE8.

padcom commented 10 years ago

From MALfunct...@gmail.com on April 01, 2013 14:58:04

Btw, I have seen that jcommon file locking issue as well. I've filed it as issue 343 .

padcom commented 10 years ago

From MALfunct...@gmail.com on April 01, 2013 16:00:50

This bug existed in 2.3.2, so I'm inclined to believe it was in 2.3.0. It may have existed in 2.2.x as well.

milosz.engel, can I email you a test build?

Labels: FoundIn-2.3.0

padcom commented 10 years ago

From MALfunct...@gmail.com on April 05, 2013 15:22:14

milosz.engel, can I email you a test build?

Owner: MALfunct...@gmail.com

padcom commented 10 years ago

From milosz.e...@gmail.com on April 08, 2013 05:38:26

yes, please email it to me. Sorry for late response.

padcom commented 10 years ago

From MALfunct...@gmail.com on April 09, 2013 13:57:39

This issue was updated by revision r747 .

padcom commented 10 years ago

From MALfunct...@gmail.com on April 10, 2013 07:27:44

Issue 345 has been merged into this issue.

padcom commented 10 years ago

From MALfunct...@gmail.com on April 10, 2013 11:09:44

I think this is fixed. Waiting on verification from the user.

Status: FixedInSource
Labels: Verified-No

padcom commented 10 years ago

From milosz.e...@gmail.com on April 11, 2013 07:06:00

I'm sorry to inform you, but it isnt fixed. Still the same Error

Attachment: error page2.txt

padcom commented 10 years ago

From MALfunct...@gmail.com on April 11, 2013 09:06:09

Back to the drawing board.

Status: Reopened

padcom commented 10 years ago

From MALfunct...@gmail.com on April 11, 2013 09:09:22

Status: Accepted

padcom commented 10 years ago

From MALfunct...@gmail.com on April 12, 2013 13:26:23

Status: Started
Labels: -Verified-No

padcom commented 10 years ago

From MALfunct...@gmail.com on June 14, 2013 07:41:40

Issue 356 has been merged into this issue.

padcom commented 10 years ago

From dale.ogi...@gmail.com on July 14, 2013 16:08:41

Hello, just seen this this morning on our setup.

probe 2.3.3 java version "1.7.0_25" Java(TM) SE Runtime Environment (build 1.7.0_25-b15) Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode) tomcat 7.0.41

padcom commented 10 years ago

From dale.ogi...@gmail.com on July 14, 2013 16:16:16

See attached stacktrace. Logs reported only:

14 Jul 2013 23:13:48 [catalina-exec-57] WARN org.springframework.web.servlet.PageNotFound - No mapping found for HTTP request with URI [/probe/logs/css/classic/main.css] in DispatcherServlet with name 'probe' 14 Jul 2013 23:13:48 [catalina-exec-63] WARN org.springframework.web.servlet.PageNotFound - No mapping found for HTTP request with URI [/probe/logs/css/classic/messages.css] in DispatcherServlet with name 'probe'

Attachment: probe_error.txt

padcom commented 10 years ago

From dale.ogi...@gmail.com on July 14, 2013 16:22:10

One possibility for consideration. We have a bug in our app code that causes the app classloader to be orphaned in tomcat. When I look at "show all logs" in probe, I see two instances of our app code hooking to log4j. Perhaps probe is being confused by this and finding the orphaned log4j hooks?

padcom commented 10 years ago

From dale.ogi...@gmail.com on July 16, 2013 20:44:15

Restarted our tomcat, problem still manifested after the restart, with no reloads of our app, so I guess scratch the idea of orphaned classloader being involved.

Logs are currently working fine on our system.

padcom commented 10 years ago

From tiag...@gmail.com on October 29, 2013 12:42:46

Had the same problem here, with the following situation, when a tomcat's context doesn't have any log appender the log detail view throws the exception in case, but when i've removed troublemaker context from deployment it worked fine.

padcom commented 10 years ago

From rnman...@gmail.com on February 26, 2014 20:52:59

For me, it seems that this problem happen in tomcat 7.0.23. But tomcat 7.0.29 and 7.0.52 don't have this issue.

padcom commented 10 years ago

From MALfunct...@gmail.com on April 11, 2014 16:33:04

Labels: Stacktrace

padcom commented 10 years ago

From MALfunct...@gmail.com on April 11, 2014 16:33:15

Issue 403 has been merged into this issue.

padcom commented 10 years ago

From MALfunct...@gmail.com on May 15, 2014 11:55:48

Issue 409 has been merged into this issue.

padcom commented 10 years ago

From tril...@gmail.com on June 12, 2014 04:48:10

had the issue on one server and not the other looked at the different applications installed and the only difference was / (root) "Welcome to Tomcat".

Deleted to test it, and it solved the problem on Apache Tomcat/7.0.37

padcom commented 10 years ago

From MALfunct...@gmail.com on August 13, 2014 06:19:50

Issue 416 has been merged into this issue.