0008123: ant diagnostics does ignore and not show tomcat errors when doing tomcat checks

Description

ant diagnostics does check some settings from inside tomcat. However when tomcat reports an error 'ant diagnostics' does not show this error to the user, so it is not easy to find out what is not working correctly.

Steps To Reproduce

Example:

- use debian provided tomcat5.5 package and do not disable the security manager (as is decribed on the wiki)
- in this case the ant diagnostics does fail and you can see this in the tomcat logfiles
- but in ant diagnostics output you just see either NumberFormatException or 'Server seems not to be tomcat'

Proposed Solution

Show a short description of the error message to the user and give some hints where to look for the reason.

Example:
[checkJVMversion] 0 INFO CheckJVMVersion - Checking Tomcat's JVM version...

[checkJVMversion] 6 ERROR ServerConnection - Server response: java.io.IOException: Server returned HTTP response code: 500 for URL: http://localhost:8180/OpenbravoDiagnostics/Check.html?Command=jvm-version [^]

[checkJVMversion] 7 ERROR ServerConnection - Probable reason: java.security.AccessControlException: access denied (java.util.PropertyPermission java.runtime.version read)

[checkJVMversion] 8 ERROR ServerConnection - Please check the servers logfiles for the detailed error message or access the failing url in your browser to see the full error: http://localhost:8180/OpenbravoDiagnostics/Check.html?Command=jvm-version [^]

Tags

OB3-Reviewed

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

Notes
(0014635) shuehner (administrator) 2009-03-13 18:16	Related: When ant dianostic does fails it does not remove the diagnostic code (webapp) from tomcat. When then running ant dianostic again i cannot add the diagnostic code to tomcat and fails. Fix can easily be included in this fix for this issue.

(0123764) shuehner (administrator) 2020-10-19 12:23	ant diagnostics is planned to removed in this issue 45242. Closing this very old usability issue as out of date.

Issue History
Date Modified	Username	Field	Change
2009-03-13 18:12	shuehner	New Issue
2009-03-13 18:12	shuehner	Assigned To	=> shuehner
2009-03-13 18:12	shuehner	Regression testing	=> No
2009-03-13 18:16	shuehner	Note Added: 0014635
2009-03-13 19:21	psarobe	Status	new => scheduled
2009-03-13 19:21	psarobe	fix_in_branch	=> pi
2011-10-28 11:30	psarobe	Tag Attached: OB3-Reviewed
2012-02-20 11:16	shuehner	Assigned To	shuehner => alostale
2015-03-11 14:01	alostale	Status	scheduled => acknowledged
2015-03-17 14:37	alostale	Assigned To	alostale => platform
2020-10-19 12:23	shuehner	Status	acknowledged => scheduled
2020-10-19 12:23	shuehner	Note Added: 0123764
2020-10-19 12:23	shuehner	Status	scheduled => closed
2020-10-19 12:23	shuehner	Resolution	open => out of date