[JBoss JIRA] (TEIID-2143) Cleanup DMR module descriptions
by Heiko Braun (JIRA)
Heiko Braun created TEIID-2143:
----------------------------------
Summary: Cleanup DMR module descriptions
Key: TEIID-2143
URL: https://issues.jboss.org/browse/TEIID-2143
Project: Teiid
Issue Type: Bug
Components: Server
Reporter: Heiko Braun
Assignee: Steven Hawkins
The DMR attribute description for "enabled-cipher-suites" requires whitespace between the possible cipher names. Otherwiese it leads to non-breakable strings that mess up the web interface help texts.
"Cipher suites that are allowed to be used for SSL. Use to restrict encryption strength(128 bit, 256 bit). Only provide encryption suites that are supported by both client and server JVM. ex:SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA,SSL_RSA_WITH_3DES_EDE_CBC_SHA,SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA,SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA,TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_DHE_DSS_WITH_AES_128_CBC_SHA,TLS_KRB5_WITH_RC4_128_MD5,TLS_KRB5_WITH_RC4_128_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_KRB5_WITH_3DES_EDE_CBC_MD5,TLS_KRB5_WITH_3DES_EDE_CBC_SHA,TLS_DHE_RSA_WITH_AES_256_CBC_SHA,TLS_DHE_DSS_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIID-2121) Getting DuplicateServiceException while creating Dynamic VDB with Teiid 8.1.0 Beta2
by Manoj Agarwal (JIRA)
Manoj Agarwal created TEIID-2121:
------------------------------------
Summary: Getting DuplicateServiceException while creating Dynamic VDB with Teiid 8.1.0 Beta2
Key: TEIID-2121
URL: https://issues.jboss.org/browse/TEIID-2121
Project: Teiid
Issue Type: Bug
Reporter: Manoj Agarwal
Assignee: Steven Hawkins
I am creating dynamic VDB and in this process i am doing addSourceMapping like this-
modelMetaData.addSourceMapping(modelName, translatorName, "java:/XYZ-DS");
The VDB XML is getting created as per my code but while deploying this i get below exception
15:19:56,566 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."xyz.1-vdb.xml".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."xyz.1-vdb.xml".INSTALL: Failed to process phase INSTALL of deployment "xyz.1-vdb.xml"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_02]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_02]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_02]
Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.teiid.ds-listener.Chorus.1.java:/XYZ-DS is already registered
at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:227) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.teiid.jboss.VDBDeployer$1.dependentService(VDBDeployer.java:163)
at org.teiid.jboss.VDBDeployer.dataSourceDependencies(VDBDeployer.java:265)
at org.teiid.jboss.VDBDeployer.deploy(VDBDeployer.java:157)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIID-2115) Designer VDB with WebService model failed to deploy
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2115:
-----------------------------------
Summary: Designer VDB with WebService model failed to deploy
Key: TEIID-2115
URL: https://issues.jboss.org/browse/TEIID-2115
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.1
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Priority: Critical
Fix For: 8.1
Attachments: TxnService.vdb
Trying deploy a VDB with Web service and XML models is having metadata resolution issues during deploy.
{code}
11:18:07,636 WARN [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 3) TEIID31080 View PostgreTxn_WS.PostgreTxn_g1.getg1 validation error: QueryResolverException-Group does not exist: PostgreTxn_Output_View.g1_OutputView
11:18:07,638 WARN [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 3) TEIID31080 View PostgreTxn_WS.PostgreTxn_g2.getg2 validation error: QueryResolverException-Group does not exist: PostgreTxn_Output_View.g2_OutputView
11:18:07,639 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID40073 The metadata for the VDB TxnService.1 is loaded, however it is not valid. Check models for errors. Correct the metadata and re-deploy.
{code}
I originally remembered to skip the model validation on these types of models.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIID-2151) Passthrough authentication is not working shows below exception
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2151:
-----------------------------------
Summary: Passthrough authentication is not working shows below exception
Key: TEIID-2151
URL: https://issues.jboss.org/browse/TEIID-2151
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.1
{code}
Caused by: org.teiid.core.TeiidComponentException: ASSERTION FAILED: expected reference to be not null
at org.teiid.client.util.ExceptionUtil.convertException(ExceptionUtil.java:60) [teiid-client-8.1.0.Beta2-SNAPSHOT.jar:8.1.0.Beta2-SNAPSHOT]
at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:137) [teiid-runtime-8.1.0.Beta2-SNAPSHOT.jar:8.1.0.Beta2-SNAPSHOT]
at $Proxy18.executeRequest(Unknown Source) at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:640) [teiid-client-8.1.0.Beta2-SNAPSHOT.jar:8.1.0.Beta2-SNAPSHOT]
{code}
The reason looks like the "passthrough" connection property check is being done after the 'authentcation()' call on the LocalServerConnection
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIID-2062) Produce an embeddable Teiid engine
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2062:
-------------------------------------
Summary: Produce an embeddable Teiid engine
Key: TEIID-2062
URL: https://issues.jboss.org/browse/TEIID-2062
Project: Teiid
Issue Type: Enhancement
Components: Embedded
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.1
Teiid's federation and query processing features are of use to several other projects. An embeddedable form is desired such that:
- the application server is not required
- queries could be issued in the engine object model to by-pass parsing/validation and results retrieved without the need for JDBC
- new translators could be added
The following would be open for discussion:
- the inclusion of saxon/xom/nux for SQL/XML processing
- if the general deployment logic would be needed, or if just a single dynamic vdb is all that is needed
See the org.teiid.jdbc.FakeServer in the test-integration/common module for a rough approximation at the entry point for a embeddable server. Note that it is more geared at unit testing JDBC/ODBC rather than providing the features needed here.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] Created: (TEIID-1598) translator scoped result set caching
by Mark Addleman (JIRA)
translator scoped result set caching
------------------------------------
Key: TEIID-1598
URL: https://issues.jboss.org/browse/TEIID-1598
Project: Teiid
Issue Type: Feature Request
Reporter: Mark Addleman
Assignee: Steven Hawkins
Priority: Minor
Something Steven mentioned in Teiid-1589 got me thinking: It would be helpful for individual translators to request that Teiid cache results sets that match the query as presented to the execution factory (after the planner is done rewriting the query based on the translator's capabilities).
I envision a new method on an Execution getCacheTtlMs() where zero or negative indicates that Teiid shouldn't cache the results.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month