March 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-418) Server Extensions should be loaded from a Extension classpath

by Ramesh Reddy (JIRA)

Server Extensions should be loaded from a Extension classpath ------------------------------------------------------------- Key: TEIID-418 URL: https://jira.jboss.org/jira/browse/TEIID-418 Project: Teiid Issue Type: Feature Request Components: Build/Kits, Common, Server Affects Versions: 6.x Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.1.0 Currently the MembershipDomain, CustomTracker load from libraries which are defined as part of the boot class path, these need to be loaded from the extension classpath, so that they can be added or removed without server re-start. -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-412) The Postgres driver postgresql-8.1-404.jdbc3.jar isn't supported due to it's no 1.6 fully compatible

by Van Halbert (JIRA)

The Postgres driver postgresql-8.1-404.jdbc3.jar isn't supported due to it's no 1.6 fully compatible ---------------------------------------------------------------------------------------------------- Key: TEIID-412 URL: https://jira.jboss.org/jira/browse/TEIID-412 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.0.0 Environment: Using Postgres repository Reporter: Van Halbert Assignee: Steven Hawkins The following exception is thrown due to the driver 1.6 incompatibility: Caused by: java.lang.AbstractMethodError: org.postgresql.jdbc3.Jdbc3Connection.isValid(I)Z 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.common.jdbc.SimplePooledConnectionSource$ConnectionProxy.invoke(SimplePooledConnectionSource.java:83) at $Proxy0.isValid(Unknown Source) at com.metamatrix.common.jdbc.SimplePooledConnectionSource.getConnection(SimplePooledConnectionSource.java:121) at com.metamatrix.common.connection.jdbc.JDBCMgdResourceConnection.openConnection(JDBCMgdResourceConnection.java:72) at com.metamatrix.common.connection.ManagedConnection.open(ManagedConnection.java:137) at com.metamatrix.common.connection.TransactionMgr.getReadTransaction(TransactionMgr.java:73) -- 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, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (TEIID-446) ConfigurationChangeEvent is not visible

by Ramesh Reddy (JIRA)

ConfigurationChangeEvent is not visible --------------------------------------- Key: TEIID-446 URL: https://jira.jboss.org/jira/browse/TEIID-446 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 6.1.0 ConfigurationChangeEvent is thrown by XMLConfigurationMgr code, however with sequence, initialization of this class, the MessageBus is set to NoOpMessageBus, thus no ConfigurationChangeEvents flow through. ResourceFinder should not return a NoOpMessage -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-445) Threading cleanup

by Steven Hawkins (JIRA)

Threading cleanup ----------------- Key: TEIID-445 URL: https://jira.jboss.org/jira/browse/TEIID-445 Project: Teiid Issue Type: Task Components: Common, Query Engine Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 WorkerPools should expose the ability to schedule tasks (repeated and delayed). This can then be used at the connector layer to replace per connector timers with calls to the connector workerpool via the connectorenvironment. Next the nio and socket server worker threads should be combined. There is very little gain from having them be separate pools - (continuing i/o work while all the socket server workers are busy probably means that the workers should be increased, rather than queuing the server work). Finally it would nice to have a workerpool implementation that provides a shared thread pool so that connector specific pool sizings are less of consideration. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-450) Product Name not Set for Server (Integration Server)

by Ted Jones (JIRA)

Product Name not Set for Server (Integration Server) ---------------------------------------------------- Key: TEIID-450 URL: https://jira.jboss.org/jira/browse/TEIID-450 Project: Teiid Issue Type: Bug Components: Server Reporter: Ted Jones Assignee: Ted Jones Fix For: 6.0.0 The "Product Name" is not being set when a client connects to the server (It is being set for AdminAPI). The value that is expected is "Integration Server", but it is currently "null". -- 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, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIID-439) NPE Getting Resource From VDB

by Ted Jones (JIRA)

NPE Getting Resource From VDB ----------------------------- Key: TEIID-439 URL: https://jira.jboss.org/jira/browse/TEIID-439 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.0.0 Reporter: Ted Jones Assignee: Steven Hawkins Fix For: 6.1.0 While attempting to execute System.getUpdatedCharacterVDBResource() to get WSDL from a VDB, I received the following exception: com.metamatrix.jdbc.MMSQLException: Error trying to execute a statement {?=call System.getUpdatedCharacterVDBResource(?,?,?)}. at com.metamatrix.jdbc.MMSQLException.create(MMSQLException.java:75) at com.metamatrix.jdbc.MMCallableStatement.internalExecute(MMCallableStatement.java:394) at com.metamatrix.jdbc.MMPreparedStatement.internalExecuteQuery(MMPreparedStatement.java:225) at com.metamatrix.jdbc.MMPreparedStatement.execute(MMPreparedStatement.java:178) at com.metamatrix.soap.servlet.MMGetVDBResourceServlet.getResource(MMGetVDBResourceServlet.java:283) at com.metamatrix.soap.servlet.MMGetVDBResourceServlet.doPost(MMGetVDBResourceServlet.java:184) at com.metamatrix.soap.servlet.MMGetVDBResourceServlet.doGet(MMGetVDBResourceServlet.java:106) at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) 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:182) 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: com.metamatrix.jdbc.MMSQLException: java.lang.NullPointerException at com.metamatrix.jdbc.MMSQLException.create(MMSQLException.java:82) at com.metamatrix.jdbc.MMSQLException.create(MMSQLException.java:63) at com.metamatrix.jdbc.MMStatement.executeAsynchAndWait(MMStatement.java:815) at com.metamatrix.jdbc.MMStatement.sendRequestMessageAndWait(MMStatement.java:1007) at com.metamatrix.jdbc.MMCallableStatement.internalExecute(MMCallableStatement.java:392) ... 25 more Caused by: java.util.concurrent.ExecutionException: java.lang.NullPointerException at com.metamatrix.common.comm.platform.socket.client.SocketServerInstanceImpl$RemoteInvocationHandler$1.convertResult(SocketServerInstanceImpl.java:267) at com.metamatrix.dqp.client.ResultsFuture.get(ResultsFuture.java:110) at com.metamatrix.common.comm.platform.socket.client.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:310) at com.metamatrix.jdbc.MMStatement.executeAsynchAndWait(MMStatement.java:813) ... 27 more Caused by: java.lang.NullPointerException at com.metamatrix.vdb.runtime.VDBKey.<init>(VDBKey.java:33) at org.teiid.dqp.internal.process.DQPCore$ConnectorCapabilitiesCache.getVDBConnectorCapabilities(DQPCore.java:99) at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:227) 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.common.comm.platform.socket.server.ServerWorkItem.run(ServerWorkItem.java:116) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) ... 1 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-449) JDBC Driver is not setting the default client application name

by Ramesh Reddy (JIRA)

JDBC Driver is not setting the default client application name -------------------------------------------------------------- Key: TEIID-449 URL: https://jira.jboss.org/jira/browse/TEIID-449 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Minor Fix For: 6.1.0 The MMDriver is not setting default property for "ApplicationName". Although, this is not a required property, the server makes use of in creation of SessionId. A default one needs to be set, to mimic the old behaviour. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-448) Error Finding Latest active VDB suing Postgres as a Repository

by Ted Jones (JIRA)

Error Finding Latest active VDB suing Postgres as a Repository -------------------------------------------------------------- Key: TEIID-448 URL: https://jira.jboss.org/jira/browse/TEIID-448 Project: Teiid Issue Type: Bug Reporter: Ted Jones Assignee: Steven Hawkins Attempting to connect to a VDB in Teiid while using a Postgres VDB, I encountered the following exception: [VirtualDatabaseException] ERR.008.006.0035: Error processing query: SELECT VDB_UID,VDB_NM,VDB_VERSION FROM RT_VIRTUAL_DBS WHERE UCASE( VDB_NM )=? AND VDB_VERSION=? AND (VDB_STATUS=3 OR VDB_STATUS=3) 1 [PSQLException]ERROR: function ucase(character varying) does not existv -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-447) Soap data service unable to decode certain characters

by Li Liang (JIRA)

Soap data service unable to decode certain characters ------------------------------------------------------ Key: TEIID-447 URL: https://jira.jboss.org/jira/browse/TEIID-447 Project: Teiid Issue Type: Bug Components: SOAP Services Affects Versions: 6.0.0, 6.x Reporter: Li Liang Assignee: Li Liang Fix For: 6.1.0 DataServiceWebServiceImpl encodes the XML document from the server using default character set. However, the XML document has UFT-8 in its header. If the default character set on the system is not UTF-8, errors may occur for non-English characters during decoding by XML parser, which usually read the processing instructions from the header. This is from customer case 278899. -- 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, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-386) Improve error reporting to NOT include stack traces when appropriate and logging level < Detail

by Paul Nittel (JIRA)

Improve error reporting to NOT include stack traces when appropriate and logging level < Detail ----------------------------------------------------------------------------------------------- Key: TEIID-386 URL: https://jira.jboss.org/jira/browse/TEIID-386 Project: Teiid Issue Type: Feature Request Components: Query Engine Environment: Any and all Reporter: Paul Nittel Assignee: Steven Hawkins The server presently adds stack traces with reckless abandon. It seems like anything that upsets the software yields at least one stack trace. I'd like to propose that "human errors", like parsing SQL statements, return just an error (in the logs, too). If the server is set to log at Detail or Trace, then crank out the stack traces if that's necessary. Logs that show only important stuff are more valuable. (I looked in Teiid and didn't see an entry like this. If it's a dup, that's fine, as long as the stack trace deluge is remedied.) -- 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, 8 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2009