August 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-668) Simplify "Audit Logging"

by Ramesh Reddy (JIRA)

Simplify "Audit Logging" ------------------------ Key: TEIID-668 URL: https://jira.jboss.org/jira/browse/TEIID-668 Project: Teiid Issue Type: Task Components: Common Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 6.2.0 Currently "Audit" logging, is managed by a separate logging framework, this should be no different than logging in Teiid, except that these messages should be placed a well known context. By default the messages can be streamed to Teiid's main log file at INFO level, however there must be an way to user to send these messages to a separate destination. A File based destination must be supported. -- 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-725) Provide a mechanism to shutdown teiid embedded

by Steven Hawkins (JIRA)

Provide a mechanism to shutdown teiid embedded ---------------------------------------------- Key: TEIID-725 URL: https://jira.jboss.org/jira/browse/TEIID-725 Project: Teiid Issue Type: Feature Request Components: Embedded Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 We should introduce a way to fully shutdown embedded. This is useful for deploy.properties or other system resource changes not performed through adminapi to take effect. Derby's approach: http://db.apache.org/derby/papers/DerbyTut/embedded_intro.html#shutdown -- 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-770) Log Manager is not checking if the context is enabled before it logs message

by Ramesh Reddy (JIRA)

Log Manager is not checking if the context is enabled before it logs message ---------------------------------------------------------------------------- Key: TEIID-770 URL: https://jira.jboss.org/jira/browse/TEIID-770 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 6.2.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 Log Manager code is not calling "isMessageToBeRecorded" on all the log calls, so log configuration is not correctly being honoured. -- 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-769) Configure Log4j to use the ASYNC appender

by Ramesh Reddy (JIRA)

Configure Log4j to use the ASYNC appender ----------------------------------------- Key: TEIID-769 URL: https://jira.jboss.org/jira/browse/TEIID-769 Project: Teiid Issue Type: Task Components: Common Affects Versions: 6.1.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 Current Log4J configuration does not use asynchronous appender, thus may reduce the performance by doing the logging chores in the main execution thread. This needs to be handled by a separate thread. -- 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-774) Invalid session terminination after 30 minutes

by Ramesh Reddy (JIRA)

Invalid session terminination after 30 minutes ---------------------------------------------- Key: TEIID-774 URL: https://jira.jboss.org/jira/browse/TEIID-774 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.2.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 A user session is being automatically being terminated after 30 minutes., because max life of session is set to 30 minutes. The configuration file contains wrong "session.timeoutInMilli" value, and default value also set to 10 minutes, which should be in-definite. -- 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-697) Make Admin API changes to support newly added services to runtime engine

by Ramesh Reddy (JIRA)

Make Admin API changes to support newly added services to runtime engine ------------------------------------------------------------------------ Key: TEIID-697 URL: https://jira.jboss.org/jira/browse/TEIID-697 Project: Teiid Issue Type: Sub-task Components: Common, Embedded, Server Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 With addition of new services to embedded profile, the Admin API methods needs to modified to fit the needs. Also, since Server and Embedded platform are going to be supported based on the current embedded runtime, the API methods need to consolidated from previous version. -- 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
9
0 / 0

[JBoss JIRA] Created: (TEIID-763) Exceptions from cache under load

by Steven Hawkins (JIRA)

Exceptions from cache under load -------------------------------- Key: TEIID-763 URL: https://jira.jboss.org/jira/browse/TEIID-763 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.2.0 The following exceptions happen occasional under load. These exceptions are mostly cosmetic though, since they are happening only during removal. Exception in thread "Worker5" java.lang.NullPointerException at com.metamatrix.cache.jboss.JBossCache.getChild(JBossCache.java:145) at org.teiid.dqp.internal.cache.DQPContextCache.removeRequestScopedCache(DQPContextCache.java:63) at org.teiid.dqp.internal.process.DQPCore.removeRequest(DQPCore.java:303) at org.teiid.dqp.internal.process.RequestWorkItem.attemptClose(RequestWorkItem.java:357) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:247) 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(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Exception in thread "Worker0" org.jboss.cache.NodeNotValidException: Node /Teiid/Scoped-Cache is not valid. Perhaps it has been moved or removed. at org.jboss.cache.invocation.NodeInvocationDelegate.assertValid(NodeInvocationDelegate.java:527) at org.jboss.cache.invocation.NodeInvocationDelegate.assertValid(NodeInvocationDelegate.java) at org.jboss.cache.invocation.NodeInvocationDelegate.getChild(NodeInvocationDelegate.java:360) at org.jboss.cache.invocation.NodeInvocationDelegate.getChild(NodeInvocationDelegate.java) at com.metamatrix.cache.jboss.JBossCache.getChild(JBossCache.java:145) at com.metamatrix.cache.jboss.JBossCache.getChild(JBossCache.java) at org.teiid.dqp.internal.cache.DQPContextCache.removeRequestScopedCache(DQPContextCache.java:63) at org.teiid.dqp.internal.cache.DQPContextCache.removeRequestScopedCache(DQPContextCache.java) at org.teiid.dqp.internal.process.DQPCore.removeRequest(DQPCore.java:303) at org.teiid.dqp.internal.process.DQPCore.removeRequest(DQPCore.java) at org.teiid.dqp.internal.process.RequestWorkItem.attemptClose(RequestWorkItem.java:357) at org.teiid.dqp.internal.process.RequestWorkItem.attemptClose(RequestWorkItem.java) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:247) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java) at com.metamatrix.common.queue.WorkerPoolFactory$StatsCapturingSharedThreadPoolExecutor$1.run(WorkerPoolFactory.java:211) at com.metamatrix.common.queue.WorkerPoolFactory$StatsCapturingSharedThreadPoolExecutor$1.run(WorkerPoolFactory.java) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 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
6
0 / 0

[JBoss JIRA] Created: (TEIID-779) Move the tests from the jbedsp-test-embedded project to the teiid communitiy

by Van Halbert (JIRA)

Move the tests from the jbedsp-test-embedded project to the teiid communitiy ---------------------------------------------------------------------------- Key: TEIID-779 URL: https://jira.jboss.org/jira/browse/TEIID-779 Project: Teiid Issue Type: Sub-task Reporter: Van Halbert Fix For: 6.2.0 Move the tests from the jbedsp-test-embedded project to the teiid communitiy -- 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-786) Minor performance enhancements

by Ramesh Reddy (JIRA)

Minor performance enhancements ------------------------------ Key: TEIID-786 URL: https://jira.jboss.org/jira/browse/TEIID-786 Project: Teiid Issue Type: Quality Risk Affects Versions: 6.2.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 This used as bucket for couple of minor performance enhancements in the Teiid project. -- 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-791) M2 build getting NPE when connecting to VDB

by Paul Nittel (JIRA)

M2 build getting NPE when connecting to VDB ------------------------------------------- Key: TEIID-791 URL: https://jira.jboss.org/jira/browse/TEIID-791 Project: Teiid Issue Type: Bug Environment: 6.2.0 M2, fedora 10, Java build 1.6.0_11-b03 Reporter: Paul Nittel Assignee: Steven Hawkins I found I get this NPE when connecting to the admin VDB. I see this using both a simple JDBC test tool and AdminShell. 2009-08-18 10:07:51,957 ERROR [Worker0_SocketWorker1] org.teiid.ADMIN - Unexpected exception for session 0 java.lang.NullPointerException at com.metamatrix.jdbc.EmbeddedConnectionFactoryImpl.getProcess(EmbeddedConnectionFactoryImpl.java:382) at com.metamatrix.dqp.embedded.admin.DQPMonitoringAdminImpl.getProcesses(DQPMonitoringAdminImpl.java:377) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.metamatrix.core.util.MixinProxy.invoke(MixinProxy.java:48) at com.metamatrix.jdbc.EmbeddedConnectionFactoryImpl$1.invoke(EmbeddedConnectionFactoryImpl.java:364) at $Proxy22.getProcesses(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.teiid.transport.AdminAuthorizationInterceptor.invoke(AdminAuthorizationInterceptor.java:122) at $Proxy22.getProcesses(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.teiid.transport.ServerWorkItem.run(ServerWorkItem.java:100) 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) -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2009