[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 …
[View More]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
[View Less]
15 years, 2 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 …
[View More]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
[View Less]
15 years, 2 months
[JBoss JIRA] Created: (TEIIDDES-196) Change default for UDF property *deterministic* from false to true to improve usability
by Jerry Helbling (JIRA)
Change default for UDF property *deterministic* from false to true to improve usability
---------------------------------------------------------------------------------------
Key: TEIIDDES-196
URL: https://jira.jboss.org/jira/browse/TEIIDDES-196
Project: Teiid Designer
Issue Type: Bug
Components: Modeling
Affects Versions: 6.1.0
Reporter: Jerry Helbling
Priority: Minor
[related to internal case …
[View More]IT281239]
Change the default value for the 'deterministic' property of User Defined Functions to true, so UDFs will be specified as 'deterministic' by default.
Currently the default value for the 'deterministic' property of User Defined Functions is false. It is probably false because that is the usual default for a boolean property. This is a usability issue because a user who creates a new UDF without paying attention to, and explicitly setting this property will wind up creating a non-deterministic UDF, by default.
That is a bad outcome for several reasons. First, most Functions, including User Defined Functions, are deterministic, not non-deterministic. So in most cases the current default makes it more likely that this property will be specified incorrectly. Secondly, specifying that a UDF is non-deterministic when it is really deterministic may create unnecessary performance issues. For example, the planner has the ability to optimize the placement of a deterministic function so that it can be called the fewest number of times. It is unable to do that with non-deterministic functions. More critically, a change was made to all versions in Feb 2009 (see Jira TEIID-16) that prevents the merging of queries if one of them contains a non-deterministic function. This can have a dramatically negative effect on performance (see internal case IT281239).
--
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
[View Less]
15 years, 10 months