[JBoss JIRA] (TEIID-4079) SSL - anonymouse mode - connection fails
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4079?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-4079.
---------------------------------
> SSL - anonymouse mode - connection fails
> ----------------------------------------
>
> Key: TEIID-4079
> URL: https://issues.jboss.org/browse/TEIID-4079
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.12.5
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Attachments: keystore_server_expired.jks, keystore_server_untrusted.jks, truststore.jks
>
>
> If ssl-authentication-mode is set to anonymouse no certificates should be required. But if configuration of Teiid contains keystore-name which points to keystore with expired certificate, attempt to connect to Teiid fails.
> *Exception:*
> {code:plain}
> org.teiid.jdbc.TeiidSQLException: TEIID20020 Error establishing socket to host and port: localhost:31000. Reason: java.security.cert.CertificateExpiredException: NotAfter: Fri Feb 26 11:07:46 CET 2016
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135)
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71)
> at org.teiid.jdbc.SocketProfile.connect(SocketProfile.java:66)
> at org.teiid.jdbc.TeiidDriver.connect(TeiidDriver.java:107)
> at oeg.jboss.qe.ssl.SimpleSslTest.test(SimpleSslTest.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
> at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> at org.testng.TestRunner.privateRun(TestRunner.java:767)
> at org.testng.TestRunner.run(TestRunner.java:617)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
> at org.testng.SuiteRunner.run(SuiteRunner.java:240)
> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
> at org.testng.TestNG.runSuitesSequentially(TestNG.java:1198)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1123)
> at org.testng.TestNG.run(TestNG.java:1031)
> at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:70)
> at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:108)
> at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:111)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:172)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:104)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:70)
> Caused by: org.teiid.net.socket.SingleInstanceCommunicationException: TEIID20020 Error establishing socket to host and port: localhost:31000. Reason: java.security.cert.CertificateExpiredException: NotAfter: Fri Feb 26 11:07:46 CET 2016
> at org.teiid.net.socket.SocketServerConnection.selectServerInstance(SocketServerConnection.java:161)
> at org.teiid.net.socket.SocketServerConnection.<init>(SocketServerConnection.java:95)
> at org.teiid.net.socket.SocketServerConnectionFactory.getConnection(SocketServerConnectionFactory.java:316)
> at org.teiid.jdbc.SocketProfile.connect(SocketProfile.java:64)
> ... 35 more
> Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateExpiredException: NotAfter: Fri Feb 26 11:07:46 CET 2016
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1917)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:301)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:295)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1369)
> at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:156)
> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:925)
> at sun.security.ssl.Handshaker.process_record(Handshaker.java:860)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1043)
> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1343)
> at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:909)
> at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:265)
> at java.io.DataInputStream.readInt(DataInputStream.java:387)
> at org.teiid.netty.handler.codec.serialization.ObjectDecoderInputStream.readObjectOverride(ObjectDecoderInputStream.java:97)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:365)
> at org.teiid.net.socket.OioOjbectChannelFactory$OioObjectChannel.read(OioOjbectChannelFactory.java:117)
> at org.teiid.net.socket.SocketServerInstanceImpl.doHandshake(SocketServerInstanceImpl.java:128)
> at org.teiid.net.socket.SocketServerInstanceImpl.connect(SocketServerInstanceImpl.java:96)
> at org.teiid.net.socket.SocketServerConnectionFactory.getServerInstance(SocketServerConnectionFactory.java:277)
> at org.teiid.net.socket.SocketServerConnection.connect(SocketServerConnection.java:239)
> at org.teiid.net.socket.SocketServerConnection.selectServerInstance(SocketServerConnection.java:125)
> ... 38 more
> Caused by: java.security.cert.CertificateExpiredException: NotAfter: Fri Feb 26 11:07:46 CET 2016
> at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274)
> at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629)
> at sun.security.validator.SimpleValidator.engineValidate(SimpleValidator.java:188)
> at sun.security.validator.Validator.validate(Validator.java:260)
> at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324)
> at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229)
> at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1351)
> ... 56 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (TEIID-4131) External Materialized View's initial status should not insert into SYSADMIN.MatViews
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4131?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-4131.
---------------------------------
> External Materialized View's initial status should not insert into SYSADMIN.MatViews
> ------------------------------------------------------------------------------------
>
> Key: TEIID-4131
> URL: https://issues.jboss.org/browse/TEIID-4131
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Kylin Soong
>
> During VDB deploying, External Materialized View's initial status be insert into SYSADMIN.MatViews, this cause stale data, due to External Materialized View's status should go into physical database. Below is a example
> {code}
> SQL: SELECT VDBName, SchemaName, Name, TargetSchemaName, TargetName, Valid, LoadState, Updated, Cardinality FROM SYSADMIN.MatViews
> +----------------------+------------------+----------------------+------------------+--------------------------------+--------+---------------+---------+-------------+
> | VDBName | SchemaName | Name | TargetSchemaName | TargetName | Valid | LoadState | Updated | Cardinality |
> +----------------------+------------------+----------------------+------------------+--------------------------------+--------+---------------+---------+-------------+
> | PortfolioMaterialize | pg_catalog | matpg_datatype | [NULL] | #MAT_PG_CATALOG.MATPG_DATATYPE | false | NEEDS_LOADING | [NULL] | [NULL] |
> | PortfolioMaterialize | pg_catalog | pg_type | [NULL] | #MAT_PG_CATALOG.PG_TYPE | false | NEEDS_LOADING | [NULL] | [NULL] |
> | PortfolioMaterialize | StocksMatModel | stockPricesMatView | Accounts | H2_STOCK_MAT | [NULL] | [NULL] | [NULL] | [NULL] |
> | PortfolioMaterialize | StocksMatModel_1 | stockPricesMatView_1 | Accounts | H2_STOCK_MAT_1 | [NULL] | [NULL] | [NULL] | [NULL] |
> | PortfolioMaterialize | StocksMatModel_2 | stockPricesMatView_2 | Accounts | H2_STOCK_MAT_2 | [NULL] | [NULL] | [NULL] | [NULL] |
> | PortfolioMaterialize | StocksMatModel_3 | stockPricesMatView_3 | Accounts | H2_STOCK_MAT_3 | [NULL] | [NULL] | [NULL] | [NULL] |
> | PortfolioMaterialize | SYS | spatial_ref_sys | [NULL] | #MAT_SYS.SPATIAL_REF_SYS | false | NEEDS_LOADING | [NULL] | [NULL] |
> +----------------------+------------------+----------------------+------------------+--------------------------------+--------+---------------+---------+-------------+
> {code}
> Note that stockPricesMatView, stockPricesMatView_1, stockPricesMatView_2, stockPricesMatView_3 should not go into SYSADMIN.MatViews
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (TEIID-4013) ODBC sessions never release
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4013?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-4013.
---------------------------------
> ODBC sessions never release
> ---------------------------
>
> Key: TEIID-4013
> URL: https://issues.jboss.org/browse/TEIID-4013
> Project: Teiid
> Issue Type: Bug
> Components: ODBC
> Affects Versions: 8.7.1.6_2
> Environment: Red Hat JBoss Data Virtualization 6.2.2 on EAP6.4.0 patched to version 6.4.5,
> JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157
> 64-bit Windows 7 environment
> Reporter: Steve Tran
> Assignee: Steven Hawkins
> Attachments: Capture.PNG, Capture2.PNG, Capture3.PNG
>
>
> I have 3 ODBC System DSNs on a Windows server. When I'm viewing the Deployed VDBs and looking at the Sessions tab, the ODBC connections never seem to time out or release. Not really sure if/when they should release, but they continue to multiply. See screenshots.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (TEIID-4132) Internal Mat View's teiid_rel:MATVIEW_PREFER_MEMEORY option not take effect
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4132?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-4132.
---------------------------------
> Internal Mat View's teiid_rel:MATVIEW_PREFER_MEMEORY option not take effect
> ---------------------------------------------------------------------------
>
> Key: TEIID-4132
> URL: https://issues.jboss.org/browse/TEIID-4132
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
>
> From [https://teiid.gitbooks.io/documents/content/caching/Internal_Materializat...], the "teiid_rel:MATVIEW_PREFER_MEMEORY" should be same as the pref_mem cache hint option. But in my debug, it's not convert to cache hint, for example,
> {code}
> ) OPTIONS (materialized true,
> UPDATABLE 'TRUE',
> "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true',
> "teiid_rel:MATVIEW_PREFER_MEMEORY" 'true',
> "teiid_rel:MATVIEW_TTL" 300000,
> "teiid_rel:MATVIEW_UPDATABLE" 'true',
> "teiid_rel:MATVIEW_SCOPE" 'VDB'
> )
> {code}
> In TempTableDataManager's loadGlobalTable() method, the cache hint is like
> {code}
> /*+ cache(updatable scope:VDB) */
> {code}
> also the _hint.isPrefersMemory()_ result is false.
> So how to understand "teiid_rel:MATVIEW_PREFER_MEMEORY" in internal mat? does this is expect behivior?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months