[JBoss JIRA] Created: (TEIID-1612) Tried a custom log appended, but the LoggingEvent.getMessage() returns org.teiid.logging.LogMessage and not org.teiid.logging.CommandLogMessage
by Van Halbert (JIRA)
Tried a custom log appended, but the LoggingEvent.getMessage() returns org.teiid.logging.LogMessage and not org.teiid.logging.CommandLogMessage
-----------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-1612
URL: https://issues.jboss.org/browse/TEIID-1612
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Tried to create a custom logger, following what the doc says:
------
If you want to build a custom appender for command logging that will have access to log4j "LoggingEvents" to the "COMMAND_LOG" context, it will have a message that is an instance of org.teiid.logging.CommandLogMessage defined in the teiid-api-7.4.jar use these class in your development.
-------
but the actual object type from event.getMessage() is: LOGGING EVENT MSG TYPE: org.teiid.logging.LogMessage
(this is a sysout from the custom appender)
And there, don't have access to the similar methods provided n CommandLogMessage.
I'll attach the code.
Did I implement something incorrectly?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (TEIID-1585) Make payload available in ExecutionFactory.getConnection
by Mark Addleman (JIRA)
Make payload available in ExecutionFactory.getConnection
--------------------------------------------------------
Key: TEIID-1585
URL: https://issues.jboss.org/browse/TEIID-1585
Project: Teiid
Issue Type: Feature Request
Components: Connector API
Affects Versions: 7.3
Reporter: Mark Addleman
Assignee: Steven Hawkins
We require user-specific connections to our backend datasources. We pass user credentials to the translators using the payload but the payload is not available in the getConnection(Factory f) method. I propose adding public getConnection(Factory f, Serializable payload) method in ExecutionFactory whose default implementation is to call getConnection(Factory f).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (TEIID-1640) QueryTimeout connection parameter does not cancel long-running queries
by Paul Nittel (JIRA)
QueryTimeout connection parameter does not cancel long-running queries
----------------------------------------------------------------------
Key: TEIID-1640
URL: https://issues.jboss.org/browse/TEIID-1640
Project: Teiid
Issue Type: Bug
Components: JDBC Driver
Affects Versions: 7.4
Environment: Fedora 14 (server & client), Teiid 7.4 Final
Reporter: Paul Nittel
Assignee: Steven Hawkins
Testing XML files as data sources involves running queries which can take a long time (minutes). I defined my connection URL (in SQuirreL) as jdbc:teiid:VDB@mm://localhost:31000;QueryTimeout=1
The next query I executed processed for over 4 seconds, but there was no evidence of an attempt to cancel the query.
I've got a series of XML files you can use to test this, if you want. They're too big to attach (even when zipped).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month