September 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-643) Create data source from Teiid view gets [AdminComponentException]The specified session ID "null" is invalid.

by Paul Nittel (JIRA)

Create data source from Teiid view gets [AdminComponentException]The specified session ID "null" is invalid. ------------------------------------------------------------------------------------------------------------ Key: TEIIDDES-643 URL: https://jira.jboss.org/browse/TEIIDDES-643 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration Affects Versions: 7.1.1 Environment: JBDS 4.0.0 M2, Designer build H280, Teiid in SOA-P 5.1 ER2 Reporter: Paul Nittel Fix For: 7.1.1 I tried to create a data source from the Teiid view and got this instead: Error 2010-09-30 15:03:38.187 Error creating data source for model {0} [AdminComponentException]The specified session ID "null" is invalid. It cannot be found in the userbase. 1 [AdminProcessingException]The specified session ID "null" is invalid. It cannot be found in the userbase. 2 [InvalidSessionException]The specified session ID "null" is invalid. It cannot be found in the userbase. at org.teiid.client.util.ExceptionUtil.convertException(ExceptionUtil.java:72) at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler.invoke(SocketServerInstanceImpl.java:365) at org.teiid.net.socket.SocketServerConnection$1.invoke(SocketServerConnection.java:216) at $Proxy2.createDataSource(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.teiid.adminapi.AdminFactory$AdminProxy.invoke(AdminFactory.java:80) at $Proxy2.createDataSource(Unknown Source) at org.teiid.designer.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:197) at org.teiid.designer.runtime.ui.connection.CreateDataSourceAction.run(CreateDataSourceAction.java:142) at com.metamatrix.modeler.internal.dqp.ui.workspace.TeiidView$15.run(TeiidView.java:759) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3552) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3171) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) Caused by: [AdminProcessingException]The specified session ID "null" is invalid. It cannot be found in the userbase. 1 [InvalidSessionException]The specified session ID "null" is invalid. It cannot be found in the userbase. at org.teiid.client.util.ExceptionUtil.convertException(ExceptionUtil.java:70) at org.teiid.jboss.deployers.RuntimeEngineDeployer$2.invoke(RuntimeEngineDeployer.java:287) at $Proxy358.createDataSource(Unknown Source) at sun.reflect.GeneratedMethodAccessor945.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.teiid.transport.ServerWorkItem.run(ServerWorkItem.java:81) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:189) at org.teiid.transport.SocketClientInstance.processMessagePacket(SocketClientInstance.java:160) at org.teiid.transport.SocketClientInstance.receivedMessage(SocketClientInstance.java:149) at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:210) at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:100) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:754) at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:144) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:754) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:302) at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317) at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299) at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:754) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:302) at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317) at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299) at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:540) 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:349) at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:281) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:201) at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) 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) Caused by: [InvalidSessionException]The specified session ID "null" is invalid. It cannot be found in the userbase. at org.teiid.services.SessionServiceImpl.getSessionInfo(SessionServiceImpl.java:306) at org.teiid.services.SessionServiceImpl.validateSession(SessionServiceImpl.java:299) at org.teiid.jboss.deployers.RuntimeEngineDeployer$2.invoke(RuntimeEngineDeployer.java:280) ... 39 more -- 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

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-555) Could not start Designer with Parts Examples project and perform Preview Data

by Barry LaFond (JIRA)

Could not start Designer with Parts Examples project and perform Preview Data ----------------------------------------------------------------------------- Key: TEIIDDES-555 URL: https://jira.jboss.org/browse/TEIIDDES-555 Project: Teiid Designer Issue Type: Bug Reporter: Barry LaFond Assignee: Dan Florian Priority: Critical Fix For: 7.1 1) Installed CR2 (08/13/2010) and opened Parts example project 2) Created Oracle DTP connection profile 3) Set Connection Profile on both models to this Oracle CP 4) Created Teiid Server instance 5) Select table in source or view model and tried to "Preview Data" 6) Got errors and it did NOT query NOTE: I closed the project, started from scratch with "import Parts", then preview data worked immediately. Maybe we aren't setting something correctly in the "Set Connection Profile" action? -- 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

13 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-642) Parts Project's PartSupplier_SourceB model has no tables

by Paul Nittel (JIRA)

Parts Project's PartSupplier_SourceB model has no tables -------------------------------------------------------- Key: TEIIDDES-642 URL: https://jira.jboss.org/browse/TEIIDDES-642 Project: Teiid Designer Issue Type: Bug Components: Build Affects Versions: 7.1.1 Environment: JBDS 4.0.0, Teiid Designer build H280 Reporter: Paul Nittel I imported the Parts Project Zip archive into a Model project and found the PartSupplier_SourceA model was flagged as having errors. When I opened it up I realized there were no tables in the model. Somehow the model was corrupted when copied into the archive? I'll attach appropriate stuff. -- 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

13 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-645) Unable to synchronize models in VDB

by Paul Nittel (JIRA)

Unable to synchronize models in VDB ----------------------------------- Key: TEIIDDES-645 URL: https://jira.jboss.org/browse/TEIIDDES-645 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.1.1 Environment: JBDS 4.0.0 M2, Designer build H280, SOA-P 5.1 ER2 Reporter: Paul Nittel Fix For: 7.1.1 Attachments: BooksNoSynch.zip I took the Books example and, after fixing the broken transformation SQL, went to synch the VDB (prior to deployment). When I started the VDB editor I saw none of the models were in synch, but the Synchronize All button was disabled. Also found I could not check any of the synch check boxes. Restarted the Designer with the same result. This project had once contained the corrupt "Parts Project" folder and may be suffering from that in some weird way (since I deleted it). -- 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

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-628) Hide problem markers for Preview VDB's

by Barry LaFond (JIRA)

Hide problem markers for Preview VDB's -------------------------------------- Key: TEIIDDES-628 URL: https://jira.jboss.org/browse/TEIIDDES-628 Project: Teiid Designer Issue Type: Bug Components: Validation Reporter: Barry LaFond Assignee: Dan Florian Priority: Critical Fix For: 7.1.1 VDB's are validated just like models, so any "Open" VDB that has problems will duplicate any markers for same models in workspace. The Preview VDB's, however, should NOT contribute to the problems view. This will clean up the user experience and prevent confusion. -- 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

13 years, 8 months

2
2
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-488) DB2 Import - Source with DECIMAL datatype is being imported as LONG

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-488?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIIDDES-488. ------------------------------------- Fix Version/s: 7.1.1 Resolution: Done Resolved as part of TEIIDDES-569 > DB2 Import - Source with DECIMAL datatype is being imported as LONG > ------------------------------------------------------------------- > > Key: TEIIDDES-488 > URL: https://jira.jboss.org/browse/TEIIDDES-488 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.0 > Reporter: Warren Gibson > Fix For: 7.1.1 > > > Importer for DB2 is importing BQT2 LONGNUM (DECIMAL in database) to a LONG after import. Steve H says this should be come in as either a BigInteger or BigDecimal. -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-624) Dynamic SQL transformation validation getting: The number of transformation output symbols is zero.

by Paul Nittel (JIRA)

Dynamic SQL transformation validation getting: The number of transformation output symbols is zero. --------------------------------------------------------------------------------------------------- Key: TEIIDDES-624 URL: https://jira.jboss.org/browse/TEIIDDES-624 Project: Teiid Designer Issue Type: Bug Components: Validation Affects Versions: 7.1 Environment: JBDS 3.0.1, Designer build 9/16/2010 Reporter: Paul Nittel Fix For: 7.1.1 Executing the E2E Dynamic SQL Test Script fails when validating the transformation SQL, stating: The number of transformation output symbols is zero. The SQL in the test script should validate. -- 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

13 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-630) Callback Class Fails Dynamic Compile During WS-Security War Generation

by Ted Jones (JIRA)

Callback Class Fails Dynamic Compile During WS-Security War Generation ---------------------------------------------------------------------- Key: TEIIDDES-630 URL: https://jira.jboss.org/browse/TEIIDDES-630 Project: Teiid Designer Issue Type: Bug Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.1.1 Due to an unresolved dependency on WSPasswordCallback, the dynamic compilation of the UsernameCallback class is failing when the WS-Security war option is selected -- 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

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-641) NPE opening the JDBC Source node in model explorer for model without connection properties

by Barry LaFond (JIRA)

NPE opening the JDBC Source node in model explorer for model without connection properties ------------------------------------------------------------------------------------------ Key: TEIIDDES-641 URL: https://jira.jboss.org/browse/TEIIDDES-641 Project: Teiid Designer Issue Type: Bug Components: Views Affects Versions: 7.1, 7.1.1 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Critical Fix For: 7.1.1 using attached model project set example, the Source model has JDBC Source node, but no valid "connection properties" The ExtendedModelObjectContentProvider framework was allowing a old ConnectionBindingWrapper to display info here, but the functionality went away with new Teiid Server concept. The result was an NPE because no "connection profile" could be found. Need to remove this extension contribution. -- 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

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-610) Successfully creating a WAR file should not result in a logged WARNING

by Paul Nittel (JIRA)

Successfully creating a WAR file should not result in a logged WARNING ---------------------------------------------------------------------- Key: TEIIDDES-610 URL: https://jira.jboss.org/browse/TEIIDDES-610 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.1 Reporter: Paul Nittel Fix For: 7.1.1 This has been an issue since MetaMatrix. When a WAR file is created, a warning is generated. There should be no warning when something has successfully completed. eclipse.buildId=M20100211-1343 java.version=1.6.0_21 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86 Warning Tue Sep 14 12:19:57 CDT 2010 WAR file creation has succeeded -- 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

13 years, 8 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2010