[teiid-issues] [JBoss JIRA] (TEIID-2502) org.teiid.net.socket.SingleInstanceCommunicationException

[luca gioppo (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12775247#comment-12775247 ] 

luca gioppo commented on TEIID-2502:
------------------------------------

It seems that oracle.sql.struts is serializable.
This link can perhaps help:
http://docs.oracle.com/cd/B13789_01/java.101/b10979/oraoot.htm
It should be possible to map also to java.sql.structs and maybe this could solve?

Can be a problem the fact that the designer mappet to object (is there a mapping to structs?).
I'll give it a try (if the structs mapping exists).

Hope this can help.
Luca
                
> org.teiid.net.socket.SingleInstanceCommunicationException
> ---------------------------------------------------------
>
>                 Key: TEIID-2502
>                 URL: https://issues.jboss.org/browse/TEIID-2502
>             Project: Teiid
>          Issue Type: Bug
>          Components: Query Engine
>    Affects Versions: 8.2
>         Environment: centos 6.3
>            Reporter: luca gioppo
>            Assignee: Steven Hawkins
>            Priority: Critical
>
> I'm issuing a query (a simple select * from table) on a VDB's table that contains a geometric column from oracle spatial.
> I'm getting the following error in SquirrelSQL
> Error: org.teiid.net.socket.SingleInstanceCommunicationException
> SQLState:  08S01
> ErrorCode: 0
> Afterwards the connection is broken and I cannot access any other table and have to reconnect since I get:
> Error: Error Code:TEIID20013 Message:Error Code:TEIID20013 Message:java.net.SocketException: Socket closed
> SQLState:  TEIID20013
> ErrorCode: 0
> I'm trying to access a SDO table and a geometry type column, but hoped that TEIID could read it as a BLOB without caring about the real type.
> Probably it doesn't like it too much.

--
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