[JBoss JIRA] Created: (TEIID-436) Error Installing Teiid with a Postgres Repository
by Ted Jones (JIRA)
Error Installing Teiid with a Postgres Repository
-------------------------------------------------
Key: TEIID-436
URL: https://jira.jboss.org/jira/browse/TEIID-436
Project: Teiid
Issue Type: Bug
Components: JDBC Driver
Affects Versions: 6.0.0
Reporter: Ted Jones
Assignee: Steven Hawkins
While running setupmm with a local Postgres repository, I encountered the following fatal error:
/home/tejones/apps/EnterpriseDataServicesPlatform/03202009/server-0.0.1-SNAPSHOT/config/install/setup_server.xml:453: [MetaMatrixComponentException] ERR.014.004.0054: Error inserting extension module Next Startup using SQL statement: INSERT INTO CS_EXT_FILES(FILE_UID,CHKSUM,FILE_NAME,SEARCH_POS,IS_ENABLED,FILE_DESC,CREATED_BY,CREATION_DATE,UPDATED_BY,UPDATE_DATE,FILE_TYPE) VALUES
1 [DBIDGeneratorException] ERR.003.013.0011: Error creating id for CS_EXT_FILES context.
2 [DBIDGeneratorException] ERR.003.013.0014: Could not obtain a unique ID blocksize of 100 for context CS_EXT_FILES.
3 [ManagedConnectionException] ERR.003.013.0016: Unable to obtain the managed connection for the DBID transaction
4 [MetaMatrixException] ERR.003.015.0003: JDBCPlatform Program Error, unable to create platform.
5 [MetaMatrixException] ERR.003.015.0003: JDBCPlatform Program Error, unable to create platform.
6 [IllegalArgumentException]
--
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
15 years, 8 months
[JBoss JIRA] Updated: (TEIID-503) startHost( badHostName ) causes MMProcess to loop, trying to ping bad host name
by Steven Hawkins (JIRA)
[ https://jira.jboss.org/jira/browse/TEIID-503?page=com.atlassian.jira.plug... ]
Steven Hawkins updated TEIID-503:
---------------------------------
Component/s: Server
Fix Version/s: 6.1.1
> startHost( badHostName ) causes MMProcess to loop, trying to ping bad host name
> -------------------------------------------------------------------------------
>
> Key: TEIID-503
> URL: https://jira.jboss.org/jira/browse/TEIID-503
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 6.0.0
> Environment: fedora 10, 553GA
> Reporter: Paul Nittel
> Fix For: 6.1.1
>
>
> Persistence is a virtue, but not when it comes to computers. ;-)
> I created a test for mmadmin which tried to start a host with a bad name. (I figured it would give me an error and the test could proceed from there.) What happened was the test didn't end in a reasonable time, but the server's process log was growing. Turns out it was filling with these:
> Mar 13, 2009 09:34:00.650 [SocketWorkerQueue_Worker_357|0] ERROR <com.metamatrix.platform|0> Unable to ping bindaddress: CCEtest
> Mar 13, 2009 09:34:00.650 [SocketWorkerQueue_Worker_357|0] ERROR <com.metamatrix.platform|0> Unable to ping bindaddress: CCEtest
> Mar 13, 2009 09:34:00.650 [SocketWorkerQueue_Worker_357|0] ERROR <com.metamatrix.platform|0> Unable to ping bindaddress: CCEtest
> Offhand, I'd say one would be sufficient.
--
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
15 years, 8 months
[JBoss JIRA] Moved: (TEIID-502) Allow Multiple UDF Definition Models
by Steven Hawkins (JIRA)
[ https://jira.jboss.org/jira/browse/TEIID-502?page=com.atlassian.jira.plug... ]
Steven Hawkins moved JBEDSP-731 to TEIID-502:
---------------------------------------------
Project: Teiid (was: JBoss Enterprise Data Services Platform)
Key: TEIID-502 (was: JBEDSP-731)
Component/s: Query Engine
(was: Server)
Fix Version/s: 6.2.0
(was: PostWestport)
> Allow Multiple UDF Definition Models
> ------------------------------------
>
> Key: TEIID-502
> URL: https://jira.jboss.org/jira/browse/TEIID-502
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Debbie Steigner
> Assignee: Ramesh Reddy
> Fix For: 6.2.0
>
>
> Customer feature request from Issue Tracker ticket# 228151:
> The current mechanism for UDF (user-defined functions) is limited to having one model (FunctionDefinitions.xmi) in which UDF are defined and related to their Java implementations. This results in a configuration management problem even on just one project. For multiple projects it becomes a nightmare, unless we abandon all hope of building a body of reusable UDFs. I would therefore suggest that designer and server need to support multiple UDF definition models, identified by the extensions already defined and used for FunctionDefinitions.xmi.
> Similar to JBEDSP-632
--
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
15 years, 9 months