July 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2596) enabled cipher suites property cannot be set

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2596?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2596: ---------------------------------- Issue Type: Bug (was: Feature Request) > enabled cipher suites property cannot be set > -------------------------------------------- > > Key: TEIID-2596 > URL: https://issues.jboss.org/browse/TEIID-2596 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > The enabled cipher suites property will fail to parse as expected in placed on the ssl config element. The xsd and other information needs updated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2596) enabled cipher suites property cannot be set

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2596?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2596. ----------------------------------- Resolution: Done Updated the code so that enabled-cipher-suites is picked up as an attribute of the ssl element. > enabled cipher suites property cannot be set > -------------------------------------------- > > Key: TEIID-2596 > URL: https://issues.jboss.org/browse/TEIID-2596 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > The enabled cipher suites property will fail to parse as expected in placed on the ssl config element. The xsd and other information needs updated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2596) enabled cipher suites property cannot be set

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2596: ------------------------------------- Summary: enabled cipher suites property cannot be set Key: TEIID-2596 URL: https://issues.jboss.org/browse/TEIID-2596 Project: Teiid Issue Type: Feature Request Components: Server Affects Versions: 8.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.4.1, 8.5 The enabled cipher suites property will fail to parse as expected in placed on the ssl config element. The xsd and other information needs updated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2595) Allow for more limit/offset expressions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2595?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2595. ----------------------------------- Resolution: Done updated the parse/resolve/validation logic to allow more complicated limit expressions - they are still required though to evaluate to a constant at runtime to ensure pushdown compatibility. > Allow for more limit/offset expressions > --------------------------------------- > > Key: TEIID-2595 > URL: https://issues.jboss.org/browse/TEIID-2595 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.5 > > > In virtual procedures it can be useful to specify limits based upon an expression rather than a constant. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2595) Allow for more limit/offset expressions

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2595: ------------------------------------- Summary: Allow for more limit/offset expressions Key: TEIID-2595 URL: https://issues.jboss.org/browse/TEIID-2595 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.5 In virtual procedures it can be useful to specify limits based upon an expression rather than a constant. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2593) often report: the trustAnchors parameter must be non-empty

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2593?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2593: ------------------------------------- Here is one more link http://mail.openjdk.java.net/pipermail/macosx-port-dev/2012-March/003479.... > often report: the trustAnchors parameter must be non-empty > ---------------------------------------------------------- > > Key: TEIID-2593 > URL: https://issues.jboss.org/browse/TEIID-2593 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector, JDBC Driver > Affects Versions: 7.7 > Environment: Operating System: RHEL6 > JBoss: 6.1 > JDK: java-1.7.0-openjdk-1.7.0.0.x86_64 > Teiid: 7.7.0.Final > Connecting to teiid via JDBC, the EngVDBF Database > Reporter: ying ma > Assignee: Steven Hawkins > Priority: Critical > Labels: eap6, jboss, sync > Original Estimate: 1 day > Remaining Estimate: 1 day > > This ques appear when we upgrade JBoss from 6.0 to 6.1, the teiid always could not create connection, as below: > 23:49:41,639 SEVERE [org.teiid.jdbc] (Timer-2) Could not create connection: org.teiid.jdbc.TeiidSQLException: Error establishing socket to host and port: vdb.engineering.redhat.com:31000. Reason: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:113) [teiid-client-7.7.0.Final.jar:7.7.0.Final] > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:70) [teiid-client-7.7.0.Final.jar:7.7.0.Final] > at org.teiid.jdbc.SocketProfile.connect(SocketProfile.java:56) [teiid-client-7.7.0.Final.jar:7.7.0.Final] > at org.teiid.jdbc.TeiidDriver.connect(TeiidDriver.java:107) [teiid-client-7.7.0.Final.jar:7.7.0.Final] > at java.sql.DriverManager.getConnection(DriverManager.java:571) [rt.jar:1.7.0_25] > at java.sql.DriverManager.getConnection(DriverManager.java:215) [rt.jar:1.7.0_25] > at com.rehat.tools.vault.service.impl.BugzillaProductUpdate.productVersionUpdateTask(BugzillaProductUpdate.java:42) [vault-service-1.1.1.jar:] > at com.redhat.tools.vault.listener.UpdateTimer.run(UpdateTimer.java:31) [classes:] > at java.util.TimerThread.mainLoop(Timer.java:555) [rt.jar:1.7.0_25] > at java.util.TimerThread.run(Timer.java:505) [rt.jar:1.7.0_25] > Caused by: [SingleInstanceCommunicationException]Error establishing socket to host and port: vdb.engineering.redhat.com:31000. Reason: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty > 1 [SSLException]java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty > 2 [RuntimeException]Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty > 3 [InvalidAlgorithmParameterException]the trustAnchors parameter must be non-empty > at org.teiid.net.socket.SocketServerConnection.selectServerInstance(SocketServerConnection.java:161) [teiid-client-7.7.0.Final.jar:7.7.0.Final] > at org.teiid.net.socket.SocketServerConnection.<init>(SocketServerConnection.java:95) [teiid-client-7.7.0.Final.jar:7.7.0.Final] > at org.teiid.net.socket.SocketServerConnectionFactory.getConnection(SocketServerConnectionFactory.java:320) [teiid-client-7.7.0.Final.jar:7.7.0.Final] > at org.teiid.jdbc.SocketProfile.connect(SocketProfile.java:54) [teiid-client-7.7.0.Final.jar:7.7.0.Final] > ... 7 more > Caused by: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty > at sun.security.ssl.Alerts.getSSLException(Alerts.java:208) [jsse.jar:1.7.0_25] > at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1886) [jsse.jar:1.7.0_25] > at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1844) [jsse.jar:1.7.0_25] > at sun.security.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1827) [jsse.jar:1.7.0_25] > at sun.security.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1753) [jsse.jar:1.7.0_25] > at sun.security.ssl.AppInputStream.read(AppInputStream.java:113) [jsse.jar:1.7.0_25] > at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) [rt.jar:1.7.0_25] > at java.io.BufferedInputStream.read1(BufferedInputStream.java:275) [rt.jar:1.7.0_25] > at java.io.BufferedInputStream.read(BufferedInputStream.java:334) [rt.jar:1.7.0_25] > at java.io.DataInputStream.read(DataInputStream.java:149) [rt.jar:1.7.0_25] > at org.teiid.netty.handler.codec.serialization.ObjectDecoderInputStream.fillBuffer(ObjectDecoderInputStream.java:164) [teiid-client-7.7.0.Final.jar:7.7.0.Final] > at org.teiid.netty.handler.codec.serialization.ObjectDecoderInputStream.findLength(ObjectDecoderInputStream.java:147) [teiid-client-7.7.0.Final.jar:7.7.0.Final] > at org.teiid.netty.handler.codec.serialization.ObjectDecoderInputStream.readObjectOverride(ObjectDecoderInputStream.java:81) [teiid-client-7.7.0.Final.jar:7.7.0.Final] > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:364) [rt.jar:1.7.0_25] > at org.teiid.net.socket.OioOjbectChannelFactory$OioObjectChannel.read(OioOjbectChannelFactory.java:114) [teiid-client-7.7.0.Final.jar:7.7.0.Final] > at org.teiid.net.socket.SocketServerInstanceImpl.doHandshake(SocketServerInstanceImpl.java:113) [teiid-client-7.7.0.Final.jar:7.7.0.Final] > at org.teiid.net.socket.SocketServerInstanceImpl.connect(SocketServerInstanceImpl.java:94) [teiid-client-7.7.0.Final.jar:7.7.0.Final] > at org.teiid.net.socket.SocketServerConnectionFactory.getServerInstance(SocketServerConnectionFactory.java:279) [teiid-client-7.7.0.Final.jar:7.7.0.Final] > at org.teiid.net.socket.SocketServerConnection.connect(SocketServerConnection.java:199) [teiid-client-7.7.0.Final.jar:7.7.0.Final] > at org.teiid.net.socket.SocketServerConnection.selectServerInstance(SocketServerConnection.java:125) [teiid-client-7.7.0.Final.jar:7.7.0.Final] > ... 10 more > Caused by: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty > at sun.security.validator.PKIXValidator.<init>(PKIXValidator.java:90) [rt.jar:1.7.0_25] > at sun.security.validator.Validator.getInstance(Validator.java:179) [rt.jar:1.7.0_25] > at sun.security.ssl.X509TrustManagerImpl.getValidator(X509TrustManagerImpl.java:314) [jsse.jar:1.7.0_25] > at sun.security.ssl.X509TrustManagerImpl.checkTrustedInit(X509TrustManagerImpl.java:173) [jsse.jar:1.7.0_25] > at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:186) [jsse.jar:1.7.0_25] > at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:126) [jsse.jar:1.7.0_25] > at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1323) [jsse.jar:1.7.0_25] > at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:153) [jsse.jar:1.7.0_25] > at sun.security.ssl.Handshaker.processLoop(Handshaker.java:868) [jsse.jar:1.7.0_25] > at sun.security.ssl.Handshaker.process_record(Handshaker.java:804) [jsse.jar:1.7.0_25] > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1016) [jsse.jar:1.7.0_25] > at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1312) [jsse.jar:1.7.0_25] > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:882) [jsse.jar:1.7.0_25] > at sun.security.ssl.AppInputStream.read(AppInputStream.java:102) [jsse.jar:1.7.0_25] > ... 24 more > Caused by: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty > at java.security.cert.PKIXParameters.setTrustAnchors(PKIXParameters.java:200) [rt.jar:1.7.0_25] > at java.security.cert.PKIXParameters.<init>(PKIXParameters.java:120) [rt.jar:1.7.0_25] > at java.security.cert.PKIXBuilderParameters.<init>(PKIXBuilderParameters.java:104) [rt.jar:1.7.0_25] > at sun.security.validator.PKIXValidator.<init>(PKIXValidator.java:88) [rt.jar:1.7.0_25] > ... 37 more > According to the log, it may be caused by the cacerts in jre/lib/security is NULL, however, we've create the symlink to ../../../../../../../etc/pki/java/cacerts. > I'm so confused about it, before jboss upgrade, the teiid is normal. So could you follow the issue? have any reason will cause the error? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2067) Global temporary tables

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2067?page=com.atlassian.jira.plugin... ] Work on TEIID-2067 started by Steven Hawkins. > Global temporary tables > ----------------------- > > Key: TEIID-2067 > URL: https://issues.jboss.org/browse/TEIID-2067 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.7 > Reporter: Mark Addleman > Assignee: Steven Hawkins > Fix For: 8.5 > > > Currently, temp tables are scoped to the teiid session (eg, jdbc connection) that created them. I would like temp tables visible to all sessions. It is acceptable and even desirable that temp tables use an external database a la external materialization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2594) Designer support for global temporary tables

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2594?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2594: ---------------------------------- Affects Version/s: (was: 7.7) Description: Teiid has added support for a global temporary tables - they share a common definition, but each session has their own instance. Internally this is modeled as a virtual table (without a transformation) with a table type of "TemporaryTable" (int code 6). If you provided matching index metadata we would recognize the entry as a global temporary table. Alternatively extension metadata could be used. was:Currently, temp tables are scoped to the teiid session (eg, jdbc connection) that created them. I would like temp tables visible to all sessions. It is acceptable and even desirable that temp tables use an external database a la external materialization. > Designer support for global temporary tables > -------------------------------------------- > > Key: TEIID-2594 > URL: https://issues.jboss.org/browse/TEIID-2594 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Mark Addleman > Assignee: Steven Hawkins > Fix For: 8.5 > > > Teiid has added support for a global temporary tables - they share a common definition, but each session has their own instance. Internally this is modeled as a virtual table (without a transformation) with a table type of "TemporaryTable" (int code 6). If you provided matching index metadata we would recognize the entry as a global temporary table. > Alternatively extension metadata could be used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2594) Designer support for global temporary tables

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2594: ------------------------------------- Summary: Designer support for global temporary tables Key: TEIID-2594 URL: https://issues.jboss.org/browse/TEIID-2594 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.7 Reporter: Mark Addleman Assignee: Steven Hawkins Fix For: 8.5 Currently, temp tables are scoped to the teiid session (eg, jdbc connection) that created them. I would like temp tables visible to all sessions. It is acceptable and even desirable that temp tables use an external database a la external materialization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2590) Use both the general and specific hint in the oracle hint

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2590?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2590. ----------------------------------- Resolution: Done Changed the logic to use both hints. Updated the 8.5 docs added a release note. > Use both the general and specific hint in the oracle hint > --------------------------------------------------------- > > Key: TEIID-2590 > URL: https://issues.jboss.org/browse/TEIID-2590 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > The documentation behavior is to use the specific OR general hint (preferring the specific). The request is to use both. Will likely implement as a behavioral change without the need to specify a translator property to enable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2013