[JBoss JIRA] Created: (TEIID-837) deleteVDBAndConnectorBindings gets NPE
by Paul Nittel (JIRA)
deleteVDBAndConnectorBindings gets NPE
--------------------------------------
Key: TEIID-837
URL: https://jira.jboss.org/jira/browse/TEIID-837
Project: Teiid
Issue Type: Bug
Components: AdminApi
Affects Versions: 6.2.0
Environment: fedora 10, Teiid 6.2 RC1
Reporter: Paul Nittel
Assignee: Steven Hawkins
Not too sure this method makes a lot of sense since the bindings are part of the VDB itself, but...
When it's executed from AdminShell, the following is spewed forth:
Identifier supplied can not be null and must adhere to the naming patterns; Please check the java docs for the proper naming patterns.
// Error: // Uncaught Exception: Typed variable declaration : at Line: 1020 : in file: URL: jar:file:/home/pnittel/teiid62RC1/adminshell/lib/teiid-adminshell-6.2.0-SNAPSHOT.jar!/scripts/adminapi.bsh : connectorBindings .iterator ( )
Target exception: java.lang.NullPointerException: Null Pointer in Method Invocation
In this case, I'd given this command:
deleteVDBAndConnectorBindings("NiapThing", "1");
Good news is the VDB /is/ deleted when this is executed.
--
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
16 years, 6 months
[JBoss JIRA] Created: (TEIID-841) Failed to export extension module from admin shell
by Ramesh Reddy (JIRA)
Failed to export extension module from admin shell
--------------------------------------------------
Key: TEIID-841
URL: https://jira.jboss.org/jira/browse/TEIID-841
Project: Teiid
Issue Type: Bug
Affects Versions: 6.2.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 6.2.0
admin $ connectAsAdmin("admin","teiid","mm://localhost:31000");
conn-1[mm://localhost:31000] $ exportExtensionModule("connector-text-6.2.0-SNAPSHOT.jar", "/home/pnittel/temp/foo.jar");
// Error: EvalError: Condition must evaluate to a Boolean or boolean. : at Line: 385 : in file: URL: jar:file:/home/pnittel/teiid62RC1/adminshell/lib/teiid-adminshell-6.2.0-SNAPSHOT.jar!/scripts/adminapi.bsh : contents
Called from method: exportExtensionModule : at Line: 2 : in file: <unknown file> : exportExtensionModule ( "connector-text-6.2.0-SNAPSHOT.jar" , "/home/pnittel/temp/foo.jar" )
Boolean? What Boolean?? (I like that it must evaluate to a Boolean or boolean. What's up with that?)
--
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
16 years, 6 months
[JBoss JIRA] Created: (TEIID-842) Failed to add Connector Bindings and Types using Admin API
by Ramesh Reddy (JIRA)
Failed to add Connector Bindings and Types using Admin API
----------------------------------------------------------
Key: TEIID-842
URL: https://jira.jboss.org/jira/browse/TEIID-842
Project: Teiid
Issue Type: Bug
Affects Versions: 6.2.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 6.2.0
This occurs due the remove of the "dqp.config" property from the "deploy.properties". This bug is introduced in 6.2
In absence of this property this resource is searched from the classpath and used. Since "embedded" works through url based loading, the "file://" protocol it gets loaded will no longer support the updates of underlying resources. So, user who is adding a binding or type using the admin API may see
"protocol doesn't support output"
Teiid very much like to avoid updating the "configuration.xml" file, since we can not still support the updating of properties through admin API, until other options are provided this need to be supported. By resurrecting above property, the configuration file will load with "mmfile" protocol, which will then support the updates.
--
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
16 years, 6 months
[JBoss JIRA] Created: (TEIID-826) Lob steram is being closed after the result set close
by Ramesh Reddy (JIRA)
Lob steram is being closed after the result set close
-----------------------------------------------------
Key: TEIID-826
URL: https://jira.jboss.org/jira/browse/TEIID-826
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 6.2.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Priority: Minor
Fix For: 6.2.0
While running a query on the XML document model the following exception is thrown sometimes.
2009-09-11 08:05:58,334 DEBUG [Worker12_SocketWorker160] org.teiid.QUERY_SERVICE - [Ljava.lang.Object;@1105f32
[MetaMatrixProcessingException]The request 2.4 has been cancelled.
at org.teiid.dqp.internal.process.DQPCore.getRequestWorkItem(DQPCore.java:367)
at org.teiid.dqp.internal.process.DQPCore.closeLobChunkStream(DQPCore.java:330)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.teiid.transport.ServerWorkItem.run(ServerWorkItem.java:100)
at com.metamatrix.common.queue.WorkerPoolFactory$StatsCapturingSharedThreadPoolExecutor$1.run(WorkerPoolFactory.java:211)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
--
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
16 years, 6 months
[JBoss JIRA] Created: (TEIID-835) AdminApi (thru AdminShell) allows deletion of an active VDB from under a connected user
by Paul Nittel (JIRA)
AdminApi (thru AdminShell) allows deletion of an active VDB from under a connected user
---------------------------------------------------------------------------------------
Key: TEIID-835
URL: https://jira.jboss.org/jira/browse/TEIID-835
Project: Teiid
Issue Type: Bug
Components: AdminApi
Affects Versions: 6.2.0
Environment: Fedora 10, Teiid 6.2 RC1
Reporter: Paul Nittel
Assignee: Steven Hawkins
I used two AdminShell sessions to demonstrate this: one connected as an administrator and the other connected as a user to a VDB.
Admin: addVDB("VDB name", "VDB file")
User: SELECT ...
Admin: deleteVDB("VDB name","version")
User: SELECT ...
At this point the user receives:
// Error: // Uncaught Exception: TargetError : at Line: 165 : in file: URL: jar:file:/home/pnittel/teiid62RC1/adminshell/lib/teiid-adminshell-6.2.0-SNAPSHOT.jar!/scripts/jdbc.bsh : throw e ;
Target exception: com.metamatrix.jdbc.MMSQLException: VDB "qt_db2v81ds" version "1" does not exist or not in valid state.
The MetaMatrix (Console) way of doing things is to defer deletion of the VDB until there are no active connections. Also, it was required that the VDB status be INACTIVE before the request to delete would be honored.
--
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
16 years, 6 months