[JBoss JIRA] (TEIID-3541) Remove the Teiid embedded kit
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3541?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3541:
---------------------------------------
Van are you talking about translator development, or something else?
> Remove the Teiid embedded kit
> -----------------------------
>
> Key: TEIID-3541
> URL: https://issues.jboss.org/browse/TEIID-3541
> Project: Teiid
> Issue Type: Task
> Components: Embedded
> Reporter: Ramesh Reddy
> Assignee: Kylin Soong
> Fix For: 8.12
>
>
> There is no reason to keep a separate embedded kit supplied by Teiid. The scripts that are building the kit needs to be removed from build.
> All the required jar files for the "embedded" examples will be available from the "teiid-embedded-examples". Here we need to focus on documentation, but that is separate effort
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3609) Teiid Connection import: driver field not populated for resource adapters
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3609?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3609:
------------------------------------------------
David Le Sage <dlesage(a)redhat.com> changed the Status of [bug 1246116|https://bugzilla.redhat.com/show_bug.cgi?id=1246116] from ASSIGNED to MODIFIED
> Teiid Connection import: driver field not populated for resource adapters
> -------------------------------------------------------------------------
>
> Key: TEIID-3609
> URL: https://issues.jboss.org/browse/TEIID-3609
> Project: Teiid
> Issue Type: Bug
> Reporter: Andrej Šmigala
> Assignee: Ramesh Reddy
>
> When importing using Teiid Connection, the driver field is not populated for resource adapters when the pool name of the connection definition is the same as the id of the resource adapter itself. Except for the case that there is _another_ resource adapter defined for the same module _without_ any connection definitions.
> In other words, when the following is included in standalone.xml, the driver field is not populated
> {code:xml}
> <resource-adapter id="file">
> <module slot="main" id="org.jboss.teiid.resource-adapter.file"/>
> <transaction-support>NoTransaction</transaction-support>
> <connection-definitions>
> <connection-definition class-name="org.teiid.resource.adapter.file.FileManagedConnectionFactory" jndi-name="java:/file" enabled="true" pool-name="file">
> <config-property name="ParentDirectory">
> /home/
> </config-property>
> </connection-definition>
> </connection-definitions>
> </resource-adapter>
> {code}
> However, everything works as expected when the configuration is changed to this:
> {code:xml}
> <resource-adapter id="file">
> <module slot="main" id="org.jboss.teiid.resource-adapter.file"/>
> <transaction-support>NoTransaction</transaction-support>
> <connection-definitions>
> <connection-definition class-name="org.teiid.resource.adapter.file.FileManagedConnectionFactory" jndi-name="java:/fileDS" enabled="true" pool-name="fileDS">
> <config-property name="ParentDirectory">
> /home/
> </config-property>
> </connection-definition>
> </connection-definitions>
> </resource-adapter>
> {code}
> Or this:
> {code:xml}
> <resource-adapter id="file">
> <module slot="main" id="org.jboss.teiid.resource-adapter.file"/>
> </resource-adapter>
> <resource-adapter id="fileDS">
> <module slot="main" id="org.jboss.teiid.resource-adapter.file"/>
> <transaction-support>NoTransaction</transaction-support>
> <connection-definitions>
> <connection-definition class-name="org.teiid.resource.adapter.file.FileManagedConnectionFactory" jndi-name="java:/fileDS" enabled="true" pool-name="fileDS">
> <config-property name="ParentDirectory">
> /home/
> </config-property>
> </connection-definition>
> </connection-definitions>
> </resource-adapter>
> {code}
> This might be related to TEIIDDES-1895 and is most likely the original cause of TEIIDDES-2563.
> Clicking Next in the import wizard when such a datasource is selected causes the same error as described in TEIIDDES-2563.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3664) Only JDK 1.7 can build Teiid code base success
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3664?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3664:
---------------------------------------
>From looking at the code I would think that the root cause is that the ping on the first connection is not returning within the soTimeout, which should be 1 second. I can't really say why that would seemingly be slower on 1.8 for you.
Thinking about it some more, if we remove the socket pooling logic then that will introduce some overhead to the default load balancing strategy. As it will now need to establish new connections each time it switches hosts, whereas previously it may have been able to used a pooled connection.
> Only JDK 1.7 can build Teiid code base success
> ----------------------------------------------
>
> Key: TEIID-3664
> URL: https://issues.jboss.org/browse/TEIID-3664
> Project: Teiid
> Issue Type: Quality Risk
> Components: Build/Kits
> Affects Versions: 8.12
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
> Fix For: 8.12
>
>
> The following depiction exist in README.md
> {code}
> install JDK 1.7 or higher
> {code}
> But the build commands
> {code}
> $ mvn clean install -P release -s settings.xml
> {code}
> will execute failed if use JDK 1.8
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3643) VDB based kerberos authentication does not work with ODBC
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3643?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3643:
----------------------------------
Component/s: Server
> VDB based kerberos authentication does not work with ODBC
> ---------------------------------------------------------
>
> Key: TEIID-3643
> URL: https://issues.jboss.org/browse/TEIID-3643
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1.6_2
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Fix For: 8.12, 8.11.3
>
>
> I have a VDB configured to use GSS authentication. Both, JDBC and ODBC ports are configured to use default "teiid-security" security domain. Accessing the VDB through JDBC works fine, but ODBC throws exception [1], [2]. If the ODBC port is configured to use GSS authentication, connection is successful.
> [1]
> isql -v krb
> [08001][unixODBC]could not connect to server: Spojenie odmietnut
> Is the server running on host "localhost" (::1) and accepting
> TCP/IP connections on port 35432?
> ERROR: TEIID40055 Wrong logon method is being used. Server is not set up for Kerberos based authentication.
> DETAIL: org.teiid.jdbc.TeiidSQLException: TEIID40055 Wrong logon method is being used. Server is not set up for Kerberos based authentication.
> [ISQL]ERROR: Could not SQLConnect
> [2]
> 11:49:56,470 ERROR [org.teiid.ODBC] (New I/O worker #3) TEIID40015 Unexpected error occurred: org.teiid.client.security.LogonException: TEIID40055 Wrong logon method is being used. Server is not set up for Kerberos based authentication.
> at org.teiid.transport.LogonImpl.neogitiateGssLogin(LogonImpl.java:168) [teiid-runtime-8.7.1.6_2-redhat-4.jar:8.7.1.6_2-redhat-4]
> at org.teiid.odbc.ODBCServerRemoteImpl.logon(ODBCServerRemoteImpl.java:237) [teiid-runtime-8.7.1.6_2-redhat-4.jar:8.7.1.6_2-redhat-4]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_40]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_40]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_40]
> at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_40]
> at org.teiid.transport.ODBCClientInstance.processMessage(ODBCClientInstance.java:127) [teiid-runtime-8.7.1.6_2-redhat-4.jar:8.7.1.6_2-redhat-4]
> at org.teiid.transport.ODBCClientInstance.receivedMessage(ODBCClientInstance.java:116) [teiid-runtime-8.7.1.6_2-redhat-4.jar:8.7.1.6_2-redhat-4]
> at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:211) [teiid-runtime-8.7.1.6_2-redhat-4.jar:8.7.1.6_2-redhat-4]
> at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:109) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:328) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_40]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_40]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_40]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3670) Salesforce query issue
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIID-3670?page=com.atlassian.jira.plugin... ]
Mark Drilling commented on TEIID-3670:
--------------------------------------
On the INVALID_TYPE issue, I was able to reproduce it in DV61 - but not in DV62. So I assumed there was some teiid fix between those dot versions of teiid 8.7
Both tests were teiid alone. I created a salesforce RA and used the dynamic vdb attached to the designer jira. I connected and ran the query in squirrel.
Agree, the INVALID_QUERY_FILTER_OPERATOR issue is low priority. Realize I gave it a bad id, but didnt expect the error I got.
> Salesforce query issue
> ----------------------
>
> Key: TEIID-3670
> URL: https://issues.jboss.org/browse/TEIID-3670
> Project: Teiid
> Issue Type: Quality Risk
> Components: Salesforce Connector
> Affects Versions: 8.7.3
> Reporter: Mark Drilling
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 8.12
>
> Attachments: SFException.txt
>
>
> Linking to JIRA that was logged under Teiid Designer. I was able to reproduce the reported problem with both types of VDB - it is not really a designer issue.
> For this query:
> select Opportunity.CloseDate from SalesForceSource.Campaign, SalesForceSource.Opportunity WHERE Campaign.Id = Opportunity.CampaignId
> I was able to reproduce with earlier 8.7 version of teiid, but it appears to have been addressed in a later 8.7.x version (DV62).
> However I then tried this query:
> select Opportunity.CloseDate from SalesForceSource.Campaign, SalesForceSource.Opportunity WHERE Campaign.Id = 'xx'
> which results in a "Invalid QName in mapping: sf:INVALID_QUERY_FILTER_OPERATOR" exception (see attachment). This occurs in the DV62/teiid8.7.1 version.
> I realize there has been some work recently in the salesforce connector area, so not sure if it is still an issue with recent versions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3670) Salesforce query issue
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3670?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3670:
----------------------------------
Issue Type: Quality Risk (was: Bug)
Component/s: Salesforce Connector
(was: Misc. Connectors)
Fix Version/s: 8.12
Summary: Salesforce query issue (was: Salesforce Join query issues)
Priority: Minor (was: Major)
Just to make sure there is the same understanding, you cannot reproduce the INVALID_TYPE issue with Teiid alone, but you do hit an INVALID_QUERY_FILTER_OPERATOR?
INVALID_QUERY_FILTER_OPERATOR is likely expected here - http://salesforce.stackexchange.com/questions/8351/is-there-any-way-to-fi...
It is saying that xx is not a valid id. For us to prevent this we would need to validate the id to ensure that it's a 15 character base 62 value. Converting to a low priority quality risk.
> Salesforce query issue
> ----------------------
>
> Key: TEIID-3670
> URL: https://issues.jboss.org/browse/TEIID-3670
> Project: Teiid
> Issue Type: Quality Risk
> Components: Salesforce Connector
> Affects Versions: 8.7.3
> Reporter: Mark Drilling
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 8.12
>
> Attachments: SFException.txt
>
>
> Linking to JIRA that was logged under Teiid Designer. I was able to reproduce the reported problem with both types of VDB - it is not really a designer issue.
> For this query:
> select Opportunity.CloseDate from SalesForceSource.Campaign, SalesForceSource.Opportunity WHERE Campaign.Id = Opportunity.CampaignId
> I was able to reproduce with earlier 8.7 version of teiid, but it appears to have been addressed in a later 8.7.x version (DV62).
> However I then tried this query:
> select Opportunity.CloseDate from SalesForceSource.Campaign, SalesForceSource.Opportunity WHERE Campaign.Id = 'xx'
> which results in a "Invalid QName in mapping: sf:INVALID_QUERY_FILTER_OPERATOR" exception (see attachment). This occurs in the DV62/teiid8.7.1 version.
> I realize there has been some work recently in the salesforce connector area, so not sure if it is still an issue with recent versions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3670) Salesforce Join query issues
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIID-3670?page=com.atlassian.jira.plugin... ]
Mark Drilling updated TEIID-3670:
---------------------------------
Attachment: SFException.txt
> Salesforce Join query issues
> ----------------------------
>
> Key: TEIID-3670
> URL: https://issues.jboss.org/browse/TEIID-3670
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7.3
> Reporter: Mark Drilling
> Assignee: Steven Hawkins
> Attachments: SFException.txt
>
>
> Linking to JIRA that was logged under Teiid Designer. I was able to reproduce the reported problem with both types of VDB - it is not really a designer issue.
> For this query:
> select Opportunity.CloseDate from SalesForceSource.Campaign, SalesForceSource.Opportunity WHERE Campaign.Id = Opportunity.CampaignId
> I was able to reproduce with earlier 8.7 version of teiid, but it appears to have been addressed in a later 8.7.x version (DV62).
> However I then tried this query:
> select Opportunity.CloseDate from SalesForceSource.Campaign, SalesForceSource.Opportunity WHERE Campaign.Id = 'xx'
> which results in a "Invalid QName in mapping: sf:INVALID_QUERY_FILTER_OPERATOR" exception (see attachment). This occurs in the DV62/teiid8.7.1 version.
> I realize there has been some work recently in the salesforce connector area, so not sure if it is still an issue with recent versions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months