[JBoss JIRA] Created: (TEIIDDES-133) SOAP Relational connector throws NPE when binding is created in Designer as part of import.
by John Doyle (JIRA)
SOAP Relational connector throws NPE when binding is created in Designer as part of import.
-------------------------------------------------------------------------------------------
Key: TEIIDDES-133
URL: https://jira.jboss.org/jira/browse/TEIIDDES-133
Project: Teiid Designer
Issue Type: Bug
Components: Teiid Integration
Affects Versions: 6.0.0
Reporter: John Doyle
A binding is create for the model at the end of the execution of the SOAP-Relational importer. An NPE is being thrown when the binding is created because the ExecutionContext passed to the connector is null.
The NPE is swallowed, so the user never sees it, but there is no binding there.
XMLConnectionImpl.<init>(CachingConnector, ExecutionContext, ConnectorEnvironment) line: 65
SOAPConnectorState(HTTPConnectorState).getConnection(CachingConnector, ExecutionContext, ConnectorEnvironment) line: 444
XMLConnector.getConnection(ExecutionContext) line: 63
ConnectorWrapper.getConnectionDirect(ExecutionContext) line: 64
ConnectorWrapper.getConnection(ExecutionContext) line: 59
ConnectorWrapper.getStatus() line: 96
ConnectorManager.getStatus() line: 286
EmbeddedDataService.getConnectorBindingState(String) line: 300
DQPConfigAdminImpl(BaseAdmin).convertConnectorType(ConnectorBinding, Object) line: 321
DQPConfigAdminImpl(BaseAdmin).convertToAdminObject(Object, Object) line: 198
DQPConfigAdminImpl(BaseAdmin).convertToAdminObjects(Object, Object) line: 191
DQPConfigAdminImpl(BaseAdmin).convertToAdminObjects(Object) line: 155
DQPConfigAdminImpl.addConnectorBinding(String, String, Properties, AdminOptions) line: 295
NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25
Method.invoke(Object, Object...) line: 597
EmbeddedConnection$1.invoke(Object, Method, Object[]) line: 111
$Proxy9.addConnectorBinding(String, String, Properties, AdminOptions) line: not available
WorkspaceExecutor.addConnectorBinding(ConnectorBinding) line: 323
WorkspaceExecutor$BindingListener.handleConnectorBindingEvent(ConfigurationChangeEvent, ConfigurationManager, String) line: 460
WorkspaceExecutor$BindingListener.stateChanged(ConfigurationChangeEvent) line: 439
ConfigurationManagerImpl.fireChangeEvent(ConfigurationChangeEvent) line: 510
ConfigurationManagerImpl.saveConfigLocal(ConfigurationChangeEvent) line: 143
ConfigurationManagerImpl.addBinding(ConnectorBinding) line: 221
SoapBindingInfo.createConnectorBinding(String, String) line: 116
RelationalModelBuilder.createModel(Collection, String, IContainer) line: 90
--
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
[JBoss JIRA] Created: (TEIIDDES-192) Unable to create vdb in Windows environment - Missing model import to resource......builtInDataTypes.xsd
by Warren Gibson (JIRA)
Unable to create vdb in Windows environment - Missing model import to resource......builtInDataTypes.xsd
--------------------------------------------------------------------------------------------------------
Key: TEIIDDES-192
URL: https://jira.jboss.org/jira/browse/TEIIDDES-192
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 6.0.0
Environment: Teiid Designer in Windows environment
Reporter: Warren Gibson
Attachments: Modelmissingimport.zip
I was creating a new set of BQT vdbs.
BQT Models in workspace were all error free. Created a vdb and when models were added to vdb the following error occurred. The vdb is not usable.
Missing model import to resource../../../Documents%2520and%2520Settings/admin.SLNTQM13/workspace5-18/.
metadata/.plugins/org.teiid.designer.vdb.edit/vdbWorkingForlder/1242654827171_57514671701635058-/builtInDataTypes.xsd
This same set of models were used to create a vdb in Linux successfully.
Project is attached.
--
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