August 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-718) Translate criteria fails on prepared statement update/delete criteria

by Steven Hawkins (JIRA)

Translate criteria fails on prepared statement update/delete criteria --------------------------------------------------------------------- Key: TEIID-718 URL: https://jira.jboss.org/jira/browse/TEIID-718 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 6.2.0 Translate criteria pulls values/references from the parent command that cannot be evaluated in the context of the update procedure. -- 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

15 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-729) Default keystore may lead to confusion or provide false sense of security in encrypting passwords

by Ramesh Reddy (JIRA)

Default keystore may lead to confusion or provide false sense of security in encrypting passwords ------------------------------------------------------------------------------------------------- Key: TEIID-729 URL: https://jira.jboss.org/jira/browse/TEIID-729 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 6.1.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 Currently Teiid source code contains a default "teiid.keystore", which is then used by any component (connector binding) in encrypting password. Designer does use this to encrypt the password as it does not have it's own private keystore. This poses 1) False sense of security, as this is mere obfuscation as "keystore" available to anybody. 2) If the Designer provides a keystore of its own, now it becomes the burden on the user to share this same keystore on the runtime environment to enable decrypting the password. Currently this major issue in connector binding as not starting, or somebody imports previous configuration where the passwords are encrypted with different keystore. The simple solution is not provide a "default" keystore. If Designer does not provide a private keystore, then passwords in plain text in the connector binding properties. That will seamlessly run in Teiid runtime, if user does not care about having clear text passwords. That may be situation in DEV environments. In production environments during runtime (if required) Teiid will provide tools and instructions as to how to encrypt passwords. If the user does provide keystore in the Designer then it is user responsibility to share this keystore with runtime environment, that they work in sync in encrypting and decrypting the password. Users will be provided with scripts to generate a keystore with Teiid kit, with which they can use to encrypt the passwords. So, this will make the encryption as an option rather than requirement in the Teiid system. -- 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

15 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (TEIID-681) Fix logger for JBoss cache, JBossTM integration to use the same log file as the rest of the system

by Ramesh Reddy (JIRA)

Fix logger for JBoss cache, JBossTM integration to use the same log file as the rest of the system -------------------------------------------------------------------------------------------------- Key: TEIID-681 URL: https://jira.jboss.org/jira/browse/TEIID-681 Project: Teiid Issue Type: Sub-task Components: Common Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 Teiid was using its own logging framework before and JBoss Cache and JBoss Transactions integration code was never were written to use the Teiid's native logger. They were written such that they were redirected to apache commons logging --> log4j. Now that Teiid uses the Log4J, all these subsystems need to redirect their logs to main teiid logger which will redirect to the log4j. -- 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

15 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-719) Authorization Realms are being checked in case dependent way

by Ramesh Reddy (JIRA)

Authorization Realms are being checked in case dependent way ------------------------------------------------------------ Key: TEIID-719 URL: https://jira.jboss.org/jira/browse/TEIID-719 Project: Teiid Issue Type: Bug Affects Versions: 6.1.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 When enforcing the data role entitlements on VDB the realm is computed as = Vdb-Name + Version and checked against the VDB that user is connected to. If the user connected to VDB with a different case (as connection is case in-independent of the VDB name) than what the VDB is defined as, then the user is never entitled against data which he/she should be. -- 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

15 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-735) Equals method for subqueryfromclause is incorrect

by Steven Hawkins (JIRA)

Equals method for subqueryfromclause is incorrect ------------------------------------------------- Key: TEIID-735 URL: https://jira.jboss.org/jira/browse/TEIID-735 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 The equals method for subqueryfromclause does not check for equality based upon contained command. -- 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

15 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-734) Exception while closing the JDBC Connection to the Teiid Runtime

by Ramesh Reddy (JIRA)

Exception while closing the JDBC Connection to the Teiid Runtime ---------------------------------------------------------------- Key: TEIID-734 URL: https://jira.jboss.org/jira/browse/TEIID-734 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.1.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 6.2.0 2009-07-21 16:09:00,250 DEBUG [Worker1_SocketWorker24] org.teiid.Server - message: MessageHolder: contents=null for request ID:4 2009-07-21 16:10:38,991 DEBUG [New I/O server worker #1-2] org.teiid.Server - processing message:MessageHolder: contents=com.metamatrix.common.comm.platform.socket.client.ServiceInvocationStruct@1104da7 2009-07-21 16:10:38,991 DEBUG [Worker1_SocketWorker25] org.teiid.RESOURCE_POOLING - Beginning work with virtual worker Worker1_SocketWorker25 2009-07-21 16:10:38,991 DEBUG [Worker1_SocketWorker25] org.teiid.SESSION - closeSession 3 2009-07-21 16:10:38,992 DEBUG [Worker1_SocketWorker25] org.teiid.BUFFER_MGR - Removing TupleSources for group 3 2009-07-21 16:10:38,992 DEBUG [Worker1_SocketWorker25] org.teiid.TXN_LOG - before cancelTransactions:com.metamatrix.dqp.embedded.services.EmbeddedTransactionService@15d8d75(3,false) 2009-07-21 16:10:38,992 DEBUG [Worker1_SocketWorker25] org.teiid.TXN_LOG - after cancelTransactions : null 2009-07-21 16:10:38,993 DEBUG [Worker1_SocketWorker25] org.teiid.Server - message: MessageHolder: contents=null for request ID:5 2009-07-21 16:10:39,170 DEBUG [New I/O server worker #1-2] org.teiid.Server - Unhandled exception, closing client instance com.metamatrix.common.comm.exception.SingleInstanceCommunicationException: Channel closed at org.teiid.transport.SSLAwareChannelHandler.channelDisconnected(SSLAwareChannelHandler.java:219) at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:130) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:401) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:624) at org.jboss.netty.handler.codec.frame.FrameDecoder.cleanup(FrameDecoder.java:268) at org.jboss.netty.handler.codec.frame.FrameDecoder.channelDisconnected(FrameDecoder.java:182) at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:130) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:401) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:396) at org.jboss.netty.channel.Channels.fireChannelDisconnected(Channels.java:366) at org.jboss.netty.channel.socket.nio.NioWorker.close(NioWorker.java:726) at org.jboss.netty.channel.socket.nio.NioWorker.close(NioWorker.java:371) at org.jboss.netty.channel.socket.nio.NioWorker.readIntoHeapBuffer(NioWorker.java:304) at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:254) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:163) at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:78) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) -- 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

15 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-736) MMJDBCSQLTypeInfo incorrectly maps char teiid type to char sql type

by Steven Hawkins (JIRA)

MMJDBCSQLTypeInfo incorrectly maps char teiid type to char sql type ------------------------------------------------------------------- Key: TEIID-736 URL: https://jira.jboss.org/jira/browse/TEIID-736 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 6.2.0 The teiid char type should actually map to varchar and the char sql type should map to our string type. -- 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

15 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-742) Nested properties are not correctly being resolved

by Ramesh Reddy (JIRA)

Nested properties are not correctly being resolved -------------------------------------------------- Key: TEIID-742 URL: https://jira.jboss.org/jira/browse/TEIID-742 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 6.1.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 A property that is using the ${teiid.home} in the connector binding property is not being resolved correctly when the connector is started. The issues found that 1) PropertiesUtils.resoveNestedProperties method silently swallows un-resolved property 2) PropertiesUtils.resoveNestedProperties does un-necessary cloning of the properties object 3) System properties can not be nested -- 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

15 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-743) Excessive cloning of connector binding properties

by Ramesh Reddy (JIRA)

Excessive cloning of connector binding properties ------------------------------------------------- Key: TEIID-743 URL: https://jira.jboss.org/jira/browse/TEIID-743 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 6.1.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 The connector binding properties are excessively being cloned at each level, which leads to lot if memory overhead. In the case of handling the hundreds of connector bindings this will result in OOM. 1) The connector binding properties does not have access to the configuration level properties (properties in deploy.properties) 2) Default property mechanism not being used. When you create a properties object like "new Properties(defaultProps)", the defaultProps object properties are not copied into the container properties object, nor they can be changed. They can be overridden, but will not affect the defaultProps object. 3) Properties not being cached For (2) connector binding properties need to be layered such that the connector binding property tree object will look like system properties |-------------------------> deploy.properties |------------------> Connector Type Properties |----------------------------> Connector Binding Properties For (3) since up to the "Connector Type Properties", are common for a given Connector Binding they should be cached to minimize the memory overhead. -- 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

15 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-737) Upgrade Log4J to 1.2.15 version

by Ramesh Reddy (JIRA)

Upgrade Log4J to 1.2.15 version ------------------------------- Key: TEIID-737 URL: https://jira.jboss.org/jira/browse/TEIID-737 Project: Teiid Issue Type: Task Components: Common Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 Current verson 1.2.8 does not create the log directory automatically if this does not exists. This is fixed in bug https://issues.apache.org/bugzilla/show_bug.cgi?id=9150 Only concern is JBoss Cache, JBoss Transaction use the 1.2.8 version, hopefully it would not cause any issues. -- 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

15 years, 4 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2009