September 2009 - teiid-issues - Jboss List Archives

[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

16 years, 6 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

16 years, 6 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

16 years, 6 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

16 years, 6 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

16 years, 6 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

16 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-732) Rename the teiid-embedded project to teiid-runtime

by Ramesh Reddy (JIRA)

Rename the teiid-embedded project to teiid-runtime -------------------------------------------------- Key: TEIID-732 URL: https://jira.jboss.org/jira/browse/TEIID-732 Project: Teiid Issue Type: Task Components: Common Affects Versions: 6.1.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 Rename the "teiid-embedded" project to "teiid-runtime" also, rename kit "teiid-embedded" to just "teiid" -- 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

16 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-733) ConcurrentModificationException in SessionMonitor

by Ted Jones (JIRA)

ConcurrentModificationException in SessionMonitor ------------------------------------------------- Key: TEIID-733 URL: https://jira.jboss.org/jira/browse/TEIID-733 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.1.0 Reporter: Ted Jones Assignee: Steven Hawkins While running a Seam CRUD Web App against Teiid, I am seeing the following intermittent error: 14:00:51,806 ERROR [STDERR] Exception in thread "SessionMonitor" 14:00:51,814 ERROR [STDERR] java.util.ConcurrentModificationException 14:00:51,815 ERROR [STDERR] at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) 14:00:51,815 ERROR [STDERR] at java.util.HashMap$ValueIterator.next(HashMap.java:822) 14:00:51,815 ERROR [STDERR] at com.metamatrix.platform.security.session.service.SessionServiceImpl.monitorSessions(SessionServiceImpl.java:97) 14:00:51,815 ERROR [STDERR] at com.metamatrix.platform.security.session.service.SessionServiceImpl.access$000(SessionServiceImpl.java:71) 14:00:51,815 ERROR [STDERR] at com.metamatrix.platform.security.session.service.SessionServiceImpl$1.run(SessionServiceImpl.java:340) 14:00:51,815 ERROR [STDERR] at java.util.TimerThread.mainLoop(Timer.java:512) 14:00:51,815 ERROR [STDERR] at java.util.TimerThread.run(Timer.java:462) 14:02:55,126 ERROR [STDERR] Exception in thread "Worker10" 14:02:55,135 ERROR [STDERR] java.lang.NullPointerException 14:02:55,135 ERROR [STDERR] at com.metamatrix.cache.jboss.JBossCache.getChild(JBossCache.java:145) 14:02:55,135 ERROR [STDERR] at org.teiid.dqp.internal.cache.DQPContextCache.removeRequestScopedCache(DQPContextCache.java:60) 14:02:55,135 ERROR [STDERR] at org.teiid.dqp.internal.process.DQPCore.removeRequest(DQPCore.java:304) 14:02:55,135 ERROR [STDERR] at org.teiid.dqp.internal.process.RequestWorkItem.attemptClose(RequestWorkItem.java:357) 14:02:55,135 ERROR [STDERR] at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:247) 14:02:55,135 ERROR [STDERR] at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44) 14:02:55,135 ERROR [STDERR] at com.metamatrix.common.queue.WorkerPoolFactory$StatsCapturingSharedThreadPoolExecutor$1.run(WorkerPoolFactory.java:211) 14:02:55,135 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 14:02:55,135 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 14:02:55,135 ERROR [STDERR] 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

16 years, 6 months

3
8
0 / 0

[JBoss JIRA] Created: (TEIID-731) NPE when trying to execute a query through the LDAP connector

by Paul Nittel (JIRA)

NPE when trying to execute a query through the LDAP connector ------------------------------------------------------------- Key: TEIID-731 URL: https://jira.jboss.org/jira/browse/TEIID-731 Project: Teiid Issue Type: Bug Components: LDAP Connector Affects Versions: 6.2.0 Environment: fedora 10, jdk 1.6, Designer circa early July Reporter: Paul Nittel Assignee: Steven Hawkins Attachments: LdapConnectorProject.zip Another of the Genentech test VDBs uses the LDAP connector. after modeling everything and creating the bindings, here's the exception I received when I tried a query: Error 2009-07-21 11:13:54.314 Error processing query com.metamatrix.jdbc.MMSQLException: com.metamatrix.api.exception.MetaMatrixComponentException at com.metamatrix.jdbc.MMSQLException.create(MMSQLException.java:82) at com.metamatrix.jdbc.MMSQLException.create(MMSQLException.java:63) at com.metamatrix.jdbc.MMStatement.executeSql(MMStatement.java:433) at com.metamatrix.jdbc.MMStatement.execute(MMStatement.java:328) at net.sourceforge.sqlexplorer.sqlpanel.SqlExecProgress.processQuery(SqlExecProgress.java:192) at net.sourceforge.sqlexplorer.sqlpanel.SqlExecProgress.run(SqlExecProgress.java:121) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Caused by: [MetaMatrixComponentException] 1 [NullPointerException] at org.teiid.dqp.internal.process.DataTierTupleSource.switchBatch(DataTierTupleSource.java:128) at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:89) at com.metamatrix.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:136) at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:257) at com.metamatrix.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:110) at com.metamatrix.query.processor.QueryProcessor.process(QueryProcessor.java:160) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:264) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:210) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44) at com.metamatrix.common.queue.WorkerPoolFactory$StatsCapturingSharedThreadPoolExecutor$1.run(WorkerPoolFactory.java:211) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Unknown Source) at com.metamatrix.connector.ldap.LDAPConnection.initializeLDAPContext(LDAPConnection.java:126) at com.metamatrix.connector.ldap.LDAPConnection.<init>(LDAPConnection.java:77) at com.metamatrix.connector.ldap.LDAPConnector.getConnection(LDAPConnector.java:58) at org.teiid.dqp.internal.datamgr.impl.ConnectorWrapper.getConnectionDirect(ConnectorWrapper.java:67) at org.teiid.dqp.internal.datamgr.impl.ConnectorWrapper.getConnection(ConnectorWrapper.java:62) at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.createConnection(ConnectorWorkItem.java:140) at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.createExecution(ConnectorWorkItem.java:288) at org.teiid.dqp.internal.datamgr.impl.SynchConnectorWorkItem.createExecution(SynchConnectorWorkItem.java:100) at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.process(ConnectorWorkItem.java:152) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44) at org.teiid.dqp.internal.datamgr.impl.SynchConnectorWorkItem.run(SynchConnectorWorkItem.java:69) ... 4 more Pertinent artifacts are attached. -- 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

16 years, 6 months

2
4
0 / 0

[JBoss JIRA] Closed: (TEIID-401) Increase performance of XML-Relational connectors file cache

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-401?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-401. -------------------------------- > Increase performance of XML-Relational connectors file cache > ------------------------------------------------------------ > > Key: TEIID-401 > URL: https://jira.jboss.org/jira/browse/TEIID-401 > Project: Teiid > Issue Type: Feature Request > Components: XML Connector > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: John Doyle > Fix For: 6.1.0 > > > I-T 248339. XML-Relational File Connector has severe performance issues when forced to use file caching on Linux/Solaris OS. When using only the in-memory cache, the sample query in 248339 takes around 10 seconds. When using the file cache, the query takes around 270 seconds to complete. The sample data file source in 248339 consumes around 25MB of memory, so the default memory cache setting of 16MB forces the file cache to be used. -- 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

16 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2009