[JBoss JIRA] Created: (TEIID-672) Replace homegrown Logging with Log4J
by Ramesh Reddy (JIRA)
Replace homegrown Logging with Log4J
------------------------------------
Key: TEIID-672
URL: https://jira.jboss.org/jira/browse/TEIID-672
Project: Teiid
Issue Type: Task
Components: Common
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 6.2.0
Teiid has Logging framework as well the implementation that supports the frame work, like Log Listeners, File appenders and Rolling File appenders, Platform loggers etc. Except for LogManager.java and its required constants, everything else can be replaced with Log4J implementation.
Designer seems to be only dependent upon the "Logger" interface, so that will be kept.
A "log4j.properties" configured for "embedded" and "server" runtimes to configure the logging destinations.
--
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
16 years, 8 months
[JBoss JIRA] Created: (TEIID-540) Embed Serv; et Container in Teiid
by Ted Jones (JIRA)
Embed Serv;et Container in Teiid
--------------------------------
Key: TEIID-540
URL: https://jira.jboss.org/jira/browse/TEIID-540
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 6.0.0
Reporter: Ted Jones
Assignee: Steven Hawkins
Fix For: 6.2.0
Embedding a servlet container into the same VM as Teiid will give us more flexibility in that the server will be running in the same VM as our Data Services and allow us to more easily integrate SAML, Password Digest, and other security solutions by giving the server access to the connection pool used by data services.
This will also make us "appear" more seamless and not depend on external app servers. All the configuration can be controlled via our own processes (AdminAPI, Jopr).
One possible servlet container is Jetty. It is robust and widely used/supported.
--
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
16 years, 8 months
[JBoss JIRA] Created: (TEIID-592) Error synchronizing the server from the console
by Van Halbert (JIRA)
Error synchronizing the server from the console
-----------------------------------------------
Key: TEIID-592
URL: https://jira.jboss.org/jira/browse/TEIID-592
Project: Teiid
Issue Type: Bug
Components: Console, Server
Affects Versions: 6.1.0
Reporter: Van Halbert
Assignee: Van Halbert
Getting the following exception when trying to synchronize the server:
Error Code:ERR.003.030.0071 Message:Error Code:ERR.003.030.0071 Message:Error Code:ERR.003.030.0071 Message:Decryption failed: java.io.InvalidClassException com.metamatrix.api.exception.MultipleException; com.metamatrix.api.exception.MultipleException; no valid constructor < RuntimeMgmtManager.synchronizeServer >ExternalException: [ExternalException] ERR.003.030.0071: Error Code:ERR.003.030.0071 Message:Error Code:ERR.003.030.0071 Message:Error Code:ERR.003.030.0071 Message:Decryption failed: java.io.InvalidClassException com.metamatrix.api.exception.MultipleException; com.metamatrix.api.exception.MultipleException; no valid constructor < RuntimeMgmtManager.synchronizeServer >
1 [MetaMatrixComponentException] ERR.003.030.0071: Error Code:ERR.003.030.0071 Message:Error Code:ERR.003.030.0071 Message:Decryption failed: java.io.InvalidClassException com.metamatrix.api.exception.MultipleException; com.metamatrix.api.exception.MultipleException; no valid constructor
2 [CryptoException] ERR.003.030.0071: Error Code:ERR.003.030.0071 Message:Decryption failed: java.io.InvalidClassException com.metamatrix.api.exception.MultipleException; com.metamatrix.api.exception.MultipleException; no valid constructor
at com.metamatrix.console.models.RuntimeMgmtManager.synchronizeServer(RuntimeMgmtManager.java:508)
at com.metamatrix.console.ui.views.runtime.RuntimeMgmtPanel$4.run(RuntimeMgmtPanel.java:771)
--
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
16 years, 8 months
[JBoss JIRA] Created: (TEIID-704) Missing message for key "MembershipServiceImpl.Logon_failed"
by Paul Nittel (JIRA)
Missing message for key "MembershipServiceImpl.Logon_failed"
------------------------------------------------------------
Key: TEIID-704
URL: https://jira.jboss.org/jira/browse/TEIID-704
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 6.2.0
Environment: fedora 10, OpenJDK 1.6.0, Teiid build 7/6/09, JBoss AS 5.1.0GA
Reporter: Paul Nittel
Assignee: Steven Hawkins
Whilst exercising the membership provider stuff (deployed Teiid in JBoss AS), I encountered this missing message. The whole (probably more than you need) message is:
org.teiid.MEMBERSHIP - <Missing message for key "MembershipServiceImpl.Logon_failed" in: com.metamatrix.platform.i18n>
[LogonException]user warren could not be authenticated
at com.metamatrix.platform.security.membership.spi.file.FileMembershipDomain.authenticateUser(FileMembershipDomain.java:145)
at com.metamatrix.platform.security.membership.service.MembershipServiceImpl.authenticateUser(MembershipServiceImpl.java:342)
at com.metamatrix.platform.security.session.service.SessionServiceImpl.authenticateUser(SessionServiceImpl.java:207)
at com.metamatrix.platform.security.session.service.SessionServiceImpl.createSession(SessionServiceImpl.java:148)
at org.teiid.transport.LogonImpl.logon(LogonImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:101)
at $Proxy256.logon(Unknown Source)
at org.teiid.transport.LocalServerConnection.authenticate(LocalServerConnection.java:72)
at org.teiid.transport.LocalServerConnection.<init>(LocalServerConnection.java:65)
at com.metamatrix.jdbc.EmbeddedConnectionFactoryImpl.createConnection(EmbeddedConnectionFactoryImpl.java:103)
at com.metamatrix.jdbc.EmbeddedDriver$EmbeddedTransport.createConnection(EmbeddedDriver.java:465)
at com.metamatrix.jdbc.EmbeddedDriver.createConnection(EmbeddedDriver.java:146)
at com.metamatrix.jdbc.EmbeddedDriver.connect(EmbeddedDriver.java:120)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:207)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:195)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:633)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:267)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:622)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:404)
at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:381)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:496)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941)
at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)
at org.apache.jsp.qb2_jsp._jspService(qb2_jsp.java:79)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:322)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:249)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:636)
--
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
16 years, 8 months