October 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3181) Use Teiid as default JAAS application name

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3181?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3181: ------------------------------------- No, actually this is good. I failed to recognize the usefulness of this setting before. We do have to update some documentation based on this. > Use Teiid as default JAAS application name > ------------------------------------------ > > Key: TEIID-3181 > URL: https://issues.jboss.org/browse/TEIID-3181 > Project: Teiid > Issue Type: Enhancement > Reporter: Cristiano Nicolai > Assignee: Steven Hawkins > > Enhancement for the client side of setting up JDBC connections using GSS API. Suggestion is to use "Teiid" as default JAAS application name. This is to be used in case jaasName is not supplied in the connection properties. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3181) Use Teiid as default JAAS application name

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3181?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3181: --------------------------------------- I don't have a problem with this. Ramesh? > Use Teiid as default JAAS application name > ------------------------------------------ > > Key: TEIID-3181 > URL: https://issues.jboss.org/browse/TEIID-3181 > Project: Teiid > Issue Type: Enhancement > Reporter: Cristiano Nicolai > Assignee: Steven Hawkins > > Enhancement for the client side of setting up JDBC connections using GSS API. Suggestion is to use "Teiid" as default JAAS application name. This is to be used in case jaasName is not supplied in the connection properties. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3156) Provide a mechanism to turn off string sorting

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3156?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3156: ---------------------------------- Fix Version/s: 8.7.1 > Provide a mechanism to turn off string sorting > ---------------------------------------------- > > Key: TEIID-3156 > URL: https://issues.jboss.org/browse/TEIID-3156 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > Currently we don't have a fine grained mechanism to turn off source sorting of specifically string data. If a source is using a different collation for example and cannot be set on a session basis (that could be configured on the datasource) to an ansi/utf collation, then at least for join scenarios we have to process the sort in the engine. Optionally the user may wan the Teiid default collation enforced even for other sorts. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2976) Using new database logging extension, getting error that indicates column isn't long enough

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2976?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2976: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1154655|https://bugzilla.redhat.com/show_bug.cgi?id=1154655] from NEW to MODIFIED > Using new database logging extension, getting error that indicates column isn't long enough > ------------------------------------------------------------------------------------------- > > Key: TEIID-2976 > URL: https://issues.jboss.org/browse/TEIID-2976 > Project: Teiid > Issue Type: Bug > Components: Server > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 8.7.1 > > > Getting the following sporadically: > 11:57:57,538 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (pool-2-thread-1) Value too long for column "TRANSACTIONID VARCHAR(50)": "'TransactionImple < ac, BasicAction: 0:ffffc0a80102:307704ce:5388aa39:169 status: ActionStatus.RUNNING >' (103)"; SQL statement: > insert into commandlog (id, applicationname, executionid, modelname, plan, principal, requestid, rowcount, sessionid, sourcecommand, sourcerequestid, sqlcmd, eventtype, logtime, transactionid, translatorname, vdbname, vdbversion) values (null, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [22001-168] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2976) Using new database logging extension, getting error that indicates column isn't long enough

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2976?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2976. --------------------------------- Resolution: Done Increased the size to 256 > Using new database logging extension, getting error that indicates column isn't long enough > ------------------------------------------------------------------------------------------- > > Key: TEIID-2976 > URL: https://issues.jboss.org/browse/TEIID-2976 > Project: Teiid > Issue Type: Bug > Components: Server > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 8.7.1 > > > Getting the following sporadically: > 11:57:57,538 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (pool-2-thread-1) Value too long for column "TRANSACTIONID VARCHAR(50)": "'TransactionImple < ac, BasicAction: 0:ffffc0a80102:307704ce:5388aa39:169 status: ActionStatus.RUNNING >' (103)"; SQL statement: > insert into commandlog (id, applicationname, executionid, modelname, plan, principal, requestid, rowcount, sessionid, sourcecommand, sourcerequestid, sqlcmd, eventtype, logtime, transactionid, translatorname, vdbname, vdbversion) values (null, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [22001-168] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2976) Using new database logging extension, getting error that indicates column isn't long enough

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2976?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2976: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1154655 > Using new database logging extension, getting error that indicates column isn't long enough > ------------------------------------------------------------------------------------------- > > Key: TEIID-2976 > URL: https://issues.jboss.org/browse/TEIID-2976 > Project: Teiid > Issue Type: Bug > Components: Server > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 8.7.1 > > > Getting the following sporadically: > 11:57:57,538 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (pool-2-thread-1) Value too long for column "TRANSACTIONID VARCHAR(50)": "'TransactionImple < ac, BasicAction: 0:ffffc0a80102:307704ce:5388aa39:169 status: ActionStatus.RUNNING >' (103)"; SQL statement: > insert into commandlog (id, applicationname, executionid, modelname, plan, principal, requestid, rowcount, sessionid, sourcecommand, sourcerequestid, sqlcmd, eventtype, logtime, transactionid, translatorname, vdbname, vdbversion) values (null, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [22001-168] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2976) Using new database logging extension, getting error that indicates column isn't long enough

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIID-2976?page=com.atlassian.jira.plugin... ] Andrej Šmigala reopened TEIID-2976: ----------------------------------- It appears 100 is still not enough, as I get the following: {code} org.h2.jdbc.JdbcSQLException: Value too long for column "TRANSACTIONID VARCHAR(100)": "'TransactionImple < ac, BasicAction: 0:ffff0a221e8b:29f70065:54450202:1a statu s: ActionStatus.RUNNING >' (102)"; SQL statement: insert into commandlog (applicationname, executionid, modelname, principal, queryplan, requestid, rowcount, sessionid, sourcecommand, sourcerequestid, sqlcmd, eventtype, logtim e, transactionid, translatorname, vdbname, vdbversion, id) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [22001-168] {code} This is with XA transaction involving Oracle 11g and DB2 8.1 datasources > Using new database logging extension, getting error that indicates column isn't long enough > ------------------------------------------------------------------------------------------- > > Key: TEIID-2976 > URL: https://issues.jboss.org/browse/TEIID-2976 > Project: Teiid > Issue Type: Bug > Components: Server > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 8.7.1 > > > Getting the following sporadically: > 11:57:57,538 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (pool-2-thread-1) Value too long for column "TRANSACTIONID VARCHAR(50)": "'TransactionImple < ac, BasicAction: 0:ffffc0a80102:307704ce:5388aa39:169 status: ActionStatus.RUNNING >' (103)"; SQL statement: > insert into commandlog (id, applicationname, executionid, modelname, plan, principal, requestid, rowcount, sessionid, sourcecommand, sourcerequestid, sqlcmd, eventtype, logtime, transactionid, translatorname, vdbname, vdbversion) values (null, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [22001-168] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3164) Second connection to VDB through Kerberos authentication ends with exception

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3164?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3164: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1151027|https://bugzilla.redhat.com/show_bug.cgi?id=1151027] from NEW to MODIFIED > Second connection to VDB through Kerberos authentication ends with exception > ---------------------------------------------------------------------------- > > Key: TEIID-3164 > URL: https://issues.jboss.org/browse/TEIID-3164 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora20 > arch: x86_64 > java: sun 1.7 > kdc: on localhost > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Fix For: 8.7.1, 8.9 > > Attachments: krb.zip > > > Second (third,forth,...) conection to VDB through Kerberos ends with exception: > javax.security.auth.login.LoginException: TEIID50103 Wrong Response returned from EXAMPLE.COM security domain; Expecting a Kerberoes response -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3181) Use Teiid as default JAAS application name

by Cristiano Nicolai (JIRA)

[ https://issues.jboss.org/browse/TEIID-3181?page=com.atlassian.jira.plugin... ] Cristiano Nicolai updated TEIID-3181: ------------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/348 > Use Teiid as default JAAS application name > ------------------------------------------ > > Key: TEIID-3181 > URL: https://issues.jboss.org/browse/TEIID-3181 > Project: Teiid > Issue Type: Enhancement > Reporter: Cristiano Nicolai > Assignee: Steven Hawkins > > Enhancement for the client side of setting up JDBC connections using GSS API. Suggestion is to use "Teiid" as default JAAS application name. This is to be used in case jaasName is not supplied in the connection properties. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3180) Use TEIID/hostname as default Kerberos principal name

by Cristiano Nicolai (JIRA)

[ https://issues.jboss.org/browse/TEIID-3180?page=com.atlassian.jira.plugin... ] Cristiano Nicolai updated TEIID-3180: ------------------------------------- Description: Enhancement for the client side of setting up JDBC connections using GSS API. Suggestion is to use TEIID as service name, combined with the hostname used to create the Teiid connection. This is to be used in case kerberosServicePrincipleName is not supplied in the connection properties. (was: Enhancement for the client side of setting up JDBC connections using GSS API. Suggestion is to use TEIID as service name, combined with the hostname used to create the Teiid connection. This is tu be used in case kerberosServicePrincipleName is not supplied in the connection properties.) > Use TEIID/hostname as default Kerberos principal name > ----------------------------------------------------- > > Key: TEIID-3180 > URL: https://issues.jboss.org/browse/TEIID-3180 > Project: Teiid > Issue Type: Enhancement > Reporter: Cristiano Nicolai > Assignee: Steven Hawkins > > Enhancement for the client side of setting up JDBC connections using GSS API. Suggestion is to use TEIID as service name, combined with the hostname used to create the Teiid connection. This is to be used in case kerberosServicePrincipleName is not supplied in the connection properties. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2014