[JBoss JIRA] Closed: (TEIID-1325) Teiid Admin connection re-connect fails every time
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1325?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-1325.
---------------------------------
> Teiid Admin connection re-connect fails every time
> --------------------------------------------------
>
> Key: TEIID-1325
> URL: https://issues.jboss.org/browse/TEIID-1325
> Project: Teiid
> Issue Type: Bug
> Components: AdminApi
> Affects Versions: 7.1.1
> Environment: F12, JBDS4.0.0-Beta1
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 7.1.1
>
>
> 1) Start the Teiid Server (JBoss AS) then start the JBoss Tools with Teiid Designer.
> 2) Configure the Designer to connect to Teiid Server using the Admin Connection.
> 3) Make sure the it has valid connection
> 4) Shutdown the Teiid Server
> 5) Refresh the Teiid Connection in Desinger, which will fail to connect to server (expected as the Server is down)
> 6) Now start the Server back up, and then using Designer, try to re-connect. This operation always fails with below exception
> java.lang.NullPointerException
> 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.teiid.adminapi.AdminFactory$AdminProxy.invoke(AdminFactory.java:80)
> at $Proxy2.getTranslators(Unknown Source)
> at org.teiid.designer.runtime.ExecutionAdmin.refresh(ExecutionAdmin.java:318)
> at org.teiid.designer.runtime.ui.ReconnectToServerAction$1.run(ReconnectToServerAc
> The only way to fix it discard the connection information, and create a new Teiid Instance.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Assigned: (TEIID-1427) Class not found in Teiid JON agent
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIID-1427?page=com.atlassian.jira.plugin... ]
Ted Jones reassigned TEIID-1427:
--------------------------------
Assignee: Ted Jones
> Class not found in Teiid JON agent
> ----------------------------------
>
> Key: TEIID-1427
> URL: https://issues.jboss.org/browse/TEIID-1427
> Project: Teiid
> Issue Type: Bug
> Components: Jopr Plugin
> Affects Versions: 7.1.1
> Reporter: Paul Nittel
> Assignee: Ted Jones
> Priority: Blocker
> Attachments: agent.log.zip
>
>
> While trying to delete a VDB form my server, it was noticed the agent's log showed a missing class.
> 2011-01-07 10:26:54,366 WARN [MeasurementManager.collector-1] (rhq.core.pc.measurement.MeasurementCollectorRunner)- Failure to collect measurement data for Resource[id=10301, type=Data Services, key=RuntimeEngineDeployer, name=Data Services, parent=sllxqm27:1099 production, version=7.1.1] - cause: java.lang.Exception:java.lang.NoClassDefFoundError: Could not initialize class org.teiid.adminapi.impl.SessionMetadataMapper -> java.lang.NoClassDefFoundError:Could not initialize class org.teiid.adminapi.impl.SessionMetadataMapper
> Attaching the whole log file for further analysis.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Moved: (TEIID-1427) Class not found in Teiid JON agent
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIID-1427?page=com.atlassian.jira.plugin... ]
Ted Jones moved SOA-2756 to TEIID-1427:
---------------------------------------
Project: Teiid (was: JBoss Enterprise SOA Platform)
Key: TEIID-1427 (was: SOA-2756)
Affects Version/s: 7.1.1
(was: 5.1.0.ER6)
Component/s: Jopr Plugin
(was: JON)
Security: (was: Public)
> Class not found in Teiid JON agent
> ----------------------------------
>
> Key: TEIID-1427
> URL: https://issues.jboss.org/browse/TEIID-1427
> Project: Teiid
> Issue Type: Bug
> Components: Jopr Plugin
> Affects Versions: 7.1.1
> Reporter: Paul Nittel
> Priority: Blocker
> Attachments: agent.log.zip
>
>
> While trying to delete a VDB form my server, it was noticed the agent's log showed a missing class.
> 2011-01-07 10:26:54,366 WARN [MeasurementManager.collector-1] (rhq.core.pc.measurement.MeasurementCollectorRunner)- Failure to collect measurement data for Resource[id=10301, type=Data Services, key=RuntimeEngineDeployer, name=Data Services, parent=sllxqm27:1099 production, version=7.1.1] - cause: java.lang.Exception:java.lang.NoClassDefFoundError: Could not initialize class org.teiid.adminapi.impl.SessionMetadataMapper -> java.lang.NoClassDefFoundError:Could not initialize class org.teiid.adminapi.impl.SessionMetadataMapper
> Attaching the whole log file for further analysis.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Commented: (TEIID-1336) EDS adminshell - clearCache() having no effect
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-1336?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-1336:
-------------------------------------
Please provide the test case you are testing to check the correct scenario.
> EDS adminshell - clearCache() having no effect
> ----------------------------------------------
>
> Key: TEIID-1336
> URL: https://issues.jboss.org/browse/TEIID-1336
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.1.1
> Environment: SOA-P 5.1 ER3 build
> Reporter: Len DiMaggio
> Assignee: Ramesh Reddy
> Priority: Blocker
> Fix For: 7.1.1
>
>
> clearCache() doesn't look like it's doing anything - see below:
> groovy:000> connectAsAdmin("mms://localhost:31443", "admin", "admin", "conn-1")
> ===> null
> groovy:000> getCacheStats("QUERY_SERVICE_RESULT_SET_CACHE")
> ===> hitRatio=0.0; totalEntries=0; requestCount=3
> groovy:000> clearCache("QUERY_SERVICE_RESULT_SET_CACHE")
> ===> null
> groovy:000> getCacheStats("QUERY_SERVICE_RESULT_SET_CACHE")
> ===> hitRatio=0.0; totalEntries=0; requestCount=3
> ===================
> server.log:
> 2010-10-29 12:13:07,065 DEBUG [org.teiid.TRANSPORT] (New I/O server worker #2-1) processing message:MessageHolder: contents=org.teiid.net.socket.ServiceInvocationStruct@18cf5ea
> 2010-10-29 12:13:07,065 DEBUG [org.teiid.SECURITY] (New I/O server worker #2-1) Ping MLwHWKFcHgcq
> 2010-10-29 12:13:07,065 DEBUG [org.teiid.TRANSPORT] (New I/O server worker #2-1) message: MessageHolder: contents=null for request ID:38
> 2010-10-29 12:13:07,067 DEBUG [org.teiid.TRANSPORT] (New I/O server worker #2-1) processing message:MessageHolder: contents=org.teiid.net.socket.ServiceInvocationStruct@c171b7
> 2010-10-29 12:13:07,067 DEBUG [org.teiid.ADMIN_API] (New I/O server worker #2-1) before clearCache:org.teiid.adminapi.jboss.Admin@1a42c71(QUERY_SERVICE_RESULT_SET_CACHE)
> 2010-10-29 12:13:07,067 DEBUG [org.teiid.ADMIN_API] (New I/O server worker #2-1) after clearCache : null
> 2010-10-29 12:13:07,067 DEBUG [org.teiid.TRANSPORT] (New I/O server worker #2-1) message: MessageHolder: contents=null for request ID:39
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Updated: (TEIID-1336) EDS adminshell - clearCache() having no effect
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-1336?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-1336:
-------------------------------
Priority: Blocker (was: Major)
> EDS adminshell - clearCache() having no effect
> ----------------------------------------------
>
> Key: TEIID-1336
> URL: https://issues.jboss.org/browse/TEIID-1336
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.1.1
> Environment: SOA-P 5.1 ER3 build
> Reporter: Len DiMaggio
> Assignee: Ramesh Reddy
> Priority: Blocker
> Fix For: 7.1.1
>
>
> clearCache() doesn't look like it's doing anything - see below:
> groovy:000> connectAsAdmin("mms://localhost:31443", "admin", "admin", "conn-1")
> ===> null
> groovy:000> getCacheStats("QUERY_SERVICE_RESULT_SET_CACHE")
> ===> hitRatio=0.0; totalEntries=0; requestCount=3
> groovy:000> clearCache("QUERY_SERVICE_RESULT_SET_CACHE")
> ===> null
> groovy:000> getCacheStats("QUERY_SERVICE_RESULT_SET_CACHE")
> ===> hitRatio=0.0; totalEntries=0; requestCount=3
> ===================
> server.log:
> 2010-10-29 12:13:07,065 DEBUG [org.teiid.TRANSPORT] (New I/O server worker #2-1) processing message:MessageHolder: contents=org.teiid.net.socket.ServiceInvocationStruct@18cf5ea
> 2010-10-29 12:13:07,065 DEBUG [org.teiid.SECURITY] (New I/O server worker #2-1) Ping MLwHWKFcHgcq
> 2010-10-29 12:13:07,065 DEBUG [org.teiid.TRANSPORT] (New I/O server worker #2-1) message: MessageHolder: contents=null for request ID:38
> 2010-10-29 12:13:07,067 DEBUG [org.teiid.TRANSPORT] (New I/O server worker #2-1) processing message:MessageHolder: contents=org.teiid.net.socket.ServiceInvocationStruct@c171b7
> 2010-10-29 12:13:07,067 DEBUG [org.teiid.ADMIN_API] (New I/O server worker #2-1) before clearCache:org.teiid.adminapi.jboss.Admin@1a42c71(QUERY_SERVICE_RESULT_SET_CACHE)
> 2010-10-29 12:13:07,067 DEBUG [org.teiid.ADMIN_API] (New I/O server worker #2-1) after clearCache : null
> 2010-10-29 12:13:07,067 DEBUG [org.teiid.TRANSPORT] (New I/O server worker #2-1) message: MessageHolder: contents=null for request ID:39
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (TEIID-1425) Teiid should take care of salesforce query limits by itself
by Van Halbert (JIRA)
Teiid should take care of salesforce query limits by itself
-----------------------------------------------------------
Key: TEIID-1425
URL: https://issues.jboss.org/browse/TEIID-1425
Project: Teiid
Issue Type: Feature Request
Components: Salesforce Connector
Affects Versions: 7.1.1, 7.2, 7.3
Environment: Teiid 7.1.1 on EAP 5.1 with CXF
Reporter: Wanja Pernath
Assignee: Steven Hawkins
Salesforce has a query string limit of 10.000 chars. When Teiid is calculating and executing a query like this:
SELECT Opportunity where AccountId in (a,b,c,d,e,f,g,h,i)
It could extend the 10.000 chars limit of Salesforce. Right now teiid just stops with an Exception.
Expected behavior is to have teiid splitting up the condition into correct portions and to execute the above query n times to circumvent the limit:
SELECT Opportunity where AccountId in (a, b, c);
SELECT Opportunity where AccountId in (d, e, f);
SELECT Opportunity where AccountId in (g, h, i);
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Reopened: (TEIID-1336) EDS adminshell - clearCache() having no effect
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-1336?page=com.atlassian.jira.plugin... ]
Van Halbert reopened TEIID-1336:
--------------------------------
> EDS adminshell - clearCache() having no effect
> ----------------------------------------------
>
> Key: TEIID-1336
> URL: https://issues.jboss.org/browse/TEIID-1336
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.1.1
> Environment: SOA-P 5.1 ER3 build
> Reporter: Len DiMaggio
> Assignee: Ramesh Reddy
> Fix For: 7.1.1
>
>
> clearCache() doesn't look like it's doing anything - see below:
> groovy:000> connectAsAdmin("mms://localhost:31443", "admin", "admin", "conn-1")
> ===> null
> groovy:000> getCacheStats("QUERY_SERVICE_RESULT_SET_CACHE")
> ===> hitRatio=0.0; totalEntries=0; requestCount=3
> groovy:000> clearCache("QUERY_SERVICE_RESULT_SET_CACHE")
> ===> null
> groovy:000> getCacheStats("QUERY_SERVICE_RESULT_SET_CACHE")
> ===> hitRatio=0.0; totalEntries=0; requestCount=3
> ===================
> server.log:
> 2010-10-29 12:13:07,065 DEBUG [org.teiid.TRANSPORT] (New I/O server worker #2-1) processing message:MessageHolder: contents=org.teiid.net.socket.ServiceInvocationStruct@18cf5ea
> 2010-10-29 12:13:07,065 DEBUG [org.teiid.SECURITY] (New I/O server worker #2-1) Ping MLwHWKFcHgcq
> 2010-10-29 12:13:07,065 DEBUG [org.teiid.TRANSPORT] (New I/O server worker #2-1) message: MessageHolder: contents=null for request ID:38
> 2010-10-29 12:13:07,067 DEBUG [org.teiid.TRANSPORT] (New I/O server worker #2-1) processing message:MessageHolder: contents=org.teiid.net.socket.ServiceInvocationStruct@c171b7
> 2010-10-29 12:13:07,067 DEBUG [org.teiid.ADMIN_API] (New I/O server worker #2-1) before clearCache:org.teiid.adminapi.jboss.Admin@1a42c71(QUERY_SERVICE_RESULT_SET_CACHE)
> 2010-10-29 12:13:07,067 DEBUG [org.teiid.ADMIN_API] (New I/O server worker #2-1) after clearCache : null
> 2010-10-29 12:13:07,067 DEBUG [org.teiid.TRANSPORT] (New I/O server worker #2-1) message: MessageHolder: contents=null for request ID:39
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (TEIID-1423) Limit pushing can result in inconsistent xml results
by Van Halbert (JIRA)
Limit pushing can result in inconsistent xml results
----------------------------------------------------
Key: TEIID-1423
URL: https://issues.jboss.org/browse/TEIID-1423
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Critical
Fix For: 7.1.1, 7.3
A customer case (00393370) was using rowlimitexception and not actually triggering the exception when expected. This is due to our logic in rulepushlimit that allows an unordered limit to be pushed through union not all, select nodes, or dup removal. While the results may be consistent for some ordering of results there are many situations when you will get back far less results than the limit specifies. The intent was to more broadly push the limit rather than to apply it in a fully consistent manner. However this is problematic for situations, like the rowlimitexception logic that expect an exceptional condition to be triggered if the limit is exceeded.
The best fix would be to just not push an unordered limit in these situations, then if the more aggressive pushing is desired by a user we can look at using a hint or some other mechanism to allow the pushing.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months