June 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-857) MalformedURLException when connecting to teiid vdb.

by John Doyle (JIRA)

MalformedURLException when connecting to teiid vdb. --------------------------------------------------- Key: TEIID-857 URL: https://jira.jboss.org/jira/browse/TEIID-857 Project: Teiid Issue Type: Bug Components: Embedded Affects Versions: 6.2.0 Environment: Teiid 6.2 embedded using the filepath configuration. Reporter: John Doyle Assignee: Steven Hawkins I'm not getting a log file from Teiid. I've just dropped a VDB into an unmodified 6.2 image and get the following when connecting. log4j:ERROR Could not parse url [mmfile:/home/jdoyle/NotBackedUp/teiid-6.2.0/deploy/log4j.xml]. java.net.MalformedURLException: unknown protocol: mmfile at java.net.URL.<init>(URL.java:574) at java.net.URL.<init>(URL.java:464) at java.net.URL.<init>(URL.java:413) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:650) at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:186) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:771) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:225) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:180) at org.apache.log4j.xml.DOMConfigurator$2.parse(DOMConfigurator.java:612) at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:711) at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:618) at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:470) at org.apache.log4j.LogManager.<clinit>(LogManager.java:122) at org.apache.log4j.Logger.getLogger(Logger.java:104) at com.metamatrix.jdbc.Log4JUtil.getLogger(Log4JUtil.java:91) at com.metamatrix.jdbc.LogConfigurationProvider$Log4JLogConfiguration.isEnabled(LogConfigurationProvider.java:74) at com.metamatrix.common.log.LogManager.isMessageToBeRecorded(LogManager.java:358) at com.metamatrix.common.log.LogManager.logMessage(LogManager.java:364) at com.metamatrix.common.log.LogManager.logInfo(LogManager.java:214) at com.metamatrix.dqp.embedded.DQPEmbeddedPlugin.logInfo(DQPEmbeddedPlugin.java:71) at com.metamatrix.dqp.embedded.services.EmbeddedConfigurationService.initializeService(EmbeddedConfigurationService.java:975) at com.metamatrix.dqp.embedded.services.EmbeddedBaseDQPService.initialize(EmbeddedBaseDQPService.java:60) at org.teiid.dqp.internal.process.DQPCore.start(DQPCore.java:615) ... -- 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

14 years, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (TEIID-937) Request ability on client jar to set the ConnectionRetryCount and Delay

by Debbie Steigner (JIRA)

Request ability on client jar to set the ConnectionRetryCount and Delay ----------------------------------------------------------------------- Key: TEIID-937 URL: https://jira.jboss.org/jira/browse/TEIID-937 Project: Teiid Issue Type: Feature Request Components: JDBC Driver Reporter: Debbie Steigner Assignee: Steven Hawkins Fix For: 7.0 In the current version of MetaMatrix, our client jdbc driver (metamatrix-jdbc.jar) has a hard-coded connection retry count of 3. Can this property be exposed so the customer can set the ConnectionRetryCount and the ConnectionRetryDelay. -- 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

14 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (TEIID-396) Authorization Provider can not deleted using the Admin API

by Ramesh Reddy (JIRA)

Authorization Provider can not deleted using the Admin API ---------------------------------------------------------- Key: TEIID-396 URL: https://jira.jboss.org/jira/browse/TEIID-396 Project: Teiid Issue Type: Feature Request Components: Console, Server Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 6.1.0 Currently the addAuthorizationProvider is supported through the Admin API, however there is no corresponding "remove". This needs to be provided. -- 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

14 years, 7 months

3
6
0 / 0

[JBoss JIRA] Closed: (TEIID-409) server port number should be checked for availability when creating a second mmprocess

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-409?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-409. ------------------------------- > server port number should be checked for availability when creating a second mmprocess > -------------------------------------------------------------------------------------- > > Key: TEIID-409 > URL: https://jira.jboss.org/browse/TEIID-409 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.x > Reporter: Marc Shirley > Fix For: 7.0 > > > Creating a second process on a server increments the port number by one from the primary process. This port number does not seem to be checked for availability, and so, if the second process's port is already in use, then status of the second process will be unreliable (it flickers between "Running" and "Not Started" states). One or more of the below actions should be taken: > 1) A check should be added to the process of adding a second process to detect whether a port is already in use. > 2) A KI entry should be made to cover the issue. > 3) Steps should be added to the Console User's Guide and/or Server Tuning Guide to advise the reader to make sure the port assigned to the second process is not in use by another application. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIID-408) logging controls/maintenance capabilities for transaction logging

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-408?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-408. ------------------------------- > logging controls/maintenance capabilities for transaction logging > ----------------------------------------------------------------- > > Key: TEIID-408 > URL: https://jira.jboss.org/browse/TEIID-408 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.x > Reporter: Marc Shirley > Fix For: 6.2.0 > > > case 6664 > some type of control or maintenance capabilities should be added to Console to control the logging of transactions, metamatrix commands, and data source commands. This could even be the ability to disable database logging specifically for these commands. Currently, if these are turned on, the database can be filled up with these messages, and will have to be manually purged or maintained. The case that triggered this request had the following sizes of log tables: > TX_SRCCMDLOG - 37MB > TX_SQL_PK - 59MB > TX_SQL - 367MB > TX_MMXCMDLOG - 448MB -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIID-1095) Can 'java.net.SocketTimeoutException: Read timed out' be moved to WARNING instead of ERROR level

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-1095?page=com.atlassian.jira.plugin.s... ] Steve Hawkins closed TEIID-1095. -------------------------------- > Can 'java.net.SocketTimeoutException: Read timed out' be moved to WARNING instead of ERROR level > ------------------------------------------------------------------------------------------------ > > Key: TEIID-1095 > URL: https://jira.jboss.org/browse/TEIID-1095 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > Since this ERROR simply indicates that a network level socket error has occurred and it is nothing to be alarmed about unless you are experiencing client-side errors indicating a connection has been broken, can it be changed to a WARNING. > Error message: > ERROR [CONTROLLER] SocketListener.run Error creating client connection. > java.net.SocketTimeoutException: Read timed out -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIID-137) Remove the HTTPClient Usage from the XML Connector and use the Common XML Connector

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-137?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-137. ------------------------------- > Remove the HTTPClient Usage from the XML Connector and use the Common XML Connector > ----------------------------------------------------------------------------------- > > Key: TEIID-137 > URL: https://jira.jboss.org/browse/TEIID-137 > Project: Teiid > Issue Type: Sub-task > Components: XML Connector > Affects Versions: 6.0.0 > Reporter: Ted Jones > Assignee: Ramesh Reddy > Fix For: 7.0 > > > Need to remove the HTTPClient usage from the XML Connector and use the Axis client in the Common XML Connector to reduce download size -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1068) Provide a single Connector, that represents the DS and Teiid Connector for JDBC sources.

by Ramesh Reddy (JIRA)

Provide a single Connector, that represents the DS and Teiid Connector for JDBC sources. ---------------------------------------------------------------------------------------- Key: TEIID-1068 URL: https://jira.jboss.org/jira/browse/TEIID-1068 Project: Teiid Issue Type: Sub-task Components: JDBC Connector, Query Engine Affects Versions: 7.0 Environment: 7.0 M3 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Critical Fix For: 7.0 Currently for dealing with relational databases Teiid requires two separate JCA components. 1. Data source 2. Teiid Connection Factory to the Data Source above Teiid query engine talks to 2, which in turn talks to 1. In this scenario, 2 provides the query translation facilities + acts as the proxy connection for the 1. Complications arise, as 2 is exposed as managed connection as well as 1. To be transactionally correct the both managed connections must behave like one. Also, there is burden on the user to create two separate "-ds.xml" files to define a single Teiid Connector. Since for 2, JCA behaviour is not needed, this can be removed. Provide a way to define a single "-ds.xml" file that will create a data source as well as the connection factory. Make the connection factory a stateful connection, which holds on to the data source connection. Provide templates to create such CF + DS in single step. -- 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

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Closed: (TEIID-972) Update sessionservice properties

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-972?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-972. ------------------------------- > Update sessionservice properties > -------------------------------- > > Key: TEIID-972 > URL: https://jira.jboss.org/browse/TEIID-972 > Project: Teiid > Issue Type: Task > Components: Documentation, Server > Affects Versions: 7.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The session service was simplified, we need to remove properties that are no longer in use. Only the following are still in use: > security.session.terminationHandlers > metamatrix.session.max.connections > metamatrix.session.time.limit > metamatrix.session.sessionMonitor.ActivityInterval -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-752) Errors with bulk updates

by Steven Hawkins (JIRA)

Errors with bulk updates ------------------------ Key: TEIID-752 URL: https://jira.jboss.org/jira/browse/TEIID-752 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 6.2.0 The bulk update logic is not correct JDBCBaseExecution is calling addBatch too many times, and JDBCUpdateExecution is determining the multivalued row count incorrectly (ClassCastException). -- 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

14 years, 7 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2010