November 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-1853) Salesforce Translator doesnt handle Time types

by Van Halbert (Created) (JIRA)

Salesforce Translator doesnt handle Time types ---------------------------------------------- Key: TEIID-1853 URL: https://issues.jboss.org/browse/TEIID-1853 Project: Teiid Issue Type: Bug Components: Salesforce Connector Affects Versions: 7.6 Reporter: Mark Drilling Assignee: Steven Hawkins Query the BusinessHours table imported from Salesforce, which contains columns with 'time' datatype. For example, the query: SELECT Name,CreatedDate,MondayStartTime FROM SFTest.salesforce.BusinessHours Results in: Error Code:ERR.003.029.0025 Message:Failed to transform String to Time. Expected format = hh:mm:ss for 08:00:00.000Z It looks like the code in QueryExecutionImpl.getCellDatum needs to handle translation of the salesforce time format -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1849) enabledCipherSuites property gives error on startup of server

by Ramesh Reddy (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1849?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-1849. --------------------------------- Resolution: Done Jboss beans framework in the presence of the "get" method it will look for same signature based "set" method. In the absence of "get" method, it will use the "set" method signature. Code had mixed set of in parameter in "set" and return on "get" > enabledCipherSuites property gives error on startup of server > ------------------------------------------------------------- > > Key: TEIID-1849 > URL: https://issues.jboss.org/browse/TEIID-1849 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.4.1 > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 7.6 > > > Trying to implement this new feature in 5.2: https://issues.jboss.org/browse/SOA-3448 > Setting the new enabledCipherSuites property in JdbcSslConfiguration section gives the below error on startup of the server: > java.lang.IllegalArgumentException: Property is not writable: enabledCipherSuites for org.teiid.transport.SSLConfiguration -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1849) enabledCipherSuites property gives error on startup of server

by Ramesh Reddy (Assigned) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1849?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-1849: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > enabledCipherSuites property gives error on startup of server > ------------------------------------------------------------- > > Key: TEIID-1849 > URL: https://issues.jboss.org/browse/TEIID-1849 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.4.1 > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 7.6 > > > Trying to implement this new feature in 5.2: https://issues.jboss.org/browse/SOA-3448 > Setting the new enabledCipherSuites property in JdbcSslConfiguration section gives the below error on startup of the server: > java.lang.IllegalArgumentException: Property is not writable: enabledCipherSuites for org.teiid.transport.SSLConfiguration -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1849) enabledCipherSuites property gives error on startup of server

by Van Halbert (Assigned) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1849?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-1849: ---------------------------------- Assignee: Steven Hawkins (was: Van Halbert) > enabledCipherSuites property gives error on startup of server > ------------------------------------------------------------- > > Key: TEIID-1849 > URL: https://issues.jboss.org/browse/TEIID-1849 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.4.1 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 7.6 > > > Trying to implement this new feature in 5.2: https://issues.jboss.org/browse/SOA-3448 > Setting the new enabledCipherSuites property in JdbcSslConfiguration section gives the below error on startup of the server: > java.lang.IllegalArgumentException: Property is not writable: enabledCipherSuites for org.teiid.transport.SSLConfiguration -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1849) enabledCipherSuites property gives error on startup of server

by Van Halbert (Moved) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1849?page=com.atlassian.jira.plugin... ] Van Halbert moved SOA-3622 to TEIID-1849: ----------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1849 (was: SOA-3622) Affects Version/s: 7.4.1 (was: 5.2.0 GA) Component/s: Server (was: EDS) Security: (was: Public) Fix Version/s: 7.6 (was: 5.3.0 GA) > enabledCipherSuites property gives error on startup of server > ------------------------------------------------------------- > > Key: TEIID-1849 > URL: https://issues.jboss.org/browse/TEIID-1849 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.4.1 > Reporter: Debbie Steigner > Assignee: Van Halbert > Priority: Blocker > Fix For: 7.6 > > > Trying to implement this new feature in 5.2: https://issues.jboss.org/browse/SOA-3448 > Setting the new enabledCipherSuites property in JdbcSslConfiguration section gives the below error on startup of the server: > java.lang.IllegalArgumentException: Property is not writable: enabledCipherSuites for org.teiid.transport.SSLConfiguration -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1847) Salesforce connector does not report UnexpectedErrorFault exceptions correctly when calling getUpdated

by Steven Hawkins (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1847?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1847: ---------------------------------- Issue Type: Quality Risk (was: Bug) Fix Version/s: 8.0 Priority: Minor (was: Major) Affects Version/s: 6.0.0 Complexity: Low We'll look at unwrapping the ApiFaults rather than just wrapping with resource exceptions. > Salesforce connector does not report UnexpectedErrorFault exceptions correctly when calling getUpdated > ------------------------------------------------------------------------------------------------------ > > Key: TEIID-1847 > URL: https://issues.jboss.org/browse/TEIID-1847 > Project: Teiid > Issue Type: Quality Risk > Components: Salesforce Connector > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Priority: Minor > Labels: salesforce > Fix For: 8.0 > > > When encountering an UnexpectedErrorFault with com.sforce.soap.partner.SoapBindingStub.GetUpdated(), com.metamatrix.connector.salesforce.connection.SalesforceConnection.getUpdated() throws a null error message instead of the message returned from Salesforce. It appears that the getUpdated() method is using java.rmi.RemoteException.getMessage() when it should be using SFDC com.sforce.soap.partner.fault.ApiFault.getExceptionMessage() for "UnexpectedErrorFault" exceptions. Associated stack trace below. > [Salesforce Connector_1246|9725_Worker_106|0] ERROR <CONNECTOR|0> Connector worker process failed for atomic-request=5707647.13.7.333713 > ConnectorException: Status ERROR: com.metamatrix.core code=0 null > at com.metamatrix.connector.salesforce.connection.SalesforceConnection.getUpdated(SalesforceConnection.java:737) > at com.metamatrix.connector.salesforce.execution.GetUpdatedExecutionImpl.execute(GetUpdatedExecutionImpl.java:65) > at com.metamatrix.connector.salesforce.execution.ProcedureExecutionParentImpl.execute(ProcedureExecutionParentImpl.java:86) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processNewRequest(ConnectorWorker.java:275) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.process(ConnectorWorker.java:141) > at com.metamatrix.common.queue.QueueWorker.run(QueueWorker.java:64) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1848) CLONE - Index metadata should not treat cardinality 0 as unknown

by Steven Hawkins (Created) (JIRA)

CLONE - Index metadata should not treat cardinality 0 as unknown ---------------------------------------------------------------- Key: TEIID-1848 URL: https://issues.jboss.org/browse/TEIID-1848 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 8.0 The default cardinality is currently 0, which is treated as unknown, however it would be better if the default were something like -1 instead. This will require introducing a new index file version (so that older vdbs with a value of 0 can be understood as meaning unknown) and updating the teiid/designer metadata defaults for cardinality as -1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1847) Salesforce connector does not report UnexpectedErrorFault exceptions correctly when calling getUpdated

by Van Halbert (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1847?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-1847: ------------------------------------ No, but looking at similar logic in Teiid, GetUpdatedExecutionImpl, its handling the exception in the same manner that's at issue in 5.5.4. > Salesforce connector does not report UnexpectedErrorFault exceptions correctly when calling getUpdated > ------------------------------------------------------------------------------------------------------ > > Key: TEIID-1847 > URL: https://issues.jboss.org/browse/TEIID-1847 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Reporter: Marc Shirley > Labels: salesforce > > When encountering an UnexpectedErrorFault with com.sforce.soap.partner.SoapBindingStub.GetUpdated(), com.metamatrix.connector.salesforce.connection.SalesforceConnection.getUpdated() throws a null error message instead of the message returned from Salesforce. It appears that the getUpdated() method is using java.rmi.RemoteException.getMessage() when it should be using SFDC com.sforce.soap.partner.fault.ApiFault.getExceptionMessage() for "UnexpectedErrorFault" exceptions. Associated stack trace below. > [Salesforce Connector_1246|9725_Worker_106|0] ERROR <CONNECTOR|0> Connector worker process failed for atomic-request=5707647.13.7.333713 > ConnectorException: Status ERROR: com.metamatrix.core code=0 null > at com.metamatrix.connector.salesforce.connection.SalesforceConnection.getUpdated(SalesforceConnection.java:737) > at com.metamatrix.connector.salesforce.execution.GetUpdatedExecutionImpl.execute(GetUpdatedExecutionImpl.java:65) > at com.metamatrix.connector.salesforce.execution.ProcedureExecutionParentImpl.execute(ProcedureExecutionParentImpl.java:86) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processNewRequest(ConnectorWorker.java:275) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.process(ConnectorWorker.java:141) > at com.metamatrix.common.queue.QueueWorker.run(QueueWorker.java:64) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1847) Salesforce connector does not report UnexpectedErrorFault exceptions correctly when calling getUpdated

by Steven Hawkins (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1847?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1847: --------------------------------------- Was this reproduced in Teiid/EDS? > Salesforce connector does not report UnexpectedErrorFault exceptions correctly when calling getUpdated > ------------------------------------------------------------------------------------------------------ > > Key: TEIID-1847 > URL: https://issues.jboss.org/browse/TEIID-1847 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Reporter: Marc Shirley > Labels: salesforce > > When encountering an UnexpectedErrorFault with com.sforce.soap.partner.SoapBindingStub.GetUpdated(), com.metamatrix.connector.salesforce.connection.SalesforceConnection.getUpdated() throws a null error message instead of the message returned from Salesforce. It appears that the getUpdated() method is using java.rmi.RemoteException.getMessage() when it should be using SFDC com.sforce.soap.partner.fault.ApiFault.getExceptionMessage() for "UnexpectedErrorFault" exceptions. Associated stack trace below. > [Salesforce Connector_1246|9725_Worker_106|0] ERROR <CONNECTOR|0> Connector worker process failed for atomic-request=5707647.13.7.333713 > ConnectorException: Status ERROR: com.metamatrix.core code=0 null > at com.metamatrix.connector.salesforce.connection.SalesforceConnection.getUpdated(SalesforceConnection.java:737) > at com.metamatrix.connector.salesforce.execution.GetUpdatedExecutionImpl.execute(GetUpdatedExecutionImpl.java:65) > at com.metamatrix.connector.salesforce.execution.ProcedureExecutionParentImpl.execute(ProcedureExecutionParentImpl.java:86) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processNewRequest(ConnectorWorker.java:275) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.process(ConnectorWorker.java:141) > at com.metamatrix.common.queue.QueueWorker.run(QueueWorker.java:64) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1674) Need documentation created for JON EDS/teiid plugin

by Steven Hawkins (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1674?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1674: --------------------------------------- Based upon Ted's comment, can this issue be resolved? > Need documentation created for JON EDS/teiid plugin > --------------------------------------------------- > > Key: TEIID-1674 > URL: https://issues.jboss.org/browse/TEIID-1674 > Project: Teiid > Issue Type: Bug > Components: Documentation > Affects Versions: 7.4.1 > Reporter: Marc Shirley > Assignee: Ted Jones > > Need documentation for JON EDS/Teiid plugin describing available connection properties, configuration properties, metrics, operations, etc. for all resource types that the plugin monitors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 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 November 2011