[JBoss JIRA] Closed: (TEIIDDES-110) Preview does not allow leaving fields null for nullable columns in an access pattern
by Barry LaFond (JIRA)
[ https://jira.jboss.org/jira/browse/TEIIDDES-110?page=com.atlassian.jira.p... ]
Barry LaFond closed TEIIDDES-110.
---------------------------------
> Preview does not allow leaving fields null for nullable columns in an access pattern
> ------------------------------------------------------------------------------------
>
> Key: TEIIDDES-110
> URL: https://jira.jboss.org/jira/browse/TEIIDDES-110
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview
> Affects Versions: 6.0.0
> Environment: 5.5.3GA Designer on Linux
> Reporter: Greg Haber
> Assignee: Dan Florian
> Fix For: 6.0.0
>
> Attachments: oracleTest_20081210_1.zip
>
>
> If an access pattern contains a nullable column (and this probably also holds for procedure input parameters), then Preview doesn't have an option to leave the value blank (to specify null). If you enter the string "null" into the field for that column, it will send the string "null". Not sure on how semantics of this should work (whether leaving the field blank should be the equivalent of specifying null, or whether we should use the string "null", or whether there should be a checkbox for saying that the value is null), so whatever makes sense.
> However regardless on how the UI works this should result in a WHERE colname IS NULL criteria in the resulting query.
> I know we aren't trying to tackle all edge cases with preview, but this is a common case with web service parameters (it is common to have required and nillable parameters).
> This one depends on JBEDSP-855 getting resolved first.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (TEIIDDES-117) JDBC driver JARs added when creating a new JDBC source at import time should be added as extension JARs so the connector works at runtime.
by Ken Johnson (JIRA)
JDBC driver JARs added when creating a new JDBC source at import time should be added as extension JARs so the connector works at runtime.
------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-117
URL: https://jira.jboss.org/jira/browse/TEIIDDES-117
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 6.0.0
Environment: Ganymede 3.4.1 JEE environment + Teiid Designer 6.0.0 pre-release.
Reporter: Ken Johnson
Given that Designer does not bundle any JDBC driver JARs, the need to be added by the user. Currently they are required in two places:
1. when defining an import source
2. for the connector used during preview and testing (extension jar)
The user has to deal with importing the driver JARs in two different ways to support the logical operation of Import->Model->Preview. Suggest:
a) providing a single new mechanism for adding driver JARs to the tooling so they are available for both Import and Preview/Execution, or
b) automatically add extension JAR for Preview/Execution when specifying driver JAR during import source configuration, or
c) both
In the present implementation, a novice user will have a heck of a time understanding why Preview doesn't work when they just added the JAR while configuring the source for import.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (TEIIDDES-127) Trying to export DDL gets NoClassDefFoundError: com/metamatrix/modeler/ddl/DdlPlugin
by Paul Nittel (JIRA)
Trying to export DDL gets NoClassDefFoundError: com/metamatrix/modeler/ddl/DdlPlugin
------------------------------------------------------------------------------------
Key: TEIIDDES-127
URL: https://jira.jboss.org/jira/browse/TEIIDDES-127
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 6.0.0
Environment: Fedora 10, teiid_designer_TEST_032409
Reporter: Paul Nittel
I created a small relational source model and tried to export it as DDL. I received this exception:
Error 2009-03-24 15:25:02.01 Unhandled event loop exception
java.lang.NoClassDefFoundError: com/metamatrix/modeler/ddl/DdlPlugin
at com.metamatrix.modeler.internal.ui.wizards.ExportDdlWizard.init(ExportDdlWizard.java:220)
at org.eclipse.ui.internal.dialogs.WorkbenchWizardNode.getWizard(WorkbenchWizardNode.java:185)
at org.eclipse.jface.wizard.WizardSelectionPage.getNextPage(WizardSelectionPage.java:104)
at org.eclipse.ui.internal.dialogs.WorkbenchWizardSelectionPage.getNextPage(WorkbenchWizardSelectionPage.java:100)
at org.eclipse.ui.internal.dialogs.ImportExportPage.getNextPage(ImportExportPage.java:431)
at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:813)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.handlers.WizardHandler$Export.executeHandler(WizardHandler.java:97)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:273)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:281)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:247)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
at org.eclipse.ui.internal.actions.CommandAction.run(CommandAction.java:171)
at org.eclipse.ui.actions.ExportResourcesAction.run(ExportResourcesAction.java:116)
at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:168)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500)
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:1158)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
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:386)
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:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Caused by: org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNotFoundException: An error occurred while automatically activating bundle org.teiid.designer.ddl (247).
at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:125)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:427)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:193)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:368)
at org.eclipse.osgi.framework.internal.core.SingleSourcePackage.loadClass(SingleSourcePackage.java:33)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:441)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:397)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:385)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:87)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
... 53 more
Caused by: org.osgi.framework.BundleException: The activator com.metamatrix.modeler.ddl.DdlPlugin for bundle org.teiid.designer.ddl is invalid
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:146)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:980)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:265)
at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:400)
at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111)
... 63 more
Caused by: java.lang.NoClassDefFoundError: com/metamatrix/core/xslt/Style
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
at java.lang.Class.getConstructor0(Class.java:2699)
at java.lang.Class.newInstance0(Class.java:326)
at java.lang.Class.newInstance(Class.java:308)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:141)
... 68 more
Caused by: org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNotFoundException: An error occurred while automatically activating bundle org.teiid.designer.core.xslt (246).
at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:125)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:427)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:193)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:368)
at org.eclipse.osgi.framework.internal.core.SingleSourcePackage.loadClass(SingleSourcePackage.java:33)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:441)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:397)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:385)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:87)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
... 74 more
Caused by: org.osgi.framework.BundleException: The activator com.metamatrix.core.xslt.CoreXsltPlugin for bundle org.teiid.designer.core.xslt is invalid
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:146)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:980)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:265)
at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:400)
at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111)
... 84 more
Caused by: java.lang.ClassCastException: com.metamatrix.core.xslt.CoreXsltPlugin cannot be cast to org.osgi.framework.BundleActivator
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:141)
... 89 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (TEIIDDES-138) Class loading issues with XA transactions executing VDBs in Designer
by Paul Nittel (JIRA)
Class loading issues with XA transactions executing VDBs in Designer
--------------------------------------------------------------------
Key: TEIIDDES-138
URL: https://jira.jboss.org/jira/browse/TEIIDDES-138
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 6.0.0
Environment: fedora 10, Teiid Designer 040709
Reporter: Paul Nittel
Ramesh said, "Looks like another class loading issue in the Designer. This class in issue below is in "jta-1.1.jar", looks like designer also has copy of it." in response to my email (below).
I ran through the E2E Updateable Web Service test script. When I executed the Insert operation, I received an error dialog (photo attached). There were some exceptions as well. Here they are:
Error 2009-04-08 08:21:43.869 Connector worker process failed for atomic-request=00000000-0000-000c-0000-00000000000c.14.1.751
java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "com.metamatrix.jdbcx.base.BaseXAConnection.getXAResource()Ljavax/transaction/xa/XAResource;" the class loader (instance of com/metamatrix/common/classloader/URLFilteringClassLoader) of the current class, com/metamatrix/jdbcx/base/BaseXAConnection, and the class loader (instance of <bootloader>) for interface javax/sql/XAConnection have different Class objects for the type javax/transaction/xa/XAResource used in the signature
at com.metamatrix.jdbcx.base.BaseXADataSource.getXAConnection(Unknown Source)
at org.teiid.connector.jdbc.JDBCConnector.getXAConnection(JDBCConnector.java:221)
at org.teiid.dqp.internal.pooling.connector.ConnectionPool.createConnection(ConnectionPool.java:341)
at org.teiid.dqp.internal.pooling.connector.ConnectionPool.obtain(ConnectionPool.java:269)
at org.teiid.dqp.internal.pooling.connector.PooledConnector.getXAConnectionDirect(PooledConnector.java:145)
at org.teiid.dqp.internal.datamgr.impl.ConnectorWrapper.getXAConnection(ConnectorWrapper.java:70)
at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.createConnection(ConnectorWorkItem.java:130)
at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.createExecution(ConnectorWorkItem.java:287)
at org.teiid.dqp.internal.datamgr.impl.SynchConnectorWorkItem.createExecution(SynchConnectorWorkItem.java:100)
at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.process(ConnectorWorkItem.java:151)
at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44)
at org.teiid.dqp.internal.datamgr.impl.SynchConnectorWorkItem.run(SynchConnectorWorkItem.java:69)
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)
Error 2009-04-08 08:21:43.879 ############# PW EXITING on 00000000-0000-000c-0000-00000000000c.14 - error occurred ###########
[MetaMatrixComponentException]loader constraint violation in interface itable initialization: when resolving method "com.metamatrix.jdbcx.base.BaseXAConnection.getXAResource()Ljavax/transaction/xa/XAResource;" the class loader (instance of com/metamatrix/common/classloader/URLFilteringClassLoader) of the current class, com/metamatrix/jdbcx/base/BaseXAConnection, and the class loader (instance of <bootloader>) for interface javax/sql/XAConnection have different Class objects for the type javax/transaction/xa/XAResource used in the signature
1 [LinkageError]loader constraint violation in interface itable initialization: when resolving method "com.metamatrix.jdbcx.base.BaseXAConnection.getXAResource()Ljavax/transaction/xa/XAResource;" the class loader (instance of com/metamatrix/common/classloader/URLFilteringClassLoader) of the current class, com/metamatrix/jdbcx/base/BaseXAConnection, and the class loader (instance of <bootloader>) for interface javax/sql/XAConnection have different Class objects for the type javax/transaction/xa/XAResource used in the signature
at org.teiid.dqp.internal.process.DataTierTupleSource.switchBatch(DataTierTupleSource.java:128)
at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:89)
at com.metamatrix.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:154)
at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:243)
at com.metamatrix.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:109)
at com.metamatrix.query.processor.QueryProcessor.process(QueryProcessor.java:151)
at com.metamatrix.query.processor.proc.ProcedurePlan.getResults(ProcedurePlan.java:297)
at com.metamatrix.query.processor.proc.ProcedureEnvironment.executePlan(ProcedureEnvironment.java:130)
at com.metamatrix.query.processor.proc.AbstractAssignmentInstruction.process(AbstractAssignmentInstruction.java:89)
at com.metamatrix.query.processor.proc.ProcedurePlan.processProcedure(ProcedurePlan.java:282)
at com.metamatrix.query.processor.proc.ProcedurePlan.nextBatch(ProcedurePlan.java:221)
at com.metamatrix.query.processor.relational.PlanExecutionNode.nextBatchDirect(PlanExecutionNode.java:106)
at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:243)
at com.metamatrix.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:173)
at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:243)
at com.metamatrix.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:109)
at com.metamatrix.query.processor.QueryProcessor.process(QueryProcessor.java:151)
at com.metamatrix.query.processor.proc.ProcedurePlan.getResults(ProcedurePlan.java:297)
at com.metamatrix.query.processor.proc.ProcedureEnvironment.executePlan(ProcedureEnvironment.java:130)
at com.metamatrix.query.processor.proc.AbstractAssignmentInstruction.process(AbstractAssignmentInstruction.java:89)
at com.metamatrix.query.processor.proc.ProcedurePlan.processProcedure(ProcedurePlan.java:282)
at com.metamatrix.query.processor.proc.ProcedurePlan.nextBatch(ProcedurePlan.java:221)
at com.metamatrix.query.processor.relational.PlanExecutionNode.nextBatchDirect(PlanExecutionNode.java:106)
at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:243)
at com.metamatrix.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:173)
at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:243)
at com.metamatrix.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:109)
at com.metamatrix.query.processor.QueryProcessor.process(QueryProcessor.java:151)
at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:269)
at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:213)
at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44)
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: java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "com.metamatrix.jdbcx.base.BaseXAConnection.getXAResource()Ljavax/transaction/xa/XAResource;" the class loader (instance of com/metamatrix/common/classloader/URLFilteringClassLoader) of the current class, com/metamatrix/jdbcx/base/BaseXAConnection, and the class loader (instance of <bootloader>) for interface javax/sql/XAConnection have different Class objects for the type javax/transaction/xa/XAResource used in the signature
at com.metamatrix.jdbcx.base.BaseXADataSource.getXAConnection(Unknown Source)
at org.teiid.connector.jdbc.JDBCConnector.getXAConnection(JDBCConnector.java:221)
at org.teiid.dqp.internal.pooling.connector.ConnectionPool.createConnection(ConnectionPool.java:341)
at org.teiid.dqp.internal.pooling.connector.ConnectionPool.obtain(ConnectionPool.java:269)
at org.teiid.dqp.internal.pooling.connector.PooledConnector.getXAConnectionDirect(PooledConnector.java:145)
at org.teiid.dqp.internal.datamgr.impl.ConnectorWrapper.getXAConnection(ConnectorWrapper.java:70)
at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.createConnection(ConnectorWorkItem.java:130)
at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.createExecution(ConnectorWorkItem.java:287)
at org.teiid.dqp.internal.datamgr.impl.SynchConnectorWorkItem.createExecution(SynchConnectorWorkItem.java:100)
at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.process(ConnectorWorkItem.java:151)
at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44)
at org.teiid.dqp.internal.datamgr.impl.SynchConnectorWorkItem.run(SynchConnectorWorkItem.java:69)
... 3 more
Error 2009-04-08 08:21:43.889 Error processing query
com.metamatrix.jdbc.MMSQLException: loader constraint violation in interface itable initialization: when resolving method "com.metamatrix.jdbcx.base.BaseXAConnection.getXAResource()Ljavax/transaction/xa/XAResource;" the class loader (instance of com/metamatrix/common/classloader/URLFilteringClassLoader) of the current class, com/metamatrix/jdbcx/base/BaseXAConnection, and the class loader (instance of <bootloader>) for interface javax/sql/XAConnection have different Class objects for the type javax/transaction/xa/XAResource used in the signature
at com.metamatrix.jdbc.MMSQLException.create(MMSQLException.java:82)
at com.metamatrix.jdbc.MMSQLException.create(MMSQLException.java:63)
at com.metamatrix.jdbc.MMStatement.executeSql(MMStatement.java:424)
at com.metamatrix.jdbc.MMStatement.execute(MMStatement.java:326)
at net.sourceforge.sqlexplorer.sqlpanel.SqlExecProgress.processQuery(SqlExecProgress.java:192)
at net.sourceforge.sqlexplorer.sqlpanel.SqlExecProgress.run(SqlExecProgress.java:121)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: [MetaMatrixComponentException]loader constraint violation in interface itable initialization: when resolving method "com.metamatrix.jdbcx.base.BaseXAConnection.getXAResource()Ljavax/transaction/xa/XAResource;" the class loader (instance of com/metamatrix/common/classloader/URLFilteringClassLoader) of the current class, com/metamatrix/jdbcx/base/BaseXAConnection, and the class loader (instance of <bootloader>) for interface javax/sql/XAConnection have different Class objects for the type javax/transaction/xa/XAResource used in the signature
1 [LinkageError]loader constraint violation in interface itable initialization: when resolving method "com.metamatrix.jdbcx.base.BaseXAConnection.getXAResource()Ljavax/transaction/xa/XAResource;" the class loader (instance of com/metamatrix/common/classloader/URLFilteringClassLoader) of the current class, com/metamatrix/jdbcx/base/BaseXAConnection, and the class loader (instance of <bootloader>) for interface javax/sql/XAConnection have different Class objects for the type javax/transaction/xa/XAResource used in the signature
at org.teiid.dqp.internal.process.DataTierTupleSource.switchBatch(DataTierTupleSource.java:128)
at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:89)
at com.metamatrix.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:154)
at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:243)
at com.metamatrix.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:109)
at com.metamatrix.query.processor.QueryProcessor.process(QueryProcessor.java:151)
at com.metamatrix.query.processor.proc.ProcedurePlan.getResults(ProcedurePlan.java:297)
at com.metamatrix.query.processor.proc.ProcedureEnvironment.executePlan(ProcedureEnvironment.java:130)
at com.metamatrix.query.processor.proc.AbstractAssignmentInstruction.process(AbstractAssignmentInstruction.java:89)
at com.metamatrix.query.processor.proc.ProcedurePlan.processProcedure(ProcedurePlan.java:282)
at com.metamatrix.query.processor.proc.ProcedurePlan.nextBatch(ProcedurePlan.java:221)
at com.metamatrix.query.processor.relational.PlanExecutionNode.nextBatchDirect(PlanExecutionNode.java:106)
at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:243)
at com.metamatrix.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:173)
at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:243)
at com.metamatrix.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:109)
at com.metamatrix.query.processor.QueryProcessor.process(QueryProcessor.java:151)
at com.metamatrix.query.processor.proc.ProcedurePlan.getResults(ProcedurePlan.java:297)
at com.metamatrix.query.processor.proc.ProcedureEnvironment.executePlan(ProcedureEnvironment.java:130)
at com.metamatrix.query.processor.proc.AbstractAssignmentInstruction.process(AbstractAssignmentInstruction.java:89)
at com.metamatrix.query.processor.proc.ProcedurePlan.processProcedure(ProcedurePlan.java:282)
at com.metamatrix.query.processor.proc.ProcedurePlan.nextBatch(ProcedurePlan.java:221)
at com.metamatrix.query.processor.relational.PlanExecutionNode.nextBatchDirect(PlanExecutionNode.java:106)
at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:243)
at com.metamatrix.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:173)
at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:243)
at com.metamatrix.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:109)
at com.metamatrix.query.processor.QueryProcessor.process(QueryProcessor.java:151)
at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:269)
at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:213)
at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44)
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: java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "com.metamatrix.jdbcx.base.BaseXAConnection.getXAResource()Ljavax/transaction/xa/XAResource;" the class loader (instance of com/metamatrix/common/classloader/URLFilteringClassLoader) of the current class, com/metamatrix/jdbcx/base/BaseXAConnection, and the class loader (instance of <bootloader>) for interface javax/sql/XAConnection have different Class objects for the type javax/transaction/xa/XAResource used in the signature
at com.metamatrix.jdbcx.base.BaseXADataSource.getXAConnection(Unknown Source)
at org.teiid.connector.jdbc.JDBCConnector.getXAConnection(JDBCConnector.java:221)
at org.teiid.dqp.internal.pooling.connector.ConnectionPool.createConnection(ConnectionPool.java:341)
at org.teiid.dqp.internal.pooling.connector.ConnectionPool.obtain(ConnectionPool.java:269)
at org.teiid.dqp.internal.pooling.connector.PooledConnector.getXAConnectionDirect(PooledConnector.java:145)
at org.teiid.dqp.internal.datamgr.impl.ConnectorWrapper.getXAConnection(ConnectorWrapper.java:70)
at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.createConnection(ConnectorWorkItem.java:130)
at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.createExecution(ConnectorWorkItem.java:287)
at org.teiid.dqp.internal.datamgr.impl.SynchConnectorWorkItem.createExecution(SynchConnectorWorkItem.java:100)
at org.teiid.dqp.internal.datamgr.impl.ConnectorWorkItem.process(ConnectorWorkItem.java:151)
at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44)
at org.teiid.dqp.internal.datamgr.impl.SynchConnectorWorkItem.run(SynchConnectorWorkItem.java:69)
... 3 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months