May 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-567) Set transactionisolationlevel should not throw an exception

by Steven Hawkins (JIRA)

Set transactionisolationlevel should not throw an exception ----------------------------------------------------------- Key: TEIID-567 URL: https://jira.jboss.org/jira/browse/TEIID-567 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.1.0 Not all clients handle sqlfeaturenotsupportedexceptions, so we should should just ignore sets of transaction isolation level. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-543) CNF when audit logging turned ON

by Ramesh Reddy (JIRA)

CNF when audit logging turned ON -------------------------------- Key: TEIID-543 URL: https://jira.jboss.org/jira/browse/TEIID-543 Project: Teiid Issue Type: Bug Affects Versions: 6.0.0 Reporter: Ramesh Reddy Priority: Minor Fix For: 6.1.0 [AuditDestinationInitFailedException] ERR.014.207.0016: Error Code:ERR.014.207.0016 Message:The specified audit message format class "com.metamatrix.security.audit.format.ReadableAuditMessageFormat" could not be found. 1 [ClassNotFoundException]com.metamatrix.security.audit.format.ReadableAuditMessageFormat at com.metamatrix.platform.security.audit.destination.AbstractAuditDestination.setFormat(AbstractAuditDestination.java:62) at com.metamatrix.platform.security.audit.destination.ConsoleAuditDestination.initialize(ConsoleAuditDestination.java:70) at com.metamatrix.platform.security.audit.AuditManager.initializeDestinations(AuditManager.java:212) at com.metamatrix.platform.security.audit.AuditManager.<init>(AuditManager.java:152) at com.metamatrix.platform.security.authorization.service.AuthorizationServiceImpl.initService(AuthorizationServiceImpl.java:132) at com.metamatrix.platform.service.controller.AbstractService.init(AbstractService.java:143) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.metamatrix.platform.registry.ServiceRegistryBinding$StateAwareProxy.invoke(ServiceRegistryBinding.java:60) at $Proxy25.init(Unknown Source) at com.metamatrix.platform.vm.controller.ProcessController.startService(ProcessController.java:747) at com.metamatrix.platform.vm.controller.ProcessController.startService(ProcessController.java:661) at com.metamatrix.platform.vm.controller.ProcessController.startDeployedService(ProcessController.java:430) at com.metamatrix.platform.vm.controller.ProcessController.start(ProcessController.java:318) at com.metamatrix.common.comm.platform.socket.SocketVMController.start(SocketVMController.java:79) at com.metamatrix.server.Main.launchServer(Main.java:115) at com.metamatrix.server.Main.main(Main.java:98) Caused by: java.lang.ClassNotFoundException: com.metamatrix.security.audit.format.ReadableAuditMessageFormat at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at com.metamatrix.platform.security.audit.destination.AbstractAuditDestination.setFormat(AbstractAuditDestination.java:59) ... 18 more -- 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

1
2
0 / 0

[JBoss JIRA] Closed: (TEIID-206) Create a project for federate-server-api

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-206?page=com.atlassian.jira.plug... ] Ramesh Reddy closed TEIID-206. ------------------------------ Resolution: Rejected Will re-access after couple releases if this is really necessary, or just the documentation is sufficient. > Create a project for federate-server-api > ---------------------------------------- > > Key: TEIID-206 > URL: https://jira.jboss.org/jira/browse/TEIID-206 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 6.1.0 > > > Create new project in the federate svn, "federate-server-api" that contains all the server side extension APIs that users/customers can extend to plugin into the server. These APIs are > - Membership API > - Command Logging API > - Logging API -- 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

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-558) Failed to load UDF in Embedded when running with MMROFILE protocol.

by Ramesh Reddy (JIRA)

Failed to load UDF in Embedded when running with MMROFILE protocol. ------------------------------------------------------------------- Key: TEIID-558 URL: https://jira.jboss.org/jira/browse/TEIID-558 Project: Teiid Issue Type: Bug Components: Embedded Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.1.0 When the UDF is added through the Teiid Designer, UDF is added as extension module. However, since Designer uses MMROFILE protocol, it never deletes the UDF extension file, thus trying to add a new one, finds a old one in the configuration and fails to add and aborts the operation. -- 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

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-472) Teiid Embedded unable to login to JDBC data sources requiring username/password

by Paul Nittel (JIRA)

Teiid Embedded unable to login to JDBC data sources requiring username/password ------------------------------------------------------------------------------- Key: TEIID-472 URL: https://jira.jboss.org/jira/browse/TEIID-472 Project: Teiid Issue Type: Bug Components: Embedded Affects Versions: 6.0.0 Environment: fedora 10, Teiid Designer 040709, Teiid 6.0.0 Reporter: Paul Nittel Assignee: Steven Hawkins I took the PartsSupplier_VDB from the Designer and tried to use it in Teiid Embedded. Using a simple JDBC query tool, I was unable to login to the data sources (Oracle and SQL Server). Working with Ramesh, we found we could edit the configuration.def inside the VDB and edit the mm-encrypted password to plain text and it would work. As an alternative, we could use the configuration.xml file from the Designer and that worked. Ramesh will fill in the technical details... -- 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

2
8
0 / 0

[JBoss JIRA] Created: (TEIID-564) getMetaData call on the Connection object resulting in exception

by Ramesh Reddy (JIRA)

getMetaData call on the Connection object resulting in exception ---------------------------------------------------------------- Key: TEIID-564 URL: https://jira.jboss.org/jira/browse/TEIID-564 Project: Teiid Issue Type: Bug Components: Embedded Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 6.1.0 org.jboss.util.NestedSQLException: Error; - nested throwable: (java.lang.AbstractMethodError: com.metamatrix.jdbc.MMConnection.getBaseDriver()Lcom/metamatrix/jdbc/BaseDriver;) at org.jboss.resource.adapter.jdbc.WrappedConnection.checkException(WrappedConnection.java:557) at org.jboss.resource.adapter.jdbc.WrappedConnection.getMetaData(WrappedConnection.java:358) at JDBCQueryServlet.doPost(JDBCQueryServlet.java:65) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.AbstractMethodError: com.metamatrix.jdbc.MMConnection.getBaseDriver()Lcom/metamatrix/jdbc/BaseDriver; at com.metamatrix.jdbc.MMConnection.getMetaData(MMConnection.java:495) at org.jboss.resource.adapter.jdbc.WrappedConnection.getMetaData(WrappedConnection.java:354) ... 21 more -- 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

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-559) MMSQLException querying with SQL Server XA Connector

by Barry LaFond (JIRA)

MMSQLException querying with SQL Server XA Connector ---------------------------------------------------- Key: TEIID-559 URL: https://jira.jboss.org/jira/browse/TEIID-559 Project: Teiid Issue Type: Bug Reporter: Barry LaFond Assignee: Steven Hawkins E2E Update through Virtual Groups Test Script was successful with INSERT, UPDATE, DELETE through Oracle connector (Native Driver) However updates are failing with SQL Server XA Connector. (jdbc:sqlserver://slntdb02.mm.atl2.redhat.com:1433;databasename=customeraccounts) com.metamatrix.jdbc.MMSQLException: Failed to enlist the XAResource in Transaction. 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:424) at com.metamatrix.jdbc.MMStatement.execute(MMStatement.java:326) 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: [XATransactionException]Failed to enlist the XAResource in Transaction. at org.teiid.dqp.internal.transaction.TransactionServerImpl.enlist(TransactionServerImpl.java:561) at sun.reflect.GeneratedMethodAccessor260.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at com.metamatrix.common.log.LogManager$1.invoke(LogManager.java:407) at $Proxy6.enlist(Unknown Source) at org.teiid.dqp.internal.datamgr.impl.SynchConnectorWorkItem.enlistResource(SynchConnectorWorkItem.java:118) at org.teiid.dqp.internal.datamgr.impl.SynchConnectorWorkItem.createExecution(SynchConnectorWorkItem.java:101) at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.process(ConnectorWorkItem.java:151) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44) at org.teiid.dqp.internal.datamgr.impl.SynchConnectorWorkItem.run(SynchConnectorWorkItem.java:69) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) -- 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

2
7
0 / 0

[JBoss JIRA] Created: (TEIID-565) default logging should be to java logging

by Steven Hawkins (JIRA)

default logging should be to java logging ----------------------------------------- Key: TEIID-565 URL: https://jira.jboss.org/jira/browse/TEIID-565 Project: Teiid Issue Type: Quality Risk Components: Common Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 All non-main application system outs should be converted to java logs and the default logwriter should be to java. Also the basic log configuration should default to warning. The STDOUT target for embedded logging should be removed, as that can be controlled through java logging. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-562) JBoss AS produces error after querying using Teiid Embedded Datasource about not closing the connection.

by Ramesh Reddy (JIRA)

JBoss AS produces error after querying using Teiid Embedded Datasource about not closing the connection. -------------------------------------------------------------------------------------------------------- Key: TEIID-562 URL: https://jira.jboss.org/jira/browse/TEIID-562 Project: Teiid Issue Type: Bug Components: Embedded Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 6.1.0 2:57:02,080 INFO [CachedConnectionManager] Closing a connection for you. Please close them yourself: org.jboss.resource.adapter.jdbc.WrappedConnection@17951b0 java.lang.Throwable: STACKTRACE at org.jboss.resource.connectionmanager.CachedConnectionManager.registerConnection(CachedConnectionManager.java:290) at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:417) at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:842) at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88) at JDBCQueryServlet.doPost(JDBCQueryServlet.java:63) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) 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

1
1
0 / 0

[JBoss JIRA] Resolved: (TEIID-376) Resources: SSL: Parameters are in a weird order and not terribly clear as to what is what

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-376?page=com.atlassian.jira.plug... ] Van Halbert resolved TEIID-376. ------------------------------- Resolution: Done > Resources: SSL: Parameters are in a weird order and not terribly clear as to what is what > ----------------------------------------------------------------------------------------- > > Key: TEIID-376 > URL: https://jira.jboss.org/jira/browse/TEIID-376 > Project: Teiid > Issue Type: Task > Components: Console > Affects Versions: 6.1.0 > Environment: All > Reporter: Paul Nittel > Assignee: Van Halbert > Priority: Optional > Fix For: 6.1.1 > > Attachments: SslParameters.png > > > The Resources panel of the Console covers a number of resources, one of which is SSL. The test script I'm executing dictates I change the keystore and its password. There are two password fields, one labeled "Password" and the other labeled "TrustStore Password". > Neither password field is adjacent to its associated file's field. > Please reorder these properties so they make sense and relabel the keystore's password field to be "KeyStore Password". > I'll leave it up to someone else to determine if these things are TrustStore vs Truststore and KeyStore versus Keystore. Whichever wins, they should be consistent. > See attached screenshot. -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2009