[JBoss JIRA] Created: (TEIID-1332) After updating ManagedComponent value via ProfileService, Teiid JOPR components get Availability down
by Cristiano Nicolai (JIRA)
After updating ManagedComponent value via ProfileService, Teiid JOPR components get Availability down
------------------------------------------------------------------------------------------------------
Key: TEIID-1332
URL: https://jira.jboss.org/browse/TEIID-1332
Project: Teiid
Issue Type: Bug
Components: Jopr Plugin
Affects Versions: 7.2
Environment: JbossAS 5.1
Reporter: Cristiano Nicolai
…
[View More] Assignee: Steven Hawkins
Attachments: SimpleUpdate.java
After updating some Teiid ManagementComponent value via ProfileService their availability status in Admin Console are showed as down but after refreshing the page causes the status to be up again.
The main problem is that the ManagementView isn't refreshed after the ManagementComponent is updated.
To fix it, all Teiid JOPR components (DataRoleComponent, PlatformComponent, TranslatorComponent, VDBComponent) must call managementView.load() after updating the ManagementComponent in updateResourceConfiguration method.
This problem cause the JON Agent Plugin to report the JON server that the services are DOWN.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
14 years
[JBoss JIRA] Created: (TEIID-1399) Adding ORDER BY to SELECT COUNT(*) FROM ... returns org.teiid.core.TeiidProcessingException: null to client - Needs clearer message
by Paul Nittel (JIRA)
Adding ORDER BY to SELECT COUNT(*) FROM ... returns org.teiid.core.TeiidProcessingException: null to client - Needs clearer message
-----------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-1399
URL: https://issues.jboss.org/browse/TEIID-1399
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.1.1
…
[View More]Reporter: Paul Nittel
Assignee: Steven Hawkins
I had quickly queried SELECT COUNT(*) FROM sometable ORDER BY ColA, ColB and received org.teiid.core.TeiidProcessingException: null as a result. Checking the server, I found the stack trace below. Neither actually points out the ORDER BY is incorrect since it does not reference projected columns.
A clearer message will help the users.
2010-12-14 12:54:05,010 ERROR [org.teiid.CONNECTOR] (Worker28_QueryProcessorQueue2669) Connector worker process failed for atomic-request=J76UbF11tQAM.0.1.753
java.lang.AssertionError
at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:504)
at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:432)
at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:207)
at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:130)
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:213)
at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:281)
at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:71)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:123)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:120)
at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:108)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:188)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:116)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:290)
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)
2010-12-14 12:54:05,042 WARN [org.teiid.PROCESSOR] (Worker27_QueryProcessorQueue2670) Processing exception 'null' for request J76UbF11tQAM.0. Exception type org.teiid.core.TeiidProcessingException thrown from org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:504). Enable more detailed logging to see the entire stacktrace.
2010-12-14 12:54:20,404 ERROR [org.teiid.CONNECTOR] (Worker28_QueryProcessorQueue2673) Connector worker process failed for atomic-request=Tfqv5NFZIOX4.0.1.754
java.lang.AssertionError
at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:504)
at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:432)
at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:207)
at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:130)
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:213)
at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:281)
at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:71)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:123)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:120)
at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:108)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:188)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:116)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:290)
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)
2010-12-14 12:54:20,405 WARN [org.teiid.PROCESSOR] (Worker27_QueryProcessorQueue2674) Processing exception 'null' for request Tfqv5NFZIOX4.0. Exception type org.teiid.core.TeiidProcessingException thrown from org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:504). Enable more detailed logging to see the entire stacktrace.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
14 years
[JBoss JIRA] Closed: (TEIID-1391) Changes to the use of SSL when connecting with the Teiid Driver are ignored after a successful connection
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1391?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-1391.
---------------------------------
> Changes to the use of SSL when connecting with the Teiid Driver are ignored after a successful connection
> ---------------------------------------------------------------------------------------------------------
>
> Key: TEIID-1391
> URL: https://issues.jboss.org/browse/TEIID-1391
> …
[View More] Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Affects Versions: 7.1.1
> Reporter: John Verhaeg
> Assignee: Steven Hawkins
> Fix For: 7.1.1, 7.3
>
>
> This might be a bit hard to follow, but...
> I tried to execute a Teiid VDB from the Teiid Designer perspective, which asks me to create a Teiid connection profile, which displays the Teiid driver properties dialog. Not knowing whether the server I was using was configured for SSL, I went ahead and selected the SSL option and hit Test. It failed (as expected). I then unchecked that checkbox, retested, and the test ping succeeded. But then I re-checked the box and tried once more. It succeeded again (Huh?). I then hit Finish, and got a failure message after being transferred to the DTP perspective. Seeing the connection profile in the Data Source Explorer, I opened its context menu, which showed an option to disconnect (implying it was still in a connected state). I disconnected and then tried to reconnect. Again, that worked. Opening the connection's profile and changing its SSL setting has no effect after that. Only if I completely remove the connection and recreate it can I see the SSL option fail again, but only until I turn it off and get the connection to succeed. Thereafter the setting seems to once again be ignored.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
14 years