September 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3643) VDB based kerberos authentication does not work with ODBC

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3643?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3643: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1254532|https://bugzilla.redhat.com/show_bug.cgi?id=1254532] from NEW to MODIFIED > 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.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3718) Add Log4j 2 Logger Adapter

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3718?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3718: --------------------------------------- Making a subtask of the wildfly work as we'll then pickup a later jboss logging version. I'm also fine if we want to put this and the log4j 1 adapter into a repository location for reference, use with older teiid versions, or to bypass having the additional jboss logging layer. > Add Log4j 2 Logger Adapter > -------------------------- > > Key: TEIID-3718 > URL: https://issues.jboss.org/browse/TEIID-3718 > Project: Teiid > Issue Type: Sub-task > Components: Embedded > Affects Versions: 8.11.4 > Environment: Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T04:57:37-07:00) > Maven home: C:\Java\apache-maven-3.3.3 > Java version: 1.7.0_79, vendor: Oracle Corporation > Java home: C:\Program Files\Java\jdk1.7.0_79\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" > Reporter: Gary Gregory > Attachments: Log4j2LoggerAdapter.java > > > Add a Log4j 2 Logger Adapter. See attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3718) Add Log4j 2 Logger Adapter

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3718?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3718: ------------------------------------- Assignee: (was: Steven Hawkins) > Add Log4j 2 Logger Adapter > -------------------------- > > Key: TEIID-3718 > URL: https://issues.jboss.org/browse/TEIID-3718 > Project: Teiid > Issue Type: Sub-task > Components: Embedded > Affects Versions: 8.11.4 > Environment: Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T04:57:37-07:00) > Maven home: C:\Java\apache-maven-3.3.3 > Java version: 1.7.0_79, vendor: Oracle Corporation > Java home: C:\Program Files\Java\jdk1.7.0_79\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" > Reporter: Gary Gregory > Attachments: Log4j2LoggerAdapter.java > > > Add a Log4j 2 Logger Adapter. See attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3718) Add Log4j 2 Logger Adapter

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3718?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3718: ---------------------------------- Parent: TEIID-3519 Issue Type: Sub-task (was: Feature Request) > Add Log4j 2 Logger Adapter > -------------------------- > > Key: TEIID-3718 > URL: https://issues.jboss.org/browse/TEIID-3718 > Project: Teiid > Issue Type: Sub-task > Components: Embedded > Affects Versions: 8.11.4 > Environment: Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T04:57:37-07:00) > Maven home: C:\Java\apache-maven-3.3.3 > Java version: 1.7.0_79, vendor: Oracle Corporation > Java home: C:\Program Files\Java\jdk1.7.0_79\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" > Reporter: Gary Gregory > Assignee: Steven Hawkins > Attachments: Log4j2LoggerAdapter.java > > > Add a Log4j 2 Logger Adapter. See attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3559) Refactor Object and Infinispan translator / connectors

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3559?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3559: ------------------------------------- "DV" is the new module path, there is reason to going back. That has been that way since 8.11 > Refactor Object and Infinispan translator / connectors > ------------------------------------------------------ > > Key: TEIID-3559 > URL: https://issues.jboss.org/browse/TEIID-3559 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Optional > > Now that JDG has reworked its remote-cache and changed (reduced) what dependencies its exposed, there's now more common code between the object/infinispan-cache translator/connector and the infinispan-cache-dsl translator/connector. I think refactoring can eliminate issues with support and ensure common behavior across all the code. > Where is common code seen: > - searching (i.e., DSLSearch) > - updates (InfinispanUpdateExecution) > - ClassRegistry > (for starters) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3687) Provide infinispan-cache translator override to add supportsNotCriteria

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3687?page=com.atlassian.jira.plugin... ] Van Halbert resolved TEIID-3687. -------------------------------- Fix Version/s: 8.12.1 Resolution: Done This was included in the first set of refactoring changes. > Provide infinispan-cache translator override to add supportsNotCriteria > ----------------------------------------------------------------------- > > Key: TEIID-3687 > URL: https://issues.jboss.org/browse/TEIID-3687 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.1 > > > Change the translator to add an override for supportsNotCriteria so that the user could enable push down of the GT/LT operators. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3687) Provide infinispan-cache translator override to add supportsNotCriteria

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3687?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3687: ------------------------------------ As part of the refactoring the infinispan-cache translator from the object translator, the changes were also made to include the override: @TranslatorProperty(display="NotCriteria", description="If true, translator can support the NOT operators: 'GT' or 'LT' ",advanced=true) @Override public boolean supportsNotCriteria() { return this.supportNotCriteria; } public void setSupportsNotCriteria(boolean supportNot) { this.supportNotCriteria = supportNot; } > Provide infinispan-cache translator override to add supportsNotCriteria > ----------------------------------------------------------------------- > > Key: TEIID-3687 > URL: https://issues.jboss.org/browse/TEIID-3687 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Van Halbert > > Change the translator to add an override for supportsNotCriteria so that the user could enable push down of the GT/LT operators. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3559) Refactor Object and Infinispan translator / connectors

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3559?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3559: --------------------------------------- Still no joy on the unit tests: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/Teiid%20-%20Continuou... What dependency is causing the issue? > Refactor Object and Infinispan translator / connectors > ------------------------------------------------------ > > Key: TEIID-3559 > URL: https://issues.jboss.org/browse/TEIID-3559 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Optional > > Now that JDG has reworked its remote-cache and changed (reduced) what dependencies its exposed, there's now more common code between the object/infinispan-cache translator/connector and the infinispan-cache-dsl translator/connector. I think refactoring can eliminate issues with support and ensure common behavior across all the code. > Where is common code seen: > - searching (i.e., DSLSearch) > - updates (InfinispanUpdateExecution) > - ClassRegistry > (for starters) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3559) Refactor Object and Infinispan translator / connectors

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3559?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3559: --------------------------------------- TEIID-3371 updated the path to dv. If that was a mistake, then we can revert back and track down what needs updated in the arquillian tests. Ramesh any thoughts? > Refactor Object and Infinispan translator / connectors > ------------------------------------------------------ > > Key: TEIID-3559 > URL: https://issues.jboss.org/browse/TEIID-3559 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Optional > > Now that JDG has reworked its remote-cache and changed (reduced) what dependencies its exposed, there's now more common code between the object/infinispan-cache translator/connector and the infinispan-cache-dsl translator/connector. I think refactoring can eliminate issues with support and ensure common behavior across all the code. > Where is common code seen: > - searching (i.e., DSLSearch) > - updates (InfinispanUpdateExecution) > - ClassRegistry > (for starters) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3559) Refactor Object and Infinispan translator / connectors

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3559?page=com.atlassian.jira.plugin... ] Van Halbert edited comment on TEIID-3559 at 9/30/15 9:02 AM: ------------------------------------------------------------- The root was set to "dv", I was thinking I had accidentally set that and was returning it back to its project location. Unless the project is now referencing "dv". was (Author: van.halbert): The root was set to "dv", I was thinking I had accidentally set that and was returning it back to its project location. > Refactor Object and Infinispan translator / connectors > ------------------------------------------------------ > > Key: TEIID-3559 > URL: https://issues.jboss.org/browse/TEIID-3559 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Optional > > Now that JDG has reworked its remote-cache and changed (reduced) what dependencies its exposed, there's now more common code between the object/infinispan-cache translator/connector and the infinispan-cache-dsl translator/connector. I think refactoring can eliminate issues with support and ensure common behavior across all the code. > Where is common code seen: > - searching (i.e., DSLSearch) > - updates (InfinispanUpdateExecution) > - ClassRegistry > (for starters) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2015