[JBoss JIRA] (TEIID-2208) NPE in server log when triggering operation from admin console
by Van Halbert (JIRA)
Van Halbert created TEIID-2208:
----------------------------------
Summary: NPE in server log when triggering operation from admin console
Key: TEIID-2208
URL: https://issues.jboss.org/browse/TEIID-2208
Project: Teiid
Issue Type: Bug
Components: Jopr Plugin
Affects Versions: 7.7.1
Reporter: Van Halbert
Assignee: Steven Hawkins
When using admin console, saw the following NPE in the server log:
08:15:40,928 ERROR [MeasurementManager] Could not get measurement values
java.lang.NullPointerException
at org.teiid.rhq.admin.DQPManagementView.getErrorCount(DQPManagementView.java:666)
at org.teiid.rhq.admin.DQPManagementView.getVdbMetric(DQPManagementView.java:158)
at org.teiid.rhq.admin.DQPManagementView.getMetric(DQPManagementView.java:110)
at org.teiid.rhq.plugin.VDBComponent.getValues(VDBComponent.java:178)
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.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
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:680)
Not sure what combination of control operations that I pressed that caused this. And I've yet to duplicate.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (TEIID-2216) Refreshing VDB display may show all VDBs as DOWN
by Paul Nittel (JIRA)
Paul Nittel created TEIID-2216:
----------------------------------
Summary: Refreshing VDB display may show all VDBs as DOWN
Key: TEIID-2216
URL: https://issues.jboss.org/browse/TEIID-2216
Project: Teiid
Issue Type: Bug
Components: Jopr Plugin
Reporter: Paul Nittel
Assignee: Steven Hawkins
Priority: Minor
I've noticed this on several occasions and it doesn't seem to be readily repeatable (sorry). Under the right(?) circumstances, refreshing the VDB display shows all the VDBs to be DOWN.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (TEIID-2300) executeUpdate is too restrictive
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2300:
-------------------------------------
Summary: executeUpdate is too restrictive
Key: TEIID-2300
URL: https://issues.jboss.org/browse/TEIID-2300
Project: Teiid
Issue Type: Bug
Components: JDBC Driver, Query Engine
Affects Versions: 8.1
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
executeUpdate should allow any statement to execute as long as it does not return a resultset.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (TEIID-2291) NPE during "get-query-plan" CLI request
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2291:
-----------------------------------
Summary: NPE during "get-query-plan" CLI request
Key: TEIID-2291
URL: https://issues.jboss.org/browse/TEIID-2291
Project: Teiid
Issue Type: Bug
Components: AdminApi
Affects Versions: 8.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.2
{code}
10:22:47,609 ERROR [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 26) JBAS014612: Operation ("get-query-plan") failed - address: ([("subsystem" => "teiid")]): java.lang.NullPointerException
at org.teiid.jboss.GetPlan.executeOperation(TeiidOperationHandler.java:482) [teiid-jboss-integration-8.2.0.CR1-SNAPSHOT.jar:8.2.0.CR1-SNAPSHOT]
at org.teiid.jboss.GetPlan.executeOperation(TeiidOperationHandler.java:467) [teiid-jboss-integration-8.2.0.CR1-SNAPSHOT.jar:8.2.0.CR1-SNAPSHOT]
at org.teiid.jboss.BaseOperationHandler$1.execute(BaseOperationHandler.java:71) [teiid-jboss-integration-8.2.0.CR1-SNAPSHOT.jar:8.2.0.CR1-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (TEIID-2262) Add ability to move VDB to ACTIVE/UP state from Admin Console
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2262?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2262.
---------------------------------
> Add ability to move VDB to ACTIVE/UP state from Admin Console
> -------------------------------------------------------------
>
> Key: TEIID-2262
> URL: https://issues.jboss.org/browse/TEIID-2262
> Project: Teiid
> Issue Type: Feature Request
> Components: Jopr Plugin
> Reporter: Marc Shirley
>
> Currently, a VDB that is deployed to a server, but does not deploy successfully (for instance, because a datasource referenced by the VDB is not active) must be redeployed to the server to fix the inactive status. In the case of an incorrect JNDI name being used within the VDB, the JNDI name can be corrected through the Admin Console, but there is no way to redeploy or move the VDB to an active state from the Admin Console. This causes confusion due to being able to make changes to the configuration, but not being able to effect those changes on a currently INACTIVE/DOWN status VDB.
> There was expectation to be able to administer the VDB from Admin Console due to the ability to alter the configuration properties in the UI. However, if the initial deployment fails and results in the VDB being marked as DOWN/INACTIVE, then they are unable to rectify this without fully redeploying the VDB.
> Would like the ability to update the JNDI names and effect those changes on the currently deployed VDB to move it from an INACTIVE to an ACTIVE state.
> This can be tested with the below steps:
> 1) Configure a VDB with an incorrect JNDI name
> 2) Deploy the VDB to an EDS server
> 3) Log into the Admin Console
> 4) Navigate to the VDB
> 5) Confirm the VDB is listed in an INACTIVE state
> 5) Modify the incorrect JNDI name to point to a valid datasource
> 6) Confirm that the VDB has moved to an ACTIVE state
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (TEIID-2181) SYS queries should filter by schema/table
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2181:
-------------------------------------
Summary: SYS queries should filter by schema/table
Key: TEIID-2181
URL: https://issues.jboss.org/browse/TEIID-2181
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
The tables returned by datatiermanagerimpl are returned in full for each request generating a lot of tuple garbage. It would be better to allow filtering (ideally using schema/table name lookups) as we build the result.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months