[jbosstools-issues] [JBoss JIRA] Updated: (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:45:39 EDT 2010
[ https://jira.jboss.org/browse/JBIDE-7270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Barry LaFond updated JBIDE-7270:
--------------------------------
Fix Version/s: 3.2.0.Beta2
(was: 3.2.0.Beta1)
Workaround Description:
When creating "New Teiid Instance" in Teiid Designer, remove the "s" in the "mms://localhost:31443" URL at the top of the wizard.
Use: "mm://localhost:31443"
Workaround: [Workaround Exists]
Priority: Major (was: Blocker)
For some reason, in some server configurations, JBDS will start TEIID in a non-secure mode resulting in the TEIID URL being set to "mm://localhost:31443"
Teiid Designer was changed recently to default to the secure URL : "mms://localhost:31443"
Users can just change the URL by removing the "s" and all should work.
> 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
> Fix For: 3.2.0.Beta2
>
>
> 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