[
https://issues.jboss.org/browse/TEIIDDES-1625?page=com.atlassian.jira.plu...
]
Steven Hawkins commented on TEIIDDES-1625:
------------------------------------------
3. the handshake is then written to the socketChannel, which I
thought was transferred to the server.
Yes and that is the source of this issue. The server then does not know what the proper
version of the client is.
So I am suggesting rather than the client assuming the object is not
wrapped as a SealedObject, a check should at least be added so that a ClassCastException
can be avoided, eg. if (object instanceof SealedObject) in BasicCryptor.unsealObject
That could be done, but seems unnecessary as the only case in which that would happen is a
misreported client version. There are also other places where the server is making
decisions based upon the client version, such as with data serialization. So if you
didn't fail here you would likely have failed later. If you want, you could log
something for the server side to make sure that the client version reported looks somewhat
like a version number that we expect.
Unable to create JDBC connection to Teiid 8.3 Final from Designer
-----------------------------------------------------------------
Key: TEIIDDES-1625
URL:
https://issues.jboss.org/browse/TEIIDDES-1625
Project: Teiid Designer
Issue Type: Bug
Reporter: Barry LaFond
Assignee: Paul Richardson
Fix For: 8.1
Upgraded Teiid designer to 8.3 Final bits
Tried to Preview a table and received following exception:
!ENTRY org.teiid.designer.dqp.ui 4 0 2013-03-19 11:33:24.518
!MESSAGE javax.crypto.SealedObject cannot be cast to
org.teiid.client.security.LogonResult
!STACK 0
java.lang.ClassCastException: javax.crypto.SealedObject cannot be cast to
org.teiid.client.security.LogonResult
at sun.proxy.$Proxy27.logon(Unknown Source)
at org.teiid.net.socket.SocketServerConnection.logon(SocketServerConnection.java:173)
at
org.teiid.net.socket.SocketServerConnection.selectServerInstance(SocketServerConnection.java:125)
at
org.teiid.net.socket.SocketServerConnection.<init>(SocketServerConnection.java:92)
at
org.teiid.net.socket.SocketServerConnectionFactory.getConnection(SocketServerConnectionFactory.java:312)
at org.teiid.jdbc.SocketProfile.connect(SocketProfile.java:54)
at org.teiid.jdbc.TeiidDriver.connect(TeiidDriver.java:107)
at org.teiid.jdbc.TeiidDriver.connect(TeiidDriver.java:1)
at
org.teiid.datatools.connectivity.TeiidJDBCConnection.createConnection(TeiidJDBCConnection.java:83)
at
org.eclipse.datatools.connectivity.DriverConnectionBase.internalCreateConnection(DriverConnectionBase.java:105)
at
org.eclipse.datatools.connectivity.DriverConnectionBase.open(DriverConnectionBase.java:54)
at
org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.open(JDBCConnection.java:73)
at
org.teiid.datatools.connectivity.TeiidJDBCConnectionFactory.createConnection(TeiidJDBCConnectionFactory.java:23)
at
org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:83)
at
org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:359)
at
org.teiid.designer.runtime.ui.preview.PreviewDataWorker.getSqlConnection(PreviewDataWorker.java:621)
at
org.teiid.designer.runtime.ui.preview.PreviewDataWorker.internalRun(PreviewDataWorker.java:398)
at
org.teiid.designer.runtime.ui.preview.PreviewDataWorker.run(PreviewDataWorker.java:263)
at
org.teiid.designer.runtime.ui.preview.PreviewTableDataContextAction.run(PreviewTableDataContextAction.java:99)
--
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