2 Replies Latest reply on May 15, 2013 9:58 AM by luca gioppo

    org.teiid.net.socket.SingleInstanceCommunicationException

    luca gioppo Novice

      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.

       

      I believe it could be related to:

      https://issues.jboss.org/browse/TEIID-2437

       

      If this could be the case my concern is the planned fixed release that is 8.4 that require to have EAP6.1 and not 7.1.1 anymore.

      This would mean that to solve this issue I have to install EAP in place of 7.1.1

       

      For us could be a problem

      could you plan to backport some patches (the critical ones) into 8.3 releasing a 8.3.x?

      Thanks

      Luca

        • 1. Re: org.teiid.net.socket.SingleInstanceCommunicationException
          Steven Hawkins Master

          Luca,

           

          You'll want to just approach this as any other issue - can you open a JIRA showing the underlying stacktrace, the user/source query and sample data?  TEIID-2437 and similar are caused when there is a type mismatch in data, which causes serialization to fail.  Typically we should convert any mismatched data to the expected runtime type as we bring it into Teiid, but your issue may highlight something deficient.

           

          > This would mean that to solve this issue I have to install EAP in place of 7.1.1

           

          Are you adverse to ever moving to EAP or specifically concerned about the near term timing?

           

          > could you plan to backport some patches (the critical ones) into 8.3 releasing a 8.3.x

           

          The short answer is yes.  On the download page you can see patch 2 for 8.3.x that addresses 4 critical/common issues.  The long answer is that prior to subsequent final releases we'll take responsibility for producing patches for the latest final release.  So if this gets addressed prior to final and is a critical/common issue, then it'll be added to that patch and the 8.3.x branch.  Otherwise you can always stick with an older release, such as 8.3, longer by manually pulling in patches into your own git fork of the release branch 8.3.x.

           

          Steve

          • 2. Re: org.teiid.net.socket.SingleInstanceCommunicationException
            luca gioppo Novice

            Will open a jira, but I have no logs in the server.log (I'm in domain mode and maybe I have to acrtivate something more?) the error just comes up to squirrel

             

            I'd like to pass to EAP, but for me changing a version of TEIID is quicker than changing the whole AS, that could call for bigger "change issue".

             

            Luca