[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7270) New teiid connection instances are created badly in 3.2.0.beta1

Barry LaFond (JIRA) jira-events at lists.jboss.org
Wed Oct 6 09:00:40 EDT 2010


    [ https://jira.jboss.org/browse/JBIDE-7270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555585#action_12555585 ] 

Barry LaFond commented on JBIDE-7270:
-------------------------------------

Was able to reproduce if I start my server from inside JBDS.

Looking at the console output on start-up, the Teiid Admin URL is being created as "mm://localhost:31443"

If I start my server from my file system terminal, it creates the Teiid Admin URL as "mms://localhost:31443" which is the intended default "secure" URL

Teiid Designer was changed to use the "mm://localhost:31443" as default URL. You can work-around by removing the "s" in the URL and it should work again.

So the question is now, why is the URL different when started in JBDS??

> New teiid connection instances are created badly in 3.2.0.beta1
> ---------------------------------------------------------------
>
>                 Key: JBIDE-7270
>                 URL: https://jira.jboss.org/browse/JBIDE-7270
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: teiid
>    Affects Versions: 3.2.0.Beta1
>         Environment: JBDS 4.0.0.beta1 #30, Linux 64
>            Reporter: Jiri Peterka
>            Assignee: Barry LaFond
>            Priority: Blocker
>             Fix For: 3.2.0.Beta1
>
>
> Steps:
> - Create new instance in Teidd view. 
> ERROR: It's unable to connect teiid server with newly created connection
> Java.io.StreamCorruptedException: invalid data length: -2140864253
> 	at org.teiid.transport.ObjectDecoder.decode(ObjectDecoder.java:116)
> 	at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:282)
> 	at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216)
> 	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274)
> 	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261)
> 	at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:340)
> 	at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:272)
> 	at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:192)
> 	at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list