[
https://jira.jboss.org/jira/browse/TEIID-368?page=com.atlassian.jira.plug...
]
Steven Hawkins resolved TEIID-368.
----------------------------------
Resolution: Deferred
Console is now defunct. Further integration with JOPR should be logged against 6.3
System state should give state details
--------------------------------------
Key: TEIID-368
URL:
https://jira.jboss.org/jira/browse/TEIID-368
Project: Teiid
Issue Type: Feature Request
Components: Console, Server
Affects Versions: 6.0.0
Environment: N/A
Reporter: Larry O'Leary
Priority: Minor
Fix For: 6.x
The system state displayed in the Console (or via the Admin API) should allow for
displaying individual state details. For example, if I have a connector with the state of
"Failed Initialization" I should be able to see information about the reason and
cause of that sate including state change information:
State: Failed Initialization
State changed at 1:52 PM CDT by loleary
Details: [MetaMatrix][Oracle JDBC Driver]Error establishing socket. Unknown host:
<host>
or
State: Running
State changed at 1:53 PM CDT by loleary
Details: Service started
or
State: Stopped
State changed at 1:54 PM CDT by MetaMatrixAdmin
Details: Service stopped
or
State: Data Source Unavailable
State changed at 1:59 PM CDT by DataSourceMonitor
Details: [MetaMatrix][Oracle JDBC Driver]Connection refused
Basically this would require all service state changes to be accompanied by a meaningful
state message. In the case of an exception or warning base cause of the exception should
be indicated as a message (no stack traces as that is what the logs are for). For
successful state changes this would be just an indication message to show a generic state
detail like "Started", "Stopped", "Restarted", etc.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira